A character starts as a paragraph. Then that paragraph becomes a quest, dialogue, a location, a character model, animations and code. Before long, one idea exists in half a dozen places. Then you change the character. Which version of the story is still correct? Does the dialogue reflect the change? Did you implement the new rule, or only discuss it? Where did you write down why you made that decision? That's the problem behind PlayWeld. I'm PlayWeld's creator, and I'm building a free, Apache-2.0 desktop workspace to keep game files, design records, conversations and supervised implementation work close together. Imagine a fictional flooded city powered by machines that consume memories. You decide that using a machine must cost the player a memory they have already discovered. That single rule can affect dialogue, quests, interface feedback, assets and code. The workflow I want is straightforward: record the rule beside the project files, discuss alternatives, explicitly adopt a decision, search back to its source, inspect the affected files, and keep the actual validation result separate from the plan. A discussion isn't automatically canon, and an impact preview doesn't guarantee that every dependency has been found. PlayWeld is built on Eclipse Theia and brings code editing, project notes, discussions, indexed search, supervised tasks and impact previews into the workspace. Asset and engine workflows have separate setup and review steps; generated material still needs review before import. This is a workspace you supervise, not a promise of automatic canon synchronization or a complete autonomously generated game. The current 0.21.0 Windows/Linux downloads are testing prereleases. Try a copy of a project first. Engines are installed separately; optional external model and asset providers can charge and receive project context. The recorded walkthrough shows saving notes, tagged discussions, local lexical search and an impact preview in a disposable project. It doesn't demonstrate every engine integration or end-to-end AI task execution. Demo and example: https://playweld.com/#demo User and technical handbook: https://github.com/scarecr0w12/PlayWeld/wiki Source and testing builds: https://github.com/scarecr0w12/PlayWeld For people building creative tools: how do you keep the reason for a change close to the work it affects? A concrete example of something falling out of sync would help me more than a feature wishlist.   submitted by   /u/scarecr0w12 [link]   [comments]