I have submitted a pull request for PrusaSlicer to add basic G10 temperature support for RepRapFirmware. I'm trying to minimise what I include in this for now to increase the likelyhood that it will get accepted. This absolutely won't replace the post processing scripts such as the great one created by @mkudzia which does all sorts of other clever stuff, the idea here is just to get better RepRapFirmware style G-code out of the box. The main changes are: Do not add M104/M109 automatically if there is already a G10 G-code line in the start custom start G-code. This removes the need for the hack of putting in a blank M104 line to suppress this behaviour. When automatically adding tool temperature too start G-code (if the user did not include G10 or M104/M109), use G10 style temperature G-code if the firmware flavour is RepRapFirmware. Use G10 style temperature G-code when adding all other temperature commands (e.g., on rest of layers or layers with temperature changes set) if the firmware flavour is RepRapFirmware. Use the G10 P parameter to specify tool number in temperature commands when there are multiple extruders and the firmware flavour is RepRapFirmware (if there is only one then you get no tool numbers at all in the output, which is what you probably want on a single extruder machine). This should (if I can get the pull request through) remove the need for post processing tools to hunt down the M104/M109 commands and replace them, at least meaning less work for post-processing scripts to do and more functional default G-code. In my start G-code currently I use the standby_temperature_delta variable from the Ooze Prevention section to set the standby temperatures. I will likely do another pull request for adding real standby temperature support in the future since this should really be part of the filament not the print settings. For now though it gives me a way to use it. I know there are likely all sorts of things people would want to see change in PrusaSlicer with respect to the Toolchanger but right now for me lack of G10 support was the most problematic for me. I've implemented the above changes in my fork and have submitted a pull request. If you are familiar with building PrusaSlicer from source already you can build it from the branch for this change in my fork here: https://github.com/ardenpm/PrusaSlicer/tree/pa_reprap_g10_temperature_support If anyone thinks of any G10 gotchas not covered above let me know. If you want to comment directly on the pull request you can find it here: https://github.com/prusa3d/PrusaSlicer/pull/4553 I don't think this would ever get priority from the internal team (there are request from back in 2017 still for this), so hopefully it's able to get through.