Peregrinatio

The Server Tick

Now that I can track the ticks in the database and have the ability to change config from the web administration I can start working on the tick itself. Which is, at it's heart, no more than a simple timer that fires a bunch of functions when it

The Server Tick Foundation

So now I suppose is where I start the server tick. Today will be interesting. I have an appointment at 1:30 so lunch might be the end of work for the day depending on what happens after that. However, I would like to get the server tick code started

Wiring up the debug mode care systems

Today I have to make the calls I couldn't make yesterday but I hope to at least get the base care systems rigged up. There's a lot of UI as well as Inventory and minigame design required to get them fully implemented but I want to

Displaying care stats, Server side care system

Today I have a few things I need to do around lunch time but when I left off I had a fairly solid foundation of the UI to start working on the care system. I didn't wire up the slime's data quite yet. I'm

Starting the Care Systems

Glad I took the rest of yesterday off, I would have got nothing done anyway. I felt like crap for the remainder of the day once I got home. Feeling a lot better now though so back to work on designing these care systems. Then at lunch I need to

Finishing up the Outside for now

Not much time to work today, I have an appointment to get to. With the time I have had this morning so far I set up a few things; There's less chance of a player seeing the dark void now. The cityscape is still a bit bland but

The City Outside

Today I fixed the traffic lights, cleaned up the code a little and found that I was indeed just too tired to be doing that last night. I unchecked monitorable on some of the area2D nodes responsible for stopping traffic. Once I finished with the traffic I got started on

Player Anims and Slime AI

Well, yesterday I got the slimes loaded in and wandering around with 2D navmesh and a basic state-machine based AI system. I also got started on the player animation and ran into some issues with the padding on the sprite. Today I went and set myself up with a doctor

Populating the player apartment

So now that I have a player loading in and walking around I have started loading the slimes in. They have no autonomy or... really anything outside of being a picture. The player doesn't animate yet either. Also the way the apartment loads right now is a bit

Loading Scripts on the Server, Lightening the load on the API

I know that players should have no more than 6 slimes active in the current setup but I am running some stress tests on the save system and I have found it overwhelming the API. If there are hundreds or thousands of slimes being saved the API wont be able

Slime Part Scripts on the Server

So I wrote the loader and cache system for the server scripts, I didn't get all of them loading and caching, only the faces. It's been a long and disappointing day so I guess the stress got to me a bit. I'll finish the

More slime loading.

I'll be working on the client first today, adding some particle emitter constructors so I can add particle emitters to the script loader. Once I finish with that I will load the slime scripts on the server and then I am done with the loading for the time

So, we have the slimes on the client and server, now what?

Well, I don't really have a clear picture of this point in development. It's kind of a limbo between getting the networking set up and the slimes loading and getting started on the care systems. There are a few things I need to do, important things.

The Compositor Rebuild

This will be interesting. I need to rebuild the compositor system for the slime sprites, but I need to do it in Godot. There's at least a couple ways I can handle it, one way relieves the server of some of the work and does most of the

The Slime Updater

To start out I have added a new field to the part models, Discovered(bool). When a slime is generated with a part, it will be marked Discovered. If a part is discovered then it can be cached in the client's slime part cache during updates to make

The Updater

So now I am building the update system. It will pull data from the Client Update endpoints on the API, compare that data to locally cached data(if any) and update as necessary. This should allow more rapid updates to slime and player data as well as easier rollback if

Game Server <-> Client Communication

First thing I did today was some yard work so I don't expect a whole lot will be done but I have done one important thing. With that I can just leave it running in the background while I work on the Game Server and Client with 2

Continuing Game Server networking, loading and saving data.

Today I hope to have the networking between the Client, Login and Game Servers all worked out and the client transferred over to the Game Server after logging in. Then I will make a basic test apartment and start working on loading player data and player slime data on the

Starting on the Login Server, Game Server and Client

Well, I have started on the Login Server, so far so good. There's some differences in the way networking functions now but it's not so different that I am having a hard time with it. I've got it hooked up to the API and

Finishing up the Generator for now.

Today I think I will be done with the generator for a while, I have it generating some pretty solid sprites now and have not seen any bugs in any new slimes in a while. I am sure there will be some and they will be found by Moon testing

The Slime Tester

Over the last couple days I wrote a tester which allowed me to identify and fix a lot of bugs in the compositor and some in the way I uploaded the sprite parts to the DB. The tester has a toggle to show a background texture in order to check

Further R&D on the Generator

There were a few more bugs that I have had to fix over the last couple days but I think I have mostly got the core working as intended. There are a lot of moving parts involved so I will spend a few more days debugging and writing tests endpoints

Adding Parts and Fixing Bugs.

I've added some new parts, found that I forgot to account for filename overlaps. There's a bug I need to fix. I also need to write a helper function to generate the upload path for the generated sprites from the API. They shouldn't ever

First Generator functional, time for tests

Today I managed to bang on the generator enough with my wrenches to get it to actually generate a complete slime from the applicable parts in the database. There is only one part per category and one palette right now, we need to add some more so it can be

The Initial Slime Generator

So far I have a good chunk of the generator developed, I suspect I will have it complete tomorrow. I've created the models for Illnesses, Traits and Personality Traits since I need to generate the slime with traits and I wanted to get the illness in while I