Repository navigation
Add opt-in object-data export for World Editor - #1464
Conversation
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
|
Companion extension command: wurstscript/wurst4vscode#161 |
|
@codex review |
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 856d28202c
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
1 participant
Restore an explicit way to export combined input-map and compiletime object data for World Editor placement.
-exportw3oenables the existing.w3owriter without adding export cost to ordinary builds; the export also runs when object-file writeback is skipped by the cache.The new
wurst.exportw3olanguage-server command runs development compiletime generation, skips runtime script emission and release-map packaging, and returns_build/wurstCreatedObjects.w3ofor the VS Code command to reveal. Export failures report diagnostics, including unreadable input object files.Custom objects retain the
wurs = 42marker and can be imported into a new input map before regeneration under stable rawcodes. Base-object overrides remain untagged: deleting a tagged original-object entry would also discard editor-authored fields merged into it. The workflow and limitation are documented.Validation: 68 focused tests passed across
CompiletimeNativesTest,MapModelReuseTests, andWurstCommandsTests; the final export publication regression also passed after strengthening its output assertions. Coverage includes Jass/Lua generation, unchanged input maps, opt-in/cache-hit export, combined map objects, tagged-object cleanup, and bypassing release packaging. World Editor itself was not launched.Companion VS Code extension PR: wurstscript/wurst4vscode#161.