Peregrinatio

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

Nearly finished with this design phase.

I've been spending a bit of time every day writing the books to get a broad overview of the year one systems. As of now I have only one more system to get outlined and then I can get back to work on Monday writing code starting with

Back in the lab

I've been working in the books, planning out systems for the early game and a few for the later game as to make sure I have these things in mind while designing and developing the earlier systems they will interact with. I also received a letter about an

Another Sabbatical, what a year.

Here comes some ramble; So, this year I had so much planned. I accomplished some things but not most of them. There is one thing I really need to focus my attention on; Geruterra. I've got a couple side projects I will keep working on now but my

Quirks of Minio

So as it turns out whenever I try to access my minio bucket for Geruterra through cloudflare tunnels from the main API it has permissions issues. The Image API using the same settings has no issue. I must be missing something but I have no idea yet. I will set

Maintenance and Updates

So I've spent some time while waiting for my wrist to heal trying to get a more solid image of this game together, I have also been working on the servers as always. Today I finally spent a little time working on the API devops again, getting a

Sprite Generator Front and Rear

Well, I finished up testing the sprite generator with static sprites, got front facing and rear facing working as intended. I'll still need to get animation in and working, that's going to be 2 frames I think, since the generator at the moment is python based,

The Sprite Generator Part 2

So, the last few days I have been setting up a server. Finally found one I could afford that allowed me to dump some VPSes and this one... really spooky celeron-based dedicated server I had. I did all kinds of interesting things like set up a Kubernetes cluster and figure

The Sprite Generator API

So the next thing I want to do before I get into the dreaded test writing is build my Sprite Generator API. Good news is I found the one I wrote a couple years ago on my office server. I've got it wired up to the object store

Geruterra Serializers

On to the serializers, I am getting started with the player models as they are less complex than the slime. This could take all day. Despite the weird name, the Django-Storages package is pretty nice. The documentation is a little... odd. But that seems to be the case for most

Geruterra Models

So, I've been building the models for Geruterra and setting up a versioning system so the client can self-patch most data, allowing the team to add new item, slime parts, whatever dynamically without the players having to download patches or us having to build them. I went over