Wograld is a free-software, 2d, multi-player online roleplaying game based currently on the crossfire engine. Development is, unfortunately, done by developers, supernatural entities that seem to posses software users and force them to hack away writing software code for hours on end.
Saturday, June 2, 2012
What's my name? Java Development
Wednesday, December 28, 2011
Java User Interface Development Woes
Crossfire has had several revisions since Wograld split off from it. Wograld has also had several revisions since that time, so it would consist of changing the things that are different so it works with wograld. One thing, is I don't have a metaserver. I would find it difficult to justify having a metaserver when no one wants to play a buggy pre-alpha with missing artwork and most of the awful crossfire gameplay (I mean there is a reason that usually I never see more than four players logged onto crossfire right?)
I don't think the game is even really ready for alpha yet with the amount of user interface work that needs to be done.
I've considered trying to recruit project team members again, but until its really playable, that just seems like a dead end. After all, no matter how good of an artist you are, programmers do not want to work on your game until you show them the code compiling and running with a nice user interface. I hate how programers make artists feel like they are less important. If programmers cared more about artists and what they want maybe we would not still be having these stupid debates about intellectual property and artists would be making money on free culture works all over the place. Sorry, I've been getting into a rant, but its the end of the year and I hoped that the Java User Interface would be done by now.
Sunday, July 17, 2011
Uploaded some Wall posters.
Wednesday, July 6, 2011
Top Ten reasons not to play Wograld right now
10. Its only been tested on Linux... trying it on the windows system like enough said.
9. You have to follow the admin install directions, if you are the sort of person who is reading this and doing it anyway, even though I said not to , you are not a person who follows directions, so you are not going to do well with getting it set up so it works.
8. Missing artwork. There is only one character class and race that shows artwork in game, otherwise you will be playing an invisible character.
7. Same poor game play as crossfire, only with some missing artwork, so you won't even know what killed you half the time. If you want crossfire, just go play it, but why would you considering how awful it really is.
6. No permanent server set up, how fun is it really going to be playing with yourself...
5. You have to play as root or it won't save your character, or you have to change the permissions on some folders.
4. Did I mention the bad game play, lets go into detail, one hit killed as a newbie sorcerer with a swinging door. Should sorcerers really be that frail? No freaking way!
3.Level system, and experience loss when you die, you lose stats too, so you can get worse than a newb fast.
2. You don't have to die to lose stats and experience, fighting certain monsters will also do this.
1. Ta Da, the number one reason not to play Wograld right now... The user interface is really bad. You won't be able to figure it out. It is ugly, has buttons that do nothing, and no way to know what macros you have easily.
Wednesday, June 29, 2011
Iso Crossfire
I always hated the fact that it feels like I am working on iso-crossfire, and not the Wograld project that I really want. This game has my new graphics, and a new, yet lousy, user interface. Yet I can't help feeling like I am only playing crossfire in 45 degree isometric. That is because none of the game mechanics have changed including ones I hate, such a experience loss, dying from getting hit with a normal swinging wooden door, stat loss diseases everywhere, and a combat system that seem to consist of run into things and watch them die. At least they die relatively quickly compared to some boring games, so you get a chance to go through the exciting loot.
Well, horror of horrors, my wonderful lead developer actually likes that something like iso-crossfire exists. So before we fix any of the glaring game mechanic problems, take out the extra races from the start area and add a male/female of each of orc, human elf and undead, we have to trudge through and actually fork our own project into a useless, unremarkable, not in demand game. After all, if I really wanted to play crossfire, I would just play it, and not this abomination, halfway between crossfire and Wograld with missing graphics.
I'm not quite sure what is the point of useless sourceforge projects and dead branches. Frankly, I think it is a waste of disk space. After all, given a choice between Wograld and iso-crossfire, I would gladly chose Wograld. In fact, for years thinking about how I would actually have to play test some of my changes using the horrid Crossfire kept me from working more on Wograld.
Developers arn't easy to come by though, so if he wants to waste some time forking the project so what. I wonder if that is what will happen to most game projects eventually, there will be the number of game projects >= the number of game developers on the project with all the forks.
Happy forking and fork you!
Wednesday, May 25, 2011
Fixxed the Segfaults... BUT
Anyway, enough with the stupid puns. The user interface for the map editor still sucks dangling donkey parts. You still can't click on things in the pick maps and expect them to show up in the object window of the map-editor. The co-ordinates are all off. Furthermore, all the items in the pick-maps do not display properly. I tried messing with them again a couple days ago.
Instead of fixing the user interface however, my wonderful lead programmer decides to add a bunch of stuff that is in the wrong perspective and the wrong size, into the cvs arch folder. These new arches are from other crossfire forks. I told him he does not need to do that. When I saw what he was starting to do, I got horrified. Except he doesn't use the cvs add command. Now his folder is littered up with a bunch of ? marks in front of the new arches. He really should not have done that. Only one more day until my other programmer comes back from vacation. Then we really won't get any work done because she will be too busy obsessing on cleaning and telling our lead programmer what a lousy job he does wiping the floor and taking out the trash.
I started working on my web comic again and making new 45 degree 64x64 and 64x128 tile objects that we can hopefully add once lead programmer stops trying to add stupid arches and fixes the map editor bugs.
I recently read about something called "programmer art". Apparently programmer art is when programmers do quick and dirty artwork to make demos of some software project. It looks really bad like they can't draw. In most cases, they probably can't, but it is more of a case they don't care how bad it looks. Our project suffers from the opposite problem. I feel like we have a lot of artist code. Code that is just in there to show off the awesomeness of our artwork. It seems like no one on this project really wants to work on the code, and would rather be doing art. You can't play a computer game without the code, however.
Thursday, May 5, 2011
Who's Fault? Segfault
Well, actually, if you want to see, just download the server with the map editor, wogedit from today's date or a bit earlier and see what I am complaining about her on the blog. If we could have fixed the tiles to begin with, we would not have this problem. I don't know why fixing it in the map editor became so hard. It just did.
I am not sure if the any of the segfaults are directly related to the major display user-interface problem that I described. Actually, one of them is not. If you left click in a box on the top of the editor. When you are over a tile, there is a top part of the editor that displays what is on the tile you clicked. (of course it maps the wrong tile) Then it segfaults on you. That is not nice. But it is what we are stuck with until we can figure out how to fix the code bugs. No one else wants to look at our buggy code, so we are stuck fixing it ourselves. I had thought that open source meant you could get better programmers to do you dirty work like fix major bugs, but I guess that is not how it works. Maybe my essay about keyboard monkeys seems a little naive now.