Raphael Larsen

I finished the block_library and saw another engine using binary greedy meshing, which I started cloning.

I compeltely forgot about logging. Anyways I've been working on a way to fix the weird uv problems by using a texture array

I finally figured out the bug (more of a PEBKAC error) which I could've fixed if I read the docs better. I got some jank working, still not entierly sure whats happening though.

So I have a framework for the block library thats theoretically done, it should now properly lookup attributes from the block library, however i'm unable to load the block library for some reason.

So after I setup the basic thing I started setting up an external blocklibrary asset so that I could map voxels to textures and materials without baking it into the binary. But I'm been having a ton of trouble actually using the blocklibrary. At first I had threading issues because bevys assets arent nativly threadsafe. Now I'm trying to figure out how to map the textures and materials to Meshes.

I did a bunch of stuff integrated ndshape and block-mesh, and greatly simplified how chunks worked. I finally got a working prototype.

I started to setup baking visibility into the voxels to efficiently mesh, but it got really confusing with my current setup. I also started looking at some other voxel engines and I'm switching how a few things are setup to make this easier as well as using some external crates I didn't know existed.

I've switched back to linear arrays as a representation. I also managed to start rendering some basic chunks however I've started switching some of the systems to be more reliant on bevy.

I started octree representation of chunks and starting meshing.

I've finally finished pallet chunk and array chunk. It took like super long because I generified everything. It was super satisfying but if i'm going to finish i think I gotta code rough.
Heres all the stuff I did:
Voxel:
A wrapper around an id.

Space:
I define a global voxel position as a ChunkPos with a VoxelLocalPosition (bound from 0 to chunk length)
I defined some traits to help with VoxelLocalPosition, CyclicBoundInt, BoundInt, and Wrapper that provide methods to ensure that the internal value doesn't leave the bounds.

Chunk Storage:
VoxelLocalPosition -> flatarrayindex
ArrayChunk, just a array of voxels.
PalletChunk --
Pallet - A sorted array of Voxels
PackedIndices - A array of numbers that pack smaller numbers (indices pointing to Pallet) in them using the smallest number of bits.

You can see more info in the Repo.

Next im gonna define a volumetric object made of chunks that will eventually turn into the world/ other objects made of voxels.

I've finished the PalletChunk and ArrayChunk implimentation as well as chunk space.

There is a bug where my first two devlogs seemed to have lost their time and now that time is stored in Since Last Devlog. I want to see what happens if I make a new devlog right after I made the old one even though I dont have more time.

I've finished the utils required for chunks. They are super polished. I have a rough structure for both flat chunks and for pallet chunks. You can see more commits in the repo.

I've made a number of changes however I haven't really finished any features. Notably I refined the bit_struct to have more methods to handle changing its internal data. I also am working on some other traits to help impliment a BoundInt that must be with a range: this is for local chunk coords which must be between 0 and 15.

I added a tool to store voxel pallets as a data efficient bit struct.
Anyway now I have to go actually create all the important systems instead of spending way too long optimizing.

I wanted to try bevy out, this is a snake game made following this tutorial: https://mbuffett.com/posts/bevy-snake-tutorial/

This project was majority me messing around with bevy, and rust. I tried to really organize my project in a way that a fully featured game could be. I also exported it for web.

Thanks for checking it out!

Ive been mostly trying to host a server free online so I can test It I just cannot seem to join a server no matter what I do.

I've added a way to access punched/proxied addresses through a thread_safe vector. I've also added this to the testing of the Client api.

I've reorganized a ton of stuff. Separated the Godot bindings from the general purpose server. Separated the Listings from the server, and just went over everything with a comb.

Implemented a way for the Godot API to send signals upon task completion by polling a reference in the main thread.

I cleaned up the testing script and added timeouts to client requests. Then used those tests to find a lock out.

I then fixed the lockout by separating the locks so the first one was dropped when the second one was used.

I've setup client code, wrote some tests and fixed some bugs.
I'm gonna start doing more devlogs on here.

I have finished setting up the server-side implementation and begun create a godot API for the client.

Switches over to tonic for RPC functionality.

Setup simple WS connection split into Read and write.

I had previously setup a server to use use http, but that was really messy and a WebSocket connection would be far cleaner. I also had not made a rust program before so that was good practice.

I added a bomb weapon, rifle weapon, bullets. I also made movement of weapons independent from robot movement.

I changed some internal systems. Then added a basic main menu.

I added P2P hosting on the local network.

I also added the robots to teams however their pathfinding is a bit off.

I setup the main towers with some placeholder art and setup 2 simple pathfinding nodes for a bot.

Today I added some of the more complex components for the robots such as NavReceiver, ActionEmitter, and ActionReceiver (I'll give them more descriptive names in game).
The three I referenced can override the navigation component, for ease of use I a NavHandler component as an inbetween to handle the absense of a component. I also moved a lot of the NavComponent Logic into the NavHandler.
I additionally added support for Hitboxes and Hurtboxes, their interaction with the HealthComponent, and added an interaction with the DeathComponent to handle zeroed health. Because I plan on allow multiple HealthComponents I also added a HealthHandler that acts as the go-between. Both handler components are obligated to be in the robot.

I also more throughly organized the filesystem and tried to make sure everything followed some standards.

The screenshot is the ViewCone for the camera using procedural raycasts. I just think it looks cool.

The UI was bugging me and I started changing it, but didnt finish today.

Also although this is the first devlog I had been working on this game for 2 days beforehand.