Pantheon
- 4 Devlogs
- 10 Total hours
A custom item and content framework for paper servers
A custom item and content framework for paper servers
Devlog #4
I added in what will soon be version Alpha-0.2.0 the new equipment API.
It includes,
Saddles, Helmets, Chest plates, Leggings, and boots.
The next step is re-writing the sound API prototype in common and implementing. Features soon to be added also include food and weapons
Devlog #3
So I got a bit carried away and decided that it could be a good idea to add velocity support. Currently, and what it is planned to do is pack hosting and generation, the actual logic for item is still ran on the backend server and it is not included in velocity which allows for code separation between common, velocity, and paper. I also started making presets for equipment and added custom font support. I also removed minecraft 26.1.2 in favor to 26.2 to support new features. The next step is still the equipment api such as custom armor and elytra’s. I think the next step after is tools. Linked is a demo of the custom font for ranks, note that it does not generate the rank texture but could be a good idea in the future.
Devlog #2
So, been a few days and I have been able to test and improve the current item API.
We now have:
Devlog 1
So, I have been working for a while in the mc plugin scene and each and every time a few things often come back when doing custom servers, mainly custom items. While the process of making one is easier then ever due to the changes in the last few years it is still quite annoying, mainly having to manually write json or copy-pasting while changing a few values. You also have to make sure everything matches up back in java. If you are working with modern modding api’s, such as neoforge and fabric, you will get a tool called DataGen which helps writing the json for you with the minimal amount of lines for diverse things such as loot tables, item models, etc. So I decided to make one for paper and to have a custom item related classes and also have the option to build the resource pack on the fly for quick updates. It is currently messy due to the fact that I am directly interracting with the POJO that mirror the json of a resource pack, I am planning on making a nicer api to make the process faster and cleaner.