It’s been over a year since I posted here and I had basically given up on writing games, at least in the format I’ve always wanted to use. But I’ve picked back up here recently and made some really good progress really quickly, so maybe the 100th time is the charm, yeah? In any case, I’m working on a new (old) game and plan to post about it here soon.
I’m spending time here and there working on Codex Magnus but I’m honestly struggling a little. One issue is that I’ve started playing DDO again and that’s a major waste of time (of which I don’t have much) but more than that I am having trouble deciding how to move forward. There’s not much to the game as it is so you would think that picking a feature to add would be simple, but for some reason it’s not. It’s like everything that’s left to do is so big that I’m having a difficult time figuring out how to break each piece into manageable chunks. Here is a partial list of things that are left to implement:
- Battle system
- Inventory system
- Dialog boxes
- State management system
- Save/load games
- Dynamically loading/unloading map chunks
- Map ports (for interior locations or moving from one major area to another)
- Lots and lots and lots of art
I’m sure there are even more things I’ve left off this list but that’s plenty. When I look at an item like “Battle system” it’s difficult to imagine how to create a very first step, much less a finished product. Plus I’m still fighting with Phaser a pretty good bit. I still believe it’s just my lack of experience with real software development but looking through the examples for Phaser 3 and going through the documentation can feel like falling into a black hole. Specifically, I’m trying to figure out the plugin system. The Phaser documentation says it’s really powerful and useful, but so far it’s been mostly a headache for me. I’ll keep plugging away, but it’s frustrating how slow the process is.
I have a new version ready to go but have been lazy about releasing it. I’ll really try to do that this weekend, and maybe doing so will get my motivation back to where it needs to be.
As I said a few weeks ago I have decided that my original plan was just a bit too ambitious. I still very much want to create a browser-based role playing game, but I have decided to go with a 2d game that will hopefully be more manageable for a single developer. I’ve gone back and forth a number of times but I’m writing it here so that I will stop waffling and start coding: the game will utilize Phaser 3. There, I’ve said it so now I’m committed. At this point I honestly don’t like Phaser all that much. It does some cool stuff, but the documentation is a bit of a mess since there was a relatively recent major version change from 2 to 3, but it’s actively maintained and will clearly do everything I want it to do, I just have to figure out how to make it work. I feel a little bit like I’m jumping out of the frying pan and into the fire because I became frustrated with the 3d game due to my constant fighting with the pipeline I was using, and I’m afraid that Phaser may end up presenting many of the same challenges, but hopefully it will start to make sense once I’ve committed to using it and have spent a significant amount of time with it.
I will get into the plot of the game in a future post but the core story is about a young man who gets caught up in a world of danger because of his father’s involvement with a mysterious, powerful book called Codex Magnus. The story will be mostly linear and will the game will feel very much like the older JRPGs like Final Fantasy II/IV and Secret of Mana.
In an attempt to familiarize myself with Phaser I plan to write at least a few tutorials on it and post them here. Hopefully this will force me to really examine the documentation and understand it so that the tutorials will be useful and development of the game will be easier.
This is an exciting time and hopefully things will move fast, so stay tuned.
After much consideration I’ve decided that a 3d game was just too ambitious for now. I still believe it is totally possible to make a game the way I was trying to do it, just not with the abilities and resources that I have to devote to the project right now. Instead, I have decided to create a 2d game that will act as a precursor to the 3d game that I eventually would like to build. I’m going to keep the details light for a little while as I sort out exactly what this new game will look like, but I’m thinking very much along the lines of the older Final Fantasy games. That is, a party-based single player game with a largely linear storyline and tile based graphics. I’ve been doing some prototyping and so far it’s predictably much, much simpler to work in 2 dimensions than 3, so things are progressing quickly. I will probably have to eventually get some outside help on the pixel art because I’m just not much of a 2d artist, but there’s time to figure that out later.
I’m going to give myself until January 31 to get my ideas completely worked out in my head, then on February 1 I’ll post some concrete details here about the story, the technologies I’m using, and hopefully a timeline of when a playable product will be available.
Penrith was feeling a little bare. I have some friendly trees, a few buildings, even some random fences and water, but the ground was still pretty bare. When walking around it was a little tough to tell if you were even moving because the trees might be far off and since there are places where there is little variation in the color of the ground, it was sometimes fairly unsatisfying. So I created tools to add grass to my scenes. There’s only one type of grass at the moment, and the whole process is Super Unoptimized™ but it already looks 10,000% better.
I also turned on shadows for the screenshot above, so that helps. The tool allows you to basically paint on grass, and it works surprisingly well. Eventually I’ll need to add in multiple type of grass but for now I’m happy with it and will probably move on to something else.
I had a chance over the Thanksgiving holiday to sit down with my brother and talk about the game. There are, obviously, a virtually endless number possibilities when creating a game and picking a coherent direction can be tough. Talking it over with him really helped and we decided on a slightly new direction for the game. Since I started on this incarnation of the project I have been thinking of Lyridia as a multiplayer-focused game. I was doing this primarily because I thought that I would end up with a game that other people wanted to play. While this is an important goal, in order to keep working on this in my spare time I really think I need to make a game that I want to play. Hopefully it will also be a game that other people want to play, otherwise what’s the point? But I think it’s reasonable to assume that if I like it, at least some other people will too.
So here are the highlights of the new design for Chronicles of Tright: Lyridia.
- The core of the game is a single-player experience
- There will be a primary story that takes players all the way through the game with side quests that are not necessary but will enhance the experience.
- Multiplayer features will be added later
- Extra content (like instances and raids) will be available for those that enjoy that type of play, but will not be necessary to play or finish the game. Public areas, chat, an auction system, and other features are also planned.
- Choices matter
- The story will require you to make decisions that affect the rest of the game. This means there will be multiple versions of the same core story and multiple ways to finish the game. A reincarnation system will allow players to play the game over and over, making different choices along the way each time.
One big challenge is going to be writing a story that is complete and yet can be extended later if needed. Typically in an MMORPG if you want to add more story, or increase the level cap, you just create a new area and create a story for it. For this game, increasing the level cap or adding more area to the game means I have to modify the whole story to include the new content. I can still add side quest content without messing up the core story, but I don’t think it would work to add content for players at level 60 if the game’s main story ends for players at level 50.
Obviously this is still a very big challenge and will require lots and lots of planning to avoid having to totally redo things later, but I’m excited to have a specific path to follow, and hopefully that means progress will come a bit more quickly.
I’ve missed my December 1 deadline for a demo version of the game, but that’s due to the redesign. I’ll have to see just how much time it takes to fully flesh out the story, but hopefully January 1 is a reasonable time to have something playable up and running. We’ll see.
Math is just hard. I’m an educated person. I’ve never been afraid of math. But sometimes it’s just hard. Especially when dealing with 3d graphics. I fully admit that there things going on in the background of the game that I don’t understand. THREE.js does a great job of abstracting away much of the dirty work, but sometimes things come up that have to be dealt with at a low level and that can get downright frustrating.
Here’s what I’m talking about. I have been working on getting Penrith to the point that I can release a demo-type version of the game. That means adding objects to the world, modifying the terrain to be somewhat interesting, and testing as much as I can along the way. This was all going pretty well until two weird things cropped up. First, my player character started moving *very* slowly. This was confusing because the movement at each frame is based on the game’s framerate so that the speed at which the character moves should be framerate independent. I noticed it especially on my faster development machine. It turns out (I believe) that THREE.js caps the display frame rate to 60 frames/second, but this cap is not reflected by the Clock object. So if the game is running fast enough that it is looping through my main loop at, say, 100 times/second, then the delta on the clock for each loop is going to register 0.01. But if the renderer is capped at 60 frames/second, then at each frame the character is moving 1/100 of the distance he should move in a full second, but only actually doing that 60 times/second, so he movement speed is dropped to 60%. The bizarre thing is that the faster a machine is, the more noticeable the drop. If a computer was capable of looping 600 times/second, the character would at 10% of the desired speed. On the flip side, any machine not capable of looping more than 60 times/second will never see this problem. It was simple enough to just test if the delta time was less than 1/60 and, if so, set it to 1/60, but it was still frustrating to find.
Now, the more complicated problem. My collision detection system is still a bit of a black box to me so I’m thrilled when it works and slightly befuddled when it doesn’t. To make a long story short, I had to apply the world matrix of the parent of each collider object to the points of the triangles the collision system is testing against. Without this tranform the colliders were not rotating and positioning correctly over the rendered objects and I was seeing strange behavior. Again, it only took three lines of code to fix, but required several hours of testing to find the problem nonetheless.
In any case, math is hard and I’m still moving forward. I hope to have a version of the game up and running so that multiple players can simply walk around Penrith by December 1st. I think this is a reasonable goal given how close I am to that point right now.
The design of Penrith Forest is going pretty well. A big part of pretty much every game I’ve played in the last several years has been water features, so I thought it was time to try and tackle some water in Lyridia. I’m shocked to say it really wasn’t all that difficult, at least to do the most basic job of getting something that looks like water into the world. I have a large pond/small lake that now has water in it. It even has waves on it, which is quite cool. I need to figure out an easy way to make videos of some of these features because it would be much more effective to *show* the water gently lapping against the shore of the pond than just talking about it, but for now you’ll have to take my word for it that it is cool, and I’m excited about it.
The world editor is now back in business. I can add assets, I can move them around and rotate them, I can move the terrain up and down, I can paint colors onto the terrain, and I can save the results. That seems like a really small list of things that it can do for the amount of effort it has taken to create, but at least it works. Now it’s time to step back a bit and really design the game’s first area, Penrith Forest. I have a general picture in my head but I need to really know what I want players to be able to do before I just throw some mountains and trees together. Obviously the first iteration will be just that, and I’m absolutely positive I’ll make numerous changes as more of the game develops, but this area sets the tone for the entire rest of the game so I need to make sure it makes sense from the beginning. Hopefully my next post will have some screenshots from the world editor of Penrith Forest!
I have now converted all of the art assets for Penrith Forest into glTF files. Before I had a mix of .json, .fbx, and .gltf/.glb files. While I was doing this I created collider meshes for all the assets that needed them. I also added in the ability to load double sided meshes. By default meshes created by THREE are one-sided. This is an optimization that prevents WebGL from drawing triangles that are facing away from the viewer on the assumption that these triangles will probably get drawn over anyway. This works fine for most things but for very small, simple objects like grass and flower petals I need the material to be visible from any angle. This is accomplished by simple putting the word “(Double)” anywhere in the material name in Blender. This name gets exported and the object loading code looks at the name of each material getting loaded, and if it contains “(Double)” it sets that material to double sided. This only has to be done once, when the asset is loaded, so it shouldn’t have any real effect on performance and will allow me to make all kinds of foliage as simple planes.
The next thing I need to do is clean up and confirm/re-implement the terrain editing and painting code. I had this working at one point, but I’ve changed quite a bit over the last several week so I’m guessing it’s at least partially broken. Once this is fully working again, I’ll put some time into the design and layout of Penrith Forest.