mg-polish

Identify all Synty dependencies including baked copies under _Project/Art, then build original models in Blender and integrate them through the existing arena or art builder scripts. Verify remaining references from other games before deleting old assets.

Export FBX with axis_forward='-Z' and axis_up='Y', then validate one representative object in Unity for units, orientation, pivot, normals, UVs, and scale next to the player before mass export. Rebuild materials manually in URP rather than relying on automatic Blender node transfer.

No. It preserves rules, scoring, phases, timers, hidden information, player roles, server authority, and existing network events. Changes to core game design require a separate explicit proposal beyond the artistic freedom granted.

The project uses a local Blender MCP bridge on 127.0.0.1:9876 with tools/blender_client.py, but generators can also run in a background Blender process with --background --python. Check bridge state first and never run factory-reset generators over an unsaved scene.

Rebuild the scene through the standard builder, confirm reproducibility without duplicates or lost references, capture before/after screenshots from actual gameplay cameras, and run host plus client Play Mode tests exercising changed interactions, effects, and network reactions.

Do not use it to create a brand-new minigame or to apply isolated logic bug fixes. It targets full artistic rework of an existing scene, visual reference implementation, or repeat polishing passes on already-built games.