- This topic has 18 replies, 4 voices, and was last updated 8 months, 1 week ago by
.
-
Posts
-
Hi MeseCrafters! There is a new update for MeseCraft ! This is the first update for 2023! You will now see this update hitting our github, servers, an
[See the full post at: Feature Update for January 2023!]I like the new mailboxes. Noticed some unknown items around my farm though. Turns out the blue delphinium flowers aren’t showing up.
The item string (name of hte object) in the game changed, so you’ll likely have to find them all over again.
Nice, we can finally shift+click loot chests. Been wanting that for a long time. However I think that we should have parity with things like armor-stands and auto-crafters. I would love to shift click those.
@mesecraft I developed the miner’s helmet, lighting updates, and such. Feel free to send bug reports my way. 🙂
I updated the post with the right mentions. I assumed @dcmenche was your account since it was posting about your server.
🙂 welcome to mesecraft!
The auto-crafters were included in the shift-click update. Armor stands are on my list but will need more work. I don’t think the listring functionality will work for those since each slot can only contain one type of armor. I’m thinking it needs a button to equip/unequip, which I think would be more useful anyway.
Note: Any node that you already placed might have saved an old formspec that doesn’t have shift-click support. Try digging and replacing it to get it working.
Can we fix this by registering aliases? We have some more name changes coming that could affect people more. The new ones aren’t just flowers, but whole chests worth of items that could be lost. I think an alias for the old name will cause the node to be seamlessly replaced. I haven’t tested it yet, but I did test an item I was holding was seamlessly replaced with the new item.
I just haven’t been adding aliases because I feel like it creates more maintenance required to add the backwards compatibility and I’ve been more focused on getting things setup for a more long-term and trimmer base of code. It does suck in the short term to have things break, but since I still consider this as an alpha-stage type of project, I haven’t been too worried about it.
The aliases could be used to support MTG namespaces though which might add more compatibility to mesecraft modules for other mods, but it hasn’t been a huge concern. I understand why it’s frustrating, MisterE was talking to me about this as well.
The unique namespaces are also a Minetest ContentDB requirement. They were getting on me about it about how if I change parts of a mod I can’t refer to it as the same mod anymore if it’s within MeseCraft on the contentDB. So I’ve just decided to give unique namespacing to anything that is changed or within MeseCraft. Long term, it would benefit the game to have its own namespacing too, better branding, and the unique namespacing should help more name changes in the future since we’d have our own spaces to work within.
It’s probably not perfect thinking, but that was the goal I was aiming for. I just haven’t been taking the time to account for depreciated name strings. The community here has been pretty patient with that and I appreciate that, but I can see how its frustrating for players and server operators.
I’m not saying it’s the right way to do things, I just haven’t been able to be bothered by it. It does kind of suck though, I appreciate you bringing it up and I can see how it’s a problem.
- You must be logged in to reply to this topic.