SNAAAAAAAKE

[davidn]

It's so strange having such long evenings, now - I can come home, pick Whitney up on the way, doze about for an hour and a half then get up and realize that I would normally still be waiting for a bus underground somewhere. I'm beginning to see the advantages of dragging oneself into the office at a normal hour.

Anyway, I've been using that extra time well - do you see these bastards?



This is how they work.



Now I'm not opening that group of events ever again.

Comments

[davidn]

You've no idea how tempted I am to make a playable character out of that, now - but it's not just simple colour substitution like the other ones, so it would be much too time-consuming to add on a whim (mostly thanks to the naive way I laid out the game years ago). I feel it's a huge gap that I haven't done a furry-related game yet.

Most of the work in programming is in the thinking, rather than the writing of it :) Ironically the events look (and, indeed, are) rather more complicated than they would be in a straight code-based language... a lot of what they're doing is making sure that only specific objects get selected, whereas you could normally do something like:


for each Head
Move it wherever it's going
Add the new position to the list of coordinates that this Head recently existed at
Make old unused position drop off the end of the list
for each Body owned by Head
Move the Body to the position of the point X positions along in the point list, depending on how far this Body is meant to appear down the chain


Actually, I admit that's much worse than I thought even explained like that, but the point is that without a concept of objects being owned by others, you have to keep checking to see if IDs match every time, which bulks the whole thing up considerably.