Hi, I'm Calico, I go by she/it/they pronouns. I'm a jack of all trades in terms of game dev. Feel free to look around, maybe you'll see something you like.
So, landmarks/waypoints no longer have types. Instead they have a map of typed data components, like items do in 1.21. This makes it easier for map mods to know how to render a landmark from an unfamiliar source or addon - it only needs to know how to render the components it cares to, like a name, lore, or a color.
So, we added an item stack component (see above). It kind of blows us away that (afaik) no map mod uses stacks for waypoint icons. it's easy to render an item stack, and it's super intuitive on the player end. Marking a cave? maybe a pickaxe. Ore vein? raw ore. Spawner? Spawner.
Surveyor's whole gimmick is map save data that makes sense to multiple mods - and this is a perfect representation of that.
It also lets us elaborate on the vanilla convention of using maps on banners to add map markers. We added a new command that creates a waypoint at the specified position that has the name and pick stack of the block at that position. So you can literally look at a spawner and type /waypoints block, it'll autofill the position you're looking at, and you get a waypoint that says "Mob Spawner" and looks like a mob spawner.
We added some extra config fields too - one to specify block entities to allow in landmarks (allows seeing banner patterns on the map! take that vanilla!) and one to specify POIs to automatically create block landmarks for (lodestones, by default).
So if a mod uses POIs to record, say, the position of its warp-stone-esque blocks, you can just add the POI ID to the config and instantly get map markers for them WITH names and icons that look like the warp stone. No joke.
Even if they don't use POIs, it's an easy PR!
The other breaking change to waypoints is that they're now unique by the player's UUID (or a generic UUID if it's a server-wide landmark) and an identifier. So mods pick their own uniqueness scheme on creation like blockpos [minecraft:poi/lodestone/150/63/-50], or incremental [antique_atlas:marker/bed/aqua/5], or UUID [automap:f3f2e850_b5d4_11ef_ac7e_96584d5248b2]
It keeps things readable and is nice in commands like /landmark [id] remove thanks to identifier prefix suggestions. The new keying also finally allows two landmarks to have same blockpos (phew), but also no blockpos at all! (e.g. a faction claim landmark represented by a chunkpos instead)
Next: more brainstorming use cases for this new system, and then we need to implement dynamic loading/unloading of terrain data to avoid the current unlimited memory footprint.
Hello, so I'm MerchantPug. You likely know me through my mods, either as a maintainer or as a main developer.
Why?
Origins Forge was honestly a nightmare to maintain, even the Fabric version has been a nightmare to maintain. Neither myself or Edwin had the motivation to do the necessary rewrites to get Origins Forge bugfixed or updated past 1.20.1 Forge to NeoForge.
Origins expanded in scope way past what anybody would've expected, it's essentially working with a toothpick foundation (Origins Fabric) that can't support what changes its making. Origins Forge being a partial rewrite of what was already a toothpick foundation, as well as being built on Forge, another toothpick foundation, as well as Minecraft, there's just a toothpick coalescent!!
There's also just the aspect for me where I don't want to just be known for Origins. I personally don't really want to work on things for a community that has spat in my face and would do it again, I'm not saying everybody is bad, but like, some of y'all are the actual worst.
I don't really get much satisfaction working on my Origins related projects, and I'd instead like people to give other things I've created/will create a chance. My plan for Apugli is to discontinue it too, with the goal being getting parts of the library in Origins itself. TooManyOrigins will hopefully exist as a data pack/resource pack combination in the future.
Hope for the future?
I'm personally passing the torch to the people who are trying to get Origins to work with Sinytra Connector. I'm unsure how far they've come, but I'm hoping that it'll be finished.
If somebody wants to make a new port for newer versions of the game, I wouldn't be opposed to that. I'd just try to learn from our mistakes and avoid rewriting the entire project. The imo main issue is just that Origins Fabric is already a pretty non performant mod by nature, and getting that to stabilize more is just a lot of work.
If eggo wants to pursue multiloader with Origins, I'd be happy to oversee what's being done, but again, I need a long break from a project that has brought me many mental issues over the time I've worked with it.
Can't really announce anything about the game I'm planning right now, due to it only being within the planning stages; but here's the first few bits of it. I will eventually run its own tumblr once I start developing it, anyways, here's some very early spritework for the game.
Been working on re-doing textures for my Moobloom mod, Bovines and Buttercups, the top are the old/Mojang textures (Buttercup and Pink Daisy), the bottom are new textures.
areudirty
annaxmalina
baratheonpilled
izzy806
andulkaphoto
tangentwithtanner
