daydream reports: let's make a node that you get ... #6397
Labels
No Label
1. kind/balancing
1. kind/breaking
1. kind/bug
1. kind/construction
1. kind/documentation
1. kind/enhancement
1. kind/griefing
1. kind/invalid
1. kind/meme
1. kind/node limit
1. kind/other
1. kind/protocol
2. prio/controversial
2. prio/critical
2. prio/elevated
2. prio/good first issue
2. prio/interesting
2. prio/low
3. source/art
3. source/client
3. source/engine
3. source/ingame
3. source/integration
3. source/lag
3. source/license
3. source/mod upstream
3. source/unknown
3. source/website
4. step/approved
4. step/at work
4. step/blocked
4. step/discussion
4. step/help wanted
4. step/needs confirmation
4. step/partially fixed
4. step/question
4. step/ready to deploy
4. step/ready to QA test
4. step/want approval
5. result/cannot reproduce
5. result/duplicate
5. result/fixed
5. result/maybe
5. result/wontfix
ugh/petz
ugh/QA main
ugh/QA NOK
ugh/QA OK
No Milestone
No project
No Assignees
8 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: your-land/bugtracker#6397
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
daydream reports a bug:
Player position:
Player look:
Player information:
Player meta:
Log identifier
Profiler save:
Status:
Teleport command:
Compass command:
this exists: https://content.minetest.net/packages/cheapie/areasprotector/
we had it on blocky survival, and that's how i got introduced to the idea of protection. i don't miss it in terms of how i interact with protection these days, but it was certainly useful for starting players.
pro: it's meant to integrate naturally with the areas mod that we already use.
cons: it had some bugs. block/area ID desyncs were possible, allowing people to occasionally delete other players areas. it allowed players to subvert some rules about protection areas (though those issues might all be fixed now?).
integration: by default there's 2 sizes of protection areas, neither of which align to
/protect_this
. it also doesn't give the advice and warnings that are requested in the bug report.overall: worth testing
It just stores area id in block's meta, and when block is dug, calls
areas:remove(id)
. Since ids are reused, you can place these blocks, remove areas via command, then wait for people create new areas and remove theirs.Maybe areas could have a timestamp or something (although it's uniqueness would depend on timer resolution and frequency of area creation/removal...)
We could just make a new item that, when placed, executes
protect_this
. Should be easier to integrate than changing the mod in question.another con of areasprotector: it requires a steel pick to break the node, meaning that new players couldn't move the area until they'd mined for a while.
another pro: if you punched the node, it would show you the outline of the area (similar to a WE area outline)
That should be an easy fix though
Perhaps name it "The Miocene Totem"
Wouldn't such a block be more or less a feature dupe of the markers (exept that you have to place two markers)...
Before joining YL I have tested some servers with these protection blocks enabled... I'm not really a fan of those (It was actually the absence of these mods which showed me how much more one can do with areas)...
I'd prefer a tool that guides you through the whole process (so you can protect multiple areas with it).
If no one else steps foreward, I can imagine to implement this.
Might be the wrong place to ask, but what are the oldest clients YL aims to support (eg. what's the formspec_version such a mod should work with?)
Some GUI solution could be nice, or integration into unified inventory (or our variation of it).
Also, showing borders with particles (that could be sent to specific player only) would make it even better.
How does that name have anything to do with adding a block to help with area protection ?
I've seen markers used improperly so many times but I love how markers work... for newbies the best part of markers is easily choosing y+/y- values - so nice and simple... but the whole protection this is just a lot for newbies... honestly tho? If someone has some knowledge they do understand it within a day and helping people that play for under a day really isn't worth our time... have seen such things in other games tho... the thing is if you wanna move it would remove it also - and THAT is key for me - because while everyone tells newbies how to /protect_this I rarely see anyone mention /remove_area
Miocenes can protect things right? Also, they have things to do with our lore.
A new player does not know anything about our lore. Such an item needs an unmistakable name that blatantly says what it does.
started writing a GUI for the areas mod (https://codeberg.org/tour-ist/areas-gui) Not too much to see there yet, I will call here once I think this is in a state where I need testers.
If I can get access to yl_areas_addons, I'll try to build up an optional dependency and add yl features (too close warnings, area upvote, ...) too.