SteinWipe Motion Control For X1 Series & Bambu Studio SSD

Core 0 Feb.15.2.2025 -> Core 1 Apr.28.1.2025

- First X1C release using the SteinSwitch Definition (SSD) architecture. Configuration moves from inline code editing to keyword entry in the slicer's printer notes field.
- 54 unique SSDs available at launch; every Core 0 feature plus new chute tapping aggression levels (soft/med/hard), SteinRetraction variants (low/med/max), purge flow percentage control (25/50/75/125%), automated wipe cadences, and the AMS detour family (steinwipe / snake / reverse wipe).
- New file: TimeLapseGcode. First time BBS separates time lapse from layer change; smart {elsif} coordination avoids double-wiping when first-layer-scan wipe already ran.
- First community credit embedded in code: OldSalty3D for the ignore_fan_cover_alarm feature. Sets the convention going forward.
- Purge bucket pause automation; auto-pauses the print when the bucket approaches overflow.
- Full rework of material change structure; tool_number now drives all multi-tool vectors.
- BBS 2.0.3 support throughout.

This is the Core 1 beta release for the X1C and Bambu Studio, representing a fundamental shift in how SteinWipe Motion Control gets configured. Instead of editing gcode directly, every feature is controlled by dropping keywords into the slicer's printer notes field.

Core 1 keeps everything that made Core 0 stable and adds a long list of refinements. Retraction management, aggression-tuned chute tapping, purge flow percentage control, per-layer wipe cadences, and three different AMS toolpath options give users much finer control than Core 0 offered.

The SSD architecture unlocks something Core 0 could never do well: configuration sharing. Copy your printer notes field and send it to another user; they paste it in and have your exact setup. No file sharing, no violating TOS, no code editing.

Full user manual is linked in the Resources section above. If you want to understand the SWMC core system itself, the SWMC Preset Cores Explained resource page covers the full architecture.

Core 0 stable (Feb.15.2.2025) remains in active maintenance for users who prefer the proven baseline over the newer feature set.