[GH-ISSUE #319] [Feature]: Manual matching system with tags on printers and gcodes #202

Closed
opened 2026-05-06 12:27:12 +02:00 by BreizhHardware · 1 comment

Originally created by @jnswlln on GitHub (Feb 10, 2026).
Original GitHub issue: https://github.com/maziggy/bambuddy/issues/319

Originally assigned to: @maziggy on GitHub.

Problem or Use Case

Currently, it is not possible to set a manual filament color on printers and gcodes. As we have a large library of products and colors, we would have to upload 1000+ gcodes to use Bambuddy.

Proposed Solution

Set a specific color on a printer manually in the printer settings. When adding a gcode to the queue, it should be possible to set a specific color for the gcode. The printer(s) then take(s) a job that is matching (color and printer, at a later stage nozzle size).

Printers used: P1S, A1 at later stage.
Slicer: Usually OrcaSlicer or a combination of Grasshopper and Orcaslicer, rarely BambuStudio.
We would use Bambuddy in a 60 printers farm. Will this kind of workload function with Bambuddy?

Alternatives Considered

No response

Feature Category

Print Queue & Scheduling

Priority

Critical for my use case

Mockups or Examples

No response

Contribution

  • I would be willing to help implement this feature

Checklist

  • I have searched existing issues to ensure this feature hasn't already been requested
Originally created by @jnswlln on GitHub (Feb 10, 2026). Original GitHub issue: https://github.com/maziggy/bambuddy/issues/319 Originally assigned to: @maziggy on GitHub. ### Problem or Use Case Currently, it is not possible to set a manual filament color on printers and gcodes. As we have a large library of products and colors, we would have to upload 1000+ gcodes to use Bambuddy. ### Proposed Solution Set a specific color on a printer manually in the printer settings. When adding a gcode to the queue, it should be possible to set a specific color for the gcode. The printer(s) then take(s) a job that is matching (color and printer, at a later stage nozzle size). Printers used: P1S, A1 at later stage. Slicer: Usually OrcaSlicer or a combination of Grasshopper and Orcaslicer, rarely BambuStudio. We would use Bambuddy in a 60 printers farm. Will this kind of workload function with Bambuddy? ### Alternatives Considered _No response_ ### Feature Category Print Queue & Scheduling ### Priority Critical for my use case ### Mockups or Examples _No response_ ### Contribution - [ ] I would be willing to help implement this feature ### Checklist - [x] I have searched existing issues to ensure this feature hasn't already been requested
BreizhHardware 2026-05-06 12:27:12 +02:00
  • closed this issue
  • added the
    invalid
    label
Author
Owner

@maziggy commented on GitHub (Feb 10, 2026):

This is already available.

Docs -> https://wiki.bambuddy.cool/features/print-queue/?h=ams+mapp#ams-filament-mapping

<!-- gh-comment-id:3877336313 --> @maziggy commented on GitHub (Feb 10, 2026): This is already available. Docs -> https://wiki.bambuddy.cool/features/print-queue/?h=ams+mapp#ams-filament-mapping
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/bambuddy#202
No description provided.