First drafts of the base design documents #1
Conversation
|
This is Very unfinished and doesn't outline nearly enough. The core document will have to be filled out eightfold and the other documents will have to be filled out at all. |
|
I'm awaiting a vibe check from Robin on what this has got so far, and planning to return to this tomorrow. Knowing myself I don't know how long I can sustain work on this at a reasonable pace but I know that making a design document before touching anything in a game fork is Mandatory to avert crisis, primarily because me and Robin have different visions, both presumably very detailed already. I'm not sure why I'm referring to Robin in the third person since there's not really anyone else this is targeted to? I want to consolidate (coalesce? negotiate?) our visions into a unified design so development can start and commence smoothly. |
Docs/core.txt
Outdated
| Map flavor and challenge (in regards to engineering gameplay) is expressed through the preset | ||
| configuradion of the Drill, and it's distance to the destination of it's products. |
There was a problem hiding this comment.
AI core representing computer control module. powersink representing universal power input (god that's a terrible name for it). AME controllers representing various output ports. Input ports not pictured because I hadn't thought of that when these images were made.
|
What 8 hours of sleep and ample time to write does to the readability of a design document. (This reads so much better now) |
|
Embarrassing display of poor standards here, really. Any subsequent PRs ought to be much cleaner and unfinished PRs should actually be drafts. A PR template and auto-closing should probably be set up later. |
|
Really I'm just a circus monkey with strong opinions on game design. |
arenaconspiracy
changed the title
1 participant
I forgot to make a new branch to push to and make a PR from because 1) I'm tired because it's late at night 2) I'm in a hurry because it's late at night. Oops.