Open comments for this post
Today I built my first simple portfolio.I had never really learned frontend development before, but today felt different. I actually enjoyed working on something personal: a small, minimal and efficient portfolio that represents me.I know it is simple, but that is exactly what I wanted. I like things that are clean, direct and minimal. No unnecessary noise, just something that works and feels mine.
I learnt how to better use CSS (i knew 0 css before this project).
I used iconify icons dependency for the icons.
I implemented a simple localstorage save for the theme color preferency.
I honestly did not expect to have fun writing CSS, but somehow I did.
Open comments for this post
Today I spent around two hours working on a new feature for Caesar, my Minecraft staff plugin: Staff Mode.
The idea is simple: when a staff member runs /staffmode, the plugin saves their current inventory, armor, location, and gamemode.
Then it clears their inventory, puts them in creative mode, gives them vanish, and lets them do staff stuff without affecting their normal survival items.
At first I tried saving the inventory directly into a YAML file, but restoring it was not working properly. The data was there, but the player was not getting their items back correctly.
After debugging it for a while, I changed the system to serialize the inventory into a Base64 string. This makes the saved data easier to store and much more reliable to restore later.
Now, when the player exits Staff Mode, Caesar reads the saved data, restores the inventory and armor, teleports the player back, restores their gamemode, disables vanish, and cleans the saved data from the file.
This was not a huge feature, but it was a good learning experience.
Open comments for this post
Today i started making my own Minecraft plugin for admin management implementing an sql database
Open comments for this post
Today I worked on changing my Minecraft tag plugin to work on a Velocity network.
I started splitting the project into different parts:
- one plugin for Velocity
- one plugin for Spigot
- one shared module for simple shared data
I also started learning how Velocity and Spigot can communicate with plugin messages. I do not fully understand everything yet, but the basic idea is that Velocity can send a message to the Spigot duel server, and the Spigot server can answer back.
I am still figuring out the best way to connect everything, but now the project structure makes more sense than before.