Working on "difficult" stuff which are features or bugs that you write down but never fix. I've noted these in the source code with a comment starting "note:", this is what I do in all my projects. I do also have a list for bugs, and also separate notes in the project management spreadsheet. I think fixing these things is mainly what is required to finish the game... Some of them are purely technical source code issues, but others can be logic problems like the infamous "pit problem" where it's uncertain what happens if you push a movable object into a pit. In games like Nethack a boulder plugs the hole completely, but in Kaduria it would maybe look funny if something like a potted plant would plug a hole and make it a solid floor. Even if the movable falls into the pit, what happens if you try to push another object on top of it? Maybe it just...
Some of these difficult features are not that hard after you think about them for a while, but it's the idea of them being hard that can be the difficult part itself. I guess life is full of situations like these. Something seems to be so hard that you give up even thinking about it. The annoying thing is that it could be possible if you just did something about it. If you just asked her. But doing so could make you look like a creep and you could lose your self respect.
No comments:
Post a Comment