Update START_CHAMBER_TEMP mapping docs for Prusa Slicer

[TonyBrobston]

I reported an issue and later found that the custom start g-code in the documentation uses chamber_temperature for both START_CHAMBER_TEMP and CHAMBER_TEMP, when there is a chamber_minimal_temperature meant for START_CHAMBER_TEMP, so I updated the docs to reflect this. Also, it appears that the SuperSlicer documentation already has the correct mapping.

https://discord.com/channels/582187371529764864/1441546673104097350

Summary by CodeRabbit

• Documentation
  • Updated START_PRINT macro examples to reference the correct chamber temperature source for single-toolhead and IDEX variant configurations.

_{✏️ Tip: You can customize this high-level summary in your review settings.}

[coderabbitai]

Walkthrough

Documentation update in slicer configuration examples that modifies the START_PRINT macro's chamber temperature parameter from [chamber_temperature] to [chamber_minimal_temperature] for single-toolhead and IDEX printer variants.

Changes

Cohort / File(s)	Change Summary
Documentation: Slicer Macro Examples site/docs/slicers.md	Updated START_PRINT macro examples to replace the chamber temperature source from [chamber_temperature] to [chamber_minimal_temperature] in single-toolhead and IDEX variant configurations

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Pre-merge checks and finishing touches

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title accurately summarizes the main change: updating documentation for the START_CHAMBER_TEMP variable mapping from chamber_temperature to chamber_minimal_temperature in Prusa Slicer start G-code examples.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment

---

📜 Recent review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 058ca10 and 31de02a.

📒 Files selected for processing (1)

• site/docs/slicers.md (2 hunks)

🔇 Additional comments (3)

site/docs/slicers.md (3)

56-58: Correct variable used for START_CHAMBER_TEMP in Prusa Slicer single toolhead.

The change from [chamber_temperature] to [chamber_minimal_temperature] aligns with the PR objective and is consistent with SuperSlicer's documentation as referenced in the PR.

---

66-68: Correct variable used for START_CHAMBER_TEMP in Prusa Slicer IDEX.

The change from [chamber_temperature] to [chamber_minimal_temperature] is consistent with the single toolhead variant and aligns with the PR objective.

---

186-192: Pre-existing documentation inconsistency: Super Slicer single toolhead missing START_CHAMBER_TEMP.

The Super Slicer section contains a pre-existing inconsistency between variants. The IDEX variant (lines 195-200) correctly includes START_CHAMBER_TEMP=[chamber_minimal_temperature], but the single toolhead variant (lines 186-192) omits this parameter entirely. For consistency, the single toolhead variant should also include START_CHAMBER_TEMP=[chamber_minimal_temperature].

This should be addressed in a follow-up as it is outside the scope of this PR.

Tip

📝 Customizable high-level summaries are now available in beta!

You can now customize how CodeRabbit generates the high-level summary in your pull requests — including its content, structure, tone, and formatting.

• Provide your own instructions using the high_level_summary_instructions setting.
• Format the summary however you like (bullet lists, tables, multi-section layouts, contributor stats, etc.).
• Use high_level_summary_in_walkthrough to move the summary from the description to the walkthrough section.

Example instruction:

"Divide the high-level summary into five sections:

1. 📝 Description — Summarize the main change in 50–60 words, explaining what was done.
2. 📓 References — List relevant issues, discussions, documentation, or related PRs.
3. 📦 Dependencies & Requirements — Mention any new/updated dependencies, environment variable changes, or configuration updates.
4. 📊 Contributor Summary — Include a Markdown table showing contributions:
   | Contributor | Lines Added | Lines Removed | Files Changed |
5. ✔️ Additional Notes — Add any extra reviewer context.
   Keep each section concise (under 200 words) and use bullet or numbered lists for clarity."

Note: This feature is currently in beta for Pro-tier users, and pricing will be announced later.

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}