Arabella reports: node replacer tool can even re ... #1560
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
5 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: your-land/bugtracker#1560
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?
Arabella reports a bug:
Player position:
Player look:
Player information:
Player meta:
Log identifier
Profiler save:
Status:
Teleport command:
Compass command:
Maptools nodes need to be replaceable by a creative player, but should not be by a normal player.
You can't get a maptool "item" drop by replacing it, they all drop "".
The "solution" we used on blocky, was to protect the area.
@flux maptools are used in a few places in nether (such as Corridor Corridor), and you can't protect any area in nether, thus players can still replace nointeract and other maptools in those places
proposed solution: admins should be able to protect areas even in the nether, such as the Netherlands corridor.
Why? I cannot think of a situation where someone nonstaff needs to replace maptools nodes?
IMO it would be best if we added maptools nodes to the blacklist of the replacer
if they're added to the blacklist, then staff won't be able to use them w/ the replacer, either, and there's absolutely cases where staff will want to.
i think this would be resolved by adopting my replacer redo variant. i need to do more testing w/ the creative replacement tool, though.
We'll eventually need to come to a technical comparison between the now-updated replacer mod of Sokomine and the rewrite by flux. Currently we're using the swissalps version and there are plenty of others out there. I think we'd do MT a favour if we tried to unify them.
But: https://xkcd.com/927/
the various different replacer implementations are each imperfect for different contexts. SwissalpS and Sokomine focus more on creative servers, while trying to also be useful on survival servers. i provide separate tools for both creative and survival, which have distinct capabilities. however, SwissalpS and Sokomine allow you more control over what the tool does for both creative and survival players; i'm trying to re-imagine the tool as something that is less magic particulary for non-creative players.
probably, it should even have wear, though i'm still weighing that decison. i'm gating that decision until i decide whether i want to create a mod that will prevent tools from "fully" breaking, and just become useless, until they are repaired (in a possibly special manner).
drgn accidentally replaced the maptools nointeract blocks in the netherlands portal area. they immediately reported the issue, and i fixed it w/ rheo (
//r
), but we should try to figure out a better solution.Adding wear to the replacer would from my POV be almost criminal. Don't hinder builders!
My version of the replacer supports blacklists for blocks.
the version we use (SwissalpS') also supports blacklists, and we already use those. honestly, i like Sokomine's version more than SwissalpS', mostly because the latter has insane "modes" that can easily result in terrible accidents while doing normal things. my minimalist rewrite also supports blacklists, though via a different API. replacer balancing is complex.