deepgrain-foundry/docs/history/requests.md

The owner's requests, in their own words

What the owner asked for while the game was built in claude.ai, kept word for word so the intent behind a feature can be checked. The newest are at the bottom. For what was decided and built, see docs/DESIGN.md.

Messages from before 2026-10-20 are not available word for word. The early design (2026-10-17 to 2026-10-19) is summarised in the "What the owner wants" section of docs/DESIGN.md.

2026-10-20 (sent again 2026-10-22)

• A lot of times im leaving behind a few bits of materials unmined and thats leaving obstackles in my way. how can we handle that. its a little annoying.
• belts and filter belts should mesh together as one belt.

2026-10-22

seems like sometimes when ticking items with R with he vacuum, then sucking items not starting with one that was ticked, will just suck everything. like if you tick coal and copper then click and drag from stone, you also pickup stone and other stuff.

dont let the too hard specs crumble at all. world gen shouldnt generate viens that small anyway. leaving them creates friction for flying, crumbling them into what they are leads to player confusion about how they obtained them without the right bit, and crumbling to stone or something means lost ore.

when drawing belts and filters, set their direction in the direction of drawing them. allow manual setting with R when they are placed without dragging. maybe show an arrow when dragging to place to indicate it and update the filter box on the top left where it says the direction and R.

instead of rounded ends on the belts and filters, lets make them rectangles but somewhat rounded corners.

instead of a copy tool. use modifyer keys like X for cut, c for copy. you hold the modifier while dragging a box around. when release it executesd the action. make it clear what function will happen. make them istinct. cut is destructive but it can be pasted back so its not too bad.

add ctrl+z undo for building.

when placing building objects, hold ctrl to go to replace mode to for it to replace.

please explain how to use fans in a furnace. they seem to get destroyed when in contact with the heat from smelting.

Lets allow refining of stone to get out trace amounts of common ores. maybe refine sand, dirt and gravel too?

what can we do with all the stone in the world? itsa building material but other than that not much else use. the player may want to store it somewhere for use later. but what about the rest? it just sits somewhere clogging up the place. refining can help, refining can reduce it. what else can we do with it?

need a way to move water. maybe pumps, pipes, and outlets.

2026-10-23

it seems like the screw tubes can carry more materials than the belts can, that makes a buildup on that belt. they should be the same. if the player wants more input they can build additional screw tuibes and another level of belts or something.

sand can be re-refined. that is nice but is it intended? im not sure if its good or not. in one hand the pl;ayer ends up with a lot of sand and not much to do with it all. but on the other hand re refining it means they could get more ores while reducing their sand stockpile. This also means its possible to stack refiners (one block clearance) and re-refine the sand multiple times until none is left. lets talk about this.

add a dropper/ pick item key so you can select an item already built to build more.

we need a better designed for ux, build menu system.

there seems to be some sort of length limit on building belts with drag. lets remove that.

in real life if a stack of items is on a belt, the belt does not move the items under them while leaving them stationary, thats not how physics works. lets make it more realistic.

pipes should not block water.

I also like all your ideas worth building next: Glass chain… Storage silo… Builders' orders… Cut stone or concrete… One thing about the silo though, lets make it look less like a magic black hole you can place and more like a real silo.

The four ideas were:

• the glass chain (sand to glass);
• a storage silo;
• builders' orders for bulk rubble;
• cut stone or concrete.

Cut stone was built; concrete was not.

Moving to local development

i have more notes for you but ive been thinking about exporting this to code it locally with claude code and codex. I would also need all the notes and other supporting documents and information about it and its development, and probably also an agents/claude.md files with good instructions for building this. Before i do this though i want to discuss how this would work and if the cli coding agents would be able to play test it and take screenshots as you are. i think for a while at least i might leave it as a web game like it is now but i might have the agent split the artifact into multiple modules for better coding practice and host it with python http server i think. i imagine you are playtesting the game with playwrite? i want the agent's to be able to playtest it the same way as you are. much later after the game is at a certain stage i may consider converting to a rust game for performance. but for now its fine as is. lets discuss this before moving forward with any export.

I do have more notes, some that i was planning on giving you now and some for the future, but for now you could just not work on any of them and include them in a notes file i can add to locally after the export. the agent could read and modify the notes file removing items that have been completed. the completed items could be recorded in another log the agent uses internally for its self. ill be adding more notes to the notes file which it could read and complete when asked. for now a zip export is fine, ill have the agent add it to a gitea instance i have, here i think claude probably only supports github. make sure the agent instructions include things like to not hallucinate, assume or be too confident. confirm with different sources if not confident enough and use the web when needed. as for splitting it to modules i think keeping the build step is fine for now. but i do want to split the larger source files more. the agents will work better with smaller more concise files. the agents should also create a project map for their use so they can quickly find the information they need when its not in context. before the export, are there any more questions or concerns you have?

q1: yes please split for me first that will make the agents get to work faster. maybe also deduplicate and refactor a little too while you are at it? ofcourse full testing first to confirm the game still works properly. q2: the done please check section is actually a better idea. q3: i usually run one or the other and if its claude code, i have instructions for it to locally delegate to codex some things to save tokens. so one at a time i guess. but codex and claude working side by side and some way for them to communicate sounds like a good idea, but for later, ive never done it that way and will need to figure out and plan how that will work first.

concerns: note 3 was not fixed, all of those notes i wrote after version 24. i have exported the only save i care about. claude code and codex both have web access.

The notes written after version 24 are in NOTES.md. The note "keep sand as is, allow re-refining..." was a decision, so it is recorded in docs/DESIGN.md instead.