PLAY → INSPECT SOURCE → PLAN A PLAYABLE CHANGE
Find your starting point.
Make the next step concrete.
Find a browser game worth exploring. Compare what its code and content allow, then take a precise change brief to your own assistant.
20 external references, including a separately labelled commercial-game fan port. This workbench does not import, run, combine or build game source. A saved plan is not a working remix.
JavaScript is required for local filters and exports. The complete static game directory works without it.
01 / FIND A BASE
Play first. Read its source.
“Input response observed” is a limited historical check, not a completed game or a current quality rating. “No original game data required” is not blanket asset clearance.
No matching games. Clear a filter or try another mechanic.
02 / CHOOSE A CHANGE
Your remix plan
Compare these as alternative bases first. Two selections do not establish licence compatibility or a way to combine their engines.
Nothing is saved automatically. Download project JSON before leaving.
03 / TAKE IT TO YOUR ASSISTANT
A useful brief, with the cautions intact.
Your assistant still needs to inspect source and licences, pin a revision, run the unchanged baseline, implement the change and test a playable result. Keep the finished build, complete source, credits and test notes together.
Return a credited remix for separate review ↗. This plan is not a submission and does not grant publication permission.