|
Post by keymaster on Oct 2, 2017 17:04:21 GMT
Do you know what white sheet syndrome is?
The funny thing is I know exactly what I want my end goal to look like, a interrupt script in 'model' and adding two collective lines to tile and movement.
In tile I added a isTrapped bool that interrupt flips on enter and exit.
And movement checks each tile traversed on enter and on a isTrapped tile calls the interrupt script.
Then I get to writing the actual interrupt script and realised I don't know what I want it to actually be, is this a base class like point that i should write other scripts for in view so I can add damage and status to it? Should the base interrupt stop the movement or should I keep that in the movement script? Then I just remembered when I following along and I snagged on modifying the state machine somewhere and I spent a day trying to solve it, then gave up and just copied the repository.
So that was my last week, and I swore I would not repeat myself and started a new this week. Which is here....
|
|
|
Post by Admin on Oct 2, 2017 22:06:41 GMT
It's funny that you mentioned "white sheet syndrome" because I would say that the common suggestions to overcome this for writers are just as applicable for you as a programmer. In particular, I would say, "just start coding" - it might not be perfect, but this is why we begin with prototypes. Just getting something working is very inspiring and helps you to see what works and what doesn't. Then you can always go back and refactor as necessary for more stable, elegant, reusable code, etc.
|
|