ElusiveAstropath reports: I traded with someone around 3 ... #3974
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
4 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: your-land/bugtracker#3974
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?
ElusiveAstropath reports a bug:
Player position:
Player look:
Player information:
Player meta:
Log identifier
Profiler save:
Status:
Teleport command:
Compass command:
Lookiong at the log, everything weems to be in order with the transfer. However:
What happened was they do a Q drop trade and because the price paid was something the seller already had in stock, it probably (some) added to her stack already and just like that, no way to really know if the full amount was paid or not. Paranoia ensues due to not being able to clearly see after the fact what exactly happened.
event logs that are visible to relevant players are an interesting idea, but that's somewhat tricky. information can't be available forever, like rollback logs, or we'll run out of memory in a month. if too much is in the log, it's hard to find anything old, unless there's some sort of search mechanism. assessment: great idea for a feature, but it's a huge mount of work to get right.
There's https://gitea.your-land.de/your-land/yl_trade which I still haven't properly looked at, but could avoid situations liek that.