Custom Start GCode not adding values to S

Hello, I was trying to print after taking a break for a few weeks and when I updated to the latests version of Cura 4.6.2 I could not use custom Codes anymore I'll share a piece of code so I can explain better. M104 S{100} M140 S{material_bed_temperature} M190 S{material_bed_temperature} G29 G1 Z

Changing default gcode output - Page 2 – PrusaSlicer – Prusa3D Forum

Only Custom Start G-code Prevents Filament Specific GCode · Issue #1317 · supermerill/SuperSlicer · GitHub

ExtraFileInfo

New PID values – User mods - OctoPrint, enclosures, nozzles, – Prusa3D Forum

Custom Start G-Code for filament does not apply into the G-Code correctly · Issue #551 · supermerill/SuperSlicer · GitHub

Custom Start GCode not adding values to S{material_xxxx_temperature} when slicing - UltiMaker Cura - UltiMaker Community of 3D Printing Experts

G-Code applied before custom startup - UltiMaker Cura - UltiMaker Community of 3D Printing Experts

PrusaSlicer G-code viewer

Slic3r Manual – Printer Settings

Prusa Slicer - no ooze leveling and a cleaner start with prime line (MuppetLabs) - GCODE for Prusa Slicer : r/prusa3d

Setting And Editing Your Start Gcode - Solidoodle Wiki

Start G-code problem on Prusa slicer : r/ender3v2

G-Code generated starts not with Start G-Code inputbox, M80 command Marlin not working /not supported · Issue #5345 · prusa3d/PrusaSlicer · GitHub

Custom Start G-Code for filament does not apply correctly · Issue #2549 · supermerill/SuperSlicer · GitHub

M420 S1 G-Code (Marlin Firmware) - Explanation & Usage - 3D Print Gorilla