niceride reports: 'Replacing nodes of type "pipe ... #4289
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#4289
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?
niceride reports a bug:
Player position:
Player look:
Player information:
Player meta:
Log identifier
Profiler save:
Status:
Teleport command:
Compass command:
When placing i.e. SGG blocks for layout, and patterning off a certain orientation of existing nodebreaker to replace into the layout. Worked in 117, bug in 118.
note also broken for "pipeworks:deployer_off"
probably #1702 (comment)
c.f. #4236
the current behavior is intended, in order to prevent the "infinite pickaxe" of #1702.
in order to allow replacing nodes conditional on the permissions of the user, we'd need an API which the current replacer mod doesn't provide.
on the other hand, my replacer redo won't remove a node if you can't place the replacement.
So what is this restriction on replacer redo and mesecons items addressing? I don't understand, there's a bug in replacer redo not updating pipeworks? Is it critical enough to disable all this functionality for all players?
Yes, unfortunately. Having a tool that goes around the placement mechanics IS bad and may create unexpected combinations and things may go wrong. We don't want that.
there's no such bug. there's a bug in the current replacer fork that we're using, which allows "replacing" a node even if you aren't allowed to place the replacement node, which turns your replacer into an infinite-durability instant pickaxe.
i'm trying to sell my own replacer fork as a solution which avoids the issue by trying to follow the builtin API as close as possible.
How can we test your replacer fork, is it live on the test server?
it's on my own testserver i've set up to test a bunch of new mechanics i'm working on. it's "fluxtest" on the public server list. poke me if you need help getting started. note that pipeworks is not on that server, nor is there any sort of machine restrictions.