This project has been deleted.
This is an ecosystem of components designed to interact with each other in order to collect analytics from a Minecraft client. It consists of a minecraft mod that runs on the client (server side coming soon) and a server that the client connects to and sends data such as player positions and server uptime.
No followers yet
Once you ship this you can't edit the description of the project, but you'll be able to add more devlogs and re-ship it as you add new features!
Finished on adding integration with mcsr for some player statistics if they have used speedrun mods
worked on adding integration with the MCSR api for tracking player stats if using the speedrunning mods (data is published publicly by default)
we now use the api to fetch the server list instead of hardcoding it into a config file
+ quite a few bug fixes & reducing the number of api calls
finished writing the api endpoint for server grabbing
started work on the analytics page for each server
page currently has icon, sanitized motd, player list
sidebar now has indicator of if a server is online and if the server has the mod installed
started work on the UI, added per-server map and got the rest of the UI (current pages) to a satisfactory point. map now scales with nearest-neighbor past the resolution provided by the map server (so you can zoom past level 3, currently max set to 6)
Moved a bunch of very generic stuff over to a library mod which will make it much easier to use in other mods. Also it adds this small frog to the main menu.
This devlog includes time spent creating the croaklib mod that stores common code between my different mods such as update checkers and certain cosmetic things.
moved the config for the encryption key into a .env for the server and the config file for the client
FINALLY FINISHED MOVING OVER TO RUST
The server is now fully reimplemented in rust up to the point it was at in python (plus quite a lot of reorganising and cutting down on unnecessary data and messages)
The server also uses mojangs official api to authenticate the users, which means that the server never knows any login info but can still fully authenticate the clients
Check out https://github.com/meeplabsdev/connectorlib-server/commit/288dafadc9c7502bbec78f10d0c5c5b6c47df1c0 if you're interested in seeing all of the changes made but the summary is that rust server now logs:
health
hunger
breath/air underwater
saturation
exhaustion
experience points
protection level from armor
gamemode
fps
ping
current status effects
message content
message type
from player
to player
dimension
biome
location
heightmap pointmap
selected slot
item names
item counts
item slots
item data/nbt/components (durability, enchants, etc)
location
velocity
dimension
sneaking
sprinting
swimming
crawling
grounded
fallfyling
nearby players and their locations
joining a server/world
leaving a server/world
death locations and timings
when doing the position data logging for the player we now also log positions of all other players within a 1024 block cube centered on the player
added ClientPosition to log player positions
renamed ChatData to ClientChat
changed the floats in postgres to be half-precesion (float4)
begin work on visualizer webpage - move over to nextui + vite + vite_actix + actix (rust backend) and implement POC map using leaflet (OSM world map) + set website theme
updated mod to work with rust backend and added support for a couple more messages, massive code changes to support msgpack instead of raw json, encrypted messages, new inbound/outbound method of encoding classes, removed auto-reconnect for now (will reimplement), authenticate on EVERY websocket join not just some of them since tokens are not carried across sessions now (per-session auth)
added to the client so that it can now decode the msgpack messages back into classes and refactored some code so that inbound and outbound messages are clearly seperated on the client side
began to get the mod working with the new rust backend, got msgpack serializing working but not deserialization yet
also implemented the mojang server join flow so that it can authenticate that the client is sending data from a real account, which prevents modified clients from sending bogus data
add coloured logging and identity authentication with the host-controlled np-p private key and aes-cbc with uuid and username checksum
the expected value (given a nonce and an iv) is now calculated for the IdentityRequest, used to help verify the authenticity of a client
now working on the rust implementation, added the ability for messages to return value back to the client
Started working on the rust port and using messagepack instead of JSON, have the handler selector working for message routing and the messagepack decoder working. Handler selector and messages module are generated at build time.
mainly modifying the chunk messages system, but I will be moving to MessagePack instead of JSON soon
Set up project in SoM (work logged on hackatime was adding websocket auto-reconnect to mod and fixing some bugs server/db side)