Skip to content

March: 16

  • 04:11PM

    The journal integration was broken during the migration but I was able to resolve it. Well kind of, there is an issue with the graphs that I need to wait on, that or I might just fork it and resolve it myself.

  • 05:01PM

    Deep dive into the avian engine for bevy, what I did notice was that it is a bit young and needs some additional improvements. The major issue that I see moving forward is enabling the simd and enhanced-determinism, I will try to get both added asap. We can start with the simd, since I did add 128 integration earlier.

  • 05:42PM

    The plan is to keep the bevy npcdb integration between the discord mud bot and the actual bevy game itself. This will be really interesting to see the integration between a MUD and the ISOMetric game, almost a weird experiment to an extent. We can go crazy and have a side chat that exists within the page too. So many ideas, but the execution time and getting things working is such a pain.

  • 06:51PM

    The edge functions will be our restful api call to the clickhouse, I am thinking this would make things easier to understand and build from. Later on, I do want to update the jedi crate to handle the clickhouse integrations as well. Okay so the edge functions are able to query the clickhouse, now we need to make sure the axum-kbve has the integration for The dashboard is already hooked up so that only admins can access it, so that should then make it easier for us to restrict the proxy calls to the clickhouse. After this integration, we can use this to resolve the argo dashboard nginx issue! Later on, I want to expand kong around to further lockdown the requests that get made. Well actually that might not be too much of a pain since kong already can verify the jwts, so that might be easier then I thought.

  • 09:31PM

    We currently have around 50~ issue tickets, I am going to try to create some more to help with the flow of the repo. There could be some prompts that I could write up to help with the information, maybe using the security In addition, I am thinking we expand the github dashboard, so that we have

  • 05:26PM

    Laptop has been returned, I will miss all but with the $5500 back in my pockets, I will just invest it. My score for the laptop will be a 9 out of 10, it still is the best laptop on the market but definitely overkill for almost everyone. I did not get a chance to try OBS streaming on it, but the next time I get the M5 laptop, I will.

  • 06:45PM

    The actions should be ready by tonight, there are only a couple more things to resolve before we are back to a full scale pipeline. Biggest issue right now is the token management and the 2nd biggest issue is the file alter triggers, both of which are just time based.

The majority of this day will be preparing the game jam and making sure everyone is on board! The VS Code live share does make it easier, to be honest. I think all software should be done in a duo. Having a buddy while doing any type of software is a huge benefit, I think pair programming should be the future, add in an AI bot or two and now you have a full team.

The JSON Map is what holds all the information for the tileset and editing the game/map data directly through the tileset editor, Map Editor and Dev Tools.

There is still an issue with the vite bundler and the pathing, which I still need to resolve for the https://kbve.com/tools/travelbox deployment! The best move might be to deploy the assets using an absolute location from a s3 bucket.