Showing posts with label Psychology. Show all posts
Showing posts with label Psychology. Show all posts
Saturday, 17 January 2009
World of Warcraft is the new Rogue
Alright, that might just be a bit of an overstatement, but it does seem like some MMO-companies have been taking a leaf out of roguelikes when it comes to game complexity and tactics. Granted, the company concerned does have quite a track record when it comes to roguelikes, but the level of detail and thought that has went into some encounters and the tactics and complexity required to overcome them rivals that of some roguelikes at least. Granted, MMOs generally lack randomness, and of course permadeath, and a whole host of other features common in roguelikes, but I think there is a strong case for at least a commonality between the genres. What do you think?
Monday, 28 July 2008
Apologies #2
Once again, due to RL issues taking longer to resolve than anticipated (specifically the mother of all assignments on these beasties*), I've not done much coding or design work on Kharne since my last post.
However, in the meantime, a lengthy entire outline of an abandoned roguelike was posted on r.g.r.d., and judging from its length, I can see why it was abandoned. When confronted with a todo list of that magnitude, any programmer, no matter how great they are at getting things done, or how skilled, would shake and quail.
For Kharne, I have a multitude of ideas, enough to keep me programming for two years, yet the basic framework, or what passes currently for the basic framework is already 14k lines of code:

But unlike the author of the abandoned attempt, programming on Kharne will recommence soon.
* Incidentally, as far as Wikipedia goes, the article isn't too bad. It does underestimate the impact of viscosity however, and doesn't mention hot-spots or boundary layers, but I'm not going to go to the lengths of editing the article to show this - I prefer to spend my time coding instead!
However, in the meantime, a lengthy entire outline of an abandoned roguelike was posted on r.g.r.d., and judging from its length, I can see why it was abandoned. When confronted with a todo list of that magnitude, any programmer, no matter how great they are at getting things done, or how skilled, would shake and quail.
For Kharne, I have a multitude of ideas, enough to keep me programming for two years, yet the basic framework, or what passes currently for the basic framework is already 14k lines of code:

But unlike the author of the abandoned attempt, programming on Kharne will recommence soon.
* Incidentally, as far as Wikipedia goes, the article isn't too bad. It does underestimate the impact of viscosity however, and doesn't mention hot-spots or boundary layers, but I'm not going to go to the lengths of editing the article to show this - I prefer to spend my time coding instead!
Wednesday, 4 June 2008
The Psychology of Getting Things Done
Andrew Doull over at ASCII Dreams has a screamingly relevant (to me) post up entitled The Cost of Interruption describing the travails that Roguelike Developers are going through. I must admit part of the reason I've slowed down coding on Kharne over the last couple of weeks is the same as his:
"...With coding, if I have a longer period of time, I'm more productive. Not as in twice as productive, but probably ten times or more...The reason for this is the time required to rebuild the mental model of the program before I can generate new, productive code. This mental model doesn't have to be complete, but it does have to be correct, and I've inadvertently introduced logic bugs that have persisted for years, due to faulty assumptions about how a particular section of code works..."
"...So rather than plain procrastination, blogging and gaming has become activities where I feel productive in a short term without experiencing this mind numbing interruption cost - the interruption cost of a blog entry is just re-reading the entry I've written so far, which is a much lower barrier."
I've experienced this succinctly in the last couple of days. Monday evening I was able to get a great deal of code written for the Magic-Handling GUI Interface in a good solid 2-hour stretch of coding, yet last night, when I finally managed to get round to doing some coding after spending most of the evening do something else (equally mentally draining as coding), I found I had great difficulty in doing even the simplest of functions (I was trying to write the routines to calculate the mana cost and spellcasting success probability of spells). In the end, I gave up and went to bed.
Its not quite got to the stage that Andrew describes though:
"...It has got so bad recently that I've started dreading coding, in so far as the idea of doing something half-way and getting interrupted is a feeling I don't particularly want to experience."
It also doesn't help that my s.o. is suffering from a bad flu at the moment and is thus spending most of her time playing Age of Conan, and seeing her play it nibbles slightly at the edges of my own MMO-addiction.
"...With coding, if I have a longer period of time, I'm more productive. Not as in twice as productive, but probably ten times or more...The reason for this is the time required to rebuild the mental model of the program before I can generate new, productive code. This mental model doesn't have to be complete, but it does have to be correct, and I've inadvertently introduced logic bugs that have persisted for years, due to faulty assumptions about how a particular section of code works..."
"...So rather than plain procrastination, blogging and gaming has become activities where I feel productive in a short term without experiencing this mind numbing interruption cost - the interruption cost of a blog entry is just re-reading the entry I've written so far, which is a much lower barrier."
I've experienced this succinctly in the last couple of days. Monday evening I was able to get a great deal of code written for the Magic-Handling GUI Interface in a good solid 2-hour stretch of coding, yet last night, when I finally managed to get round to doing some coding after spending most of the evening do something else (equally mentally draining as coding), I found I had great difficulty in doing even the simplest of functions (I was trying to write the routines to calculate the mana cost and spellcasting success probability of spells). In the end, I gave up and went to bed.
Its not quite got to the stage that Andrew describes though:
"...It has got so bad recently that I've started dreading coding, in so far as the idea of doing something half-way and getting interrupted is a feeling I don't particularly want to experience."
It also doesn't help that my s.o. is suffering from a bad flu at the moment and is thus spending most of her time playing Age of Conan, and seeing her play it nibbles slightly at the edges of my own MMO-addiction.
Subscribe to:
Posts (Atom)