Azelf reports: Electrumese Sword alt attack ( ... #5346
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#5346
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?
Azelf reports a bug:
Player position:
Player look:
Player information:
Player meta:
Log identifier
Profiler save:
Status:
Teleport command:
Compass command:
I accidentally used my electrumese sword's alternate attack on some of the chests while trying to place it into one of the chests, and the attack destroyed two chests in my base and deleted their contents (one was a chest of raw meat and the other one contained spare gear). I checked, and they did not enter the TP tube because there's none of the gear at the other end and testing on the test server proved that the contents do indeed get deleted.
It's always annoying when that happens
tag when lol
i need to get back to the color-able shared chest update at some point.
in the meantime, fixed in integration:
311a8f4dcf
technically this is a dupe of #4406, though that one's blocked on an upstream PR whereas this one got fixed in integration
Positions
156,-4162,-3059
155,-4162,-3059
Those chests are not in the backup, they changed too often ever since. But there's the log.
We'll refund the chests.
QA
With chests not exploding anymore, it won't take long until people build themselves a nether base out of those. We probably need to make up our mind what should happen in such a case. However, the chest doesn't explode anymore.
why not make it where chests can't be placed in the nether ?
Because there's no reason to disallow placing chests in the nether. Plus, it doesn't solve the basic issue
there's lots of other things that already don't explode, and e.g. locked chests take only 1/2 the iron that the shared chest does, so this doesn't open up any new exploits.
this is live
I'm not entirely certain, but I think I found them. Now I need the input of Azelf which ones exactly
The items were refunded