feat(roblox): add verifiable engine workflow and evidence gates - #7
feat(roblox): add verifiable engine workflow and evidence gates#7Aming9303 wants to merge 21 commits into
Conversation
|
The implementation and both editable games are complete, but the Roblox account used for account-bound validation is currently locked by Roblox's automated security checks, preventing public experience publication. Would public playable links published by an authorized collaborator or Roblox group be acceptable if this PR still includes the editable place sources, videos, Studio self-test output, and full performance evidence? I will not attempt to bypass the account restriction. |
…to-game-3-sync # Conflicts: # README.md
|
Public Roblox Experience URLs are not obtainable because new publishing accounts are being suspended by the platform. The PR already includes reproducible place files, verification videos, screenshots, self-tests, and performance evidence. Could those artifacts be accepted for evaluation in place of public Experience URLs? |
Submission status
The Roblox engine path, both complete benchmark games, generated Thrixel assets, imported scenes, runtime evidence, and reproducibility tooling are complete. The Thrixel Developer Program registration linked to @Aming9303 is active.
Delivered
stormwatch: survival storms with a rotating lighthouse beaconcourier-circuit: vehicle delivery loop with independently moving wheels.rbxlxfiles, generated FBX/GLB assets, textures, manifests, screenshots, videos, self-test output, and performance JSONPublic evidence
Stormwatch
Courier Circuit
Remaining account-bound step
The implementation stays draft until those two public playable URLs are attached. No attempt will be made to bypass Roblox account restrictions.
Closes #3 only when marked ready.