Core-side tracking issue for supporting map/construction-area expansion mods.
Linked mod-side issue: TajsMods/MapExpansion#1.
Player request context:
- Players want a bigger construction area, roughly 2x current size.
- Large schematics often do not fit after paste or portal workflows.
- Manual post-paste adjustment is annoying and fragile.
Core MVP:
- Provide a stable API or hook point for mods to adjust construction/workspace bounds.
- Avoid relying on editor-only changes that do not work in shipped builds.
- Keep vanilla behavior unchanged unless a mod requests expansion.
- Make bounds changes safe for node placement, selection, wiring, camera movement, and save/load.
Implementation notes:
- Prior attempts suggest patching the relevant window/container script directly may be unreliable in the shipped build.
- Core may need to expose a helper/hook around the game script that owns workspace bounds, placement validation, or camera limits.
Acceptance criteria:
- A mod can request larger workspace bounds through Core.
- The request is applied consistently in shipped builds.
- Existing saves and vanilla behavior remain safe when no mod requests expansion.
- Diagnostics/logging make it clear whether expansion was applied or failed.
Core-side tracking issue for supporting map/construction-area expansion mods.
Linked mod-side issue: TajsMods/MapExpansion#1.
Player request context:
Core MVP:
Implementation notes:
Acceptance criteria: