Saturday, March 03, 2007


OK. This is off the cuff - no editing. So here goes.

Let's lay the cards on the table first: I develop Legends of Karinth for fun. I want to see it grow; I want to see it made into a better game. I was a player for a long time, and now, as a staff member, I have a chance to see all of the fabled 'someday in the future' systems come into effect. As the main coder for Karinth right now, I'm responsible for most of the changes that come in on a day-to-day basis. So, let me clarify a few things.

We are still in active development. Now, I don't want to come across as the bad guy, but this means that, like it or not, changes ARE going to happen. And, like it or not, some of them ARE going to be drastic. We still have the 'beta' tag, which means that lots of our planned systems aren't in yet, and many of the ones that are in need fixing up. Just because a command, a skill, a system, or whatever doesn't seem 'broken' on the player end of things, it could very well be totally buggy, causing crashes, dealing with memory poorly, and so on. A good example are flymounts. Contrary to popular belief, the code WAS horribly broken. You may not have always seen it for yourselves, but it was. The tethering system caused horrible crashes, strange bugs, and lots of other things. Removing flymount saving cleared them all up. What you also didn't see was a whole lot of back-end stuff changing, which makes them easier to store, easier to access, etc.

The beacon/gateway system is another example of that. Both of them had major problems, especially when it concerned saving them in the playerfiles. So, to clear them up, we changed how they were stored. Yes, this meant some changes to user-end gameplay. But we thought that we balanced out the change in distance pretty well by (A) making beacon a whole lot cheaper, (B) increasing the max number of beacons by a ton, and (C) removing the need to train gateway as a separate spell. So, again: it was a NECESSARY change that will benefit the game a lot in the long run.

Which reminds me - you need to keep in mind that not all of the changes we bring in are designed to make the game easier, and they're not designed purely with "now" in mind. We're trying to balance the game for the long run, meaning that when we bring in a change to something like repairing, it's been designed with a long-term view in mind.

Speaking of which, most players probably don't realize how much we discuss things up in staffland. We're not just bringing in changes because we feel like it, or because we want to screw the players. No. Virtually every change is a result of hours, days, or even weeks of discussion involving basically the entire staff. We have lots of stuff planned for this mud, and eventually it'll all be put in. We take into account the future when we're bringing in new code, and that's not going to change.

And of course, we welcome constructive criticism, suggestions, and all that stuff. Players are just as important to the game as staff are.But please, if you're going to criticize, don't just talk to one staff member. We're all responsible for the changes. Use the QA channel, send a note to 'staff' or 'immortals', etc. But verbally lambasting in private isn't good for anyone. It accomplishes nothing and only serves to antagonize. At the very least, if you ARE set on talking to one person and one person only, then at least talk to the person who's bringing the changes in: me. But, talking to one person is NOT going to accomplish anything. So, don't do it. Talk to us all. That's why we're here.

Finally: don't forget that we're fans of Karinth just like you are. We play the game too. We're volunteers. We're sacrificing our spare time - hours a week, even hours a day in the case of a tireless coder like me - to try to make this game better. Where am I going with all this? Exactly where I started: expect change. It's going to happen. And it's good. It might be shocking sometimes, but trust me - we do our homework.

No comments: