It was far more verbose as it had to include a lot of error checking, and fetching of commonly used data.
#Banished mega mod guide iron ore code#
It's a nice feeling to delete all the C++ code that was previously used to setup actions. (Is it bad that I feel like I'm writing assembly code but the instructions are more than 3 letters long and the registers are named nicely?) It's a nice step toward being able to make new objects in the game without having them hard coded. It's not the fanciest thing or the easiest thing to read, but it's functional and gets me where I'm going. The script compiler uses the C++ class and its serialization function to properly parse and use the action. finished using this interact, someone else can have a extend the script, all I have to do is write a simple C++ class that exposes the action and its parameters. is the object being "IdleInteract", walk to and Length, 0.0) And it has a debugger! Two days! Yay!įor a simple interact where a character is idling, it looks like this: Plan idleInteract And in two days, I had a functioning script system that could tie the actions together and use simple stack variables. Mostly by simplifying and removing lots of features. I'm pretty sure this is the first time I've brought code back such a large amount of code that I deleted and found it useful in another manner. I could have built it with my existing serialization system, (which looks something like JSON) but it would have looked ugly and verbose, been hard to use, and difficult to debug.Īnd so I recovered my scripting code that I deleted over a year ago from source control. And per object in the world, I wanted to be able to chain them together to allow unique behaviors. So instead, what I want is the engine to provide the simple actions, CreateEntity, AddInventory, WalkTo, PlayAnimation, etc. If the rock is huge and you need explosives to break it up before using it, I don't want to have to specifically write that in the game code either. If I want sparks to fly when hitting a certain type of rock with a hammer, which might start a nearby tree on fire, I don't want to have to write specific C++ code for that. But this time around I want the option of more variety. In the last game, there were just a specific set of these written for specific categories of objects, but in general they were shared heavily. For each thing in the world that can be used, this needs to be defined in some way. Walk to some location, play an animation, add something to inventory, create this other object, play a sound, spawn an effect, etc.
It comes down to a simple list of actions.
The situation is how villagers will interact with objects. I've had a desire to move some code into data. But having access to all the revisions of code I've written in the last 10 years is pretty amazing. On a totally different note, I had a pretty amazing experience with source control that I haven't had before. This time around I've been extending the game engine, and laying foundation for something that's better to work with, and will hopefully be just as fun. I feel like I just have more done, but maybe not? When I started Banished I had nothing, and spent 10 months working before I had the game in a playable form. Despite code refactors and bug fixes, it feels like I'm coming up to a critical mass of systems and the game will come together into something.
Why is the there still a random crash while background loading!? (I already 'fixed' that once.)īut that's okay - it's good to fix bugs when encountered rather than let them slide. Why is no one picking up rocks that are close to trees? Why isn't that object drawing it's selection when selected? Do you ever get the feeling that work on your video game is coming along to slowly? It seems I've spent the last month slogging through issues and bugs that come up as I make progress toward a cohesive game.
0 kommentar(er)
