don_flymoor reports: The priest send me to the wron ... #107
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
2 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: your-land/bugtracker#107
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?
don_flymoor reports a bug:
Player position:
Player look:
Log identifier
Profiler save:
Status:
Hi,
your bugpreport was investigated. I have a recorded death of yours at 23:47 UTC, you filed the bug report at 23:53
The location was 2104,15,1300 where the priest should have sent you. Can you show me ingame, where to the priest sent you instead?
Is it possible the priest did not open the portal for you, but for someone else and you mistook it for yours?
To avoid confusion in the future, from the next release on the priest will mention in the logfile where to portals are opened and say in the public chat whom it is for. Thanks!
That's what he said:
Might have been the knockback bug. We disabled the custom knockback now and hope it's solved.