Ygor reports: The respawn screen should didp ... #642
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
6 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: your-land/bugtracker#642
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?
Ygor reports a bug:
Player position:
Player look:
Player information:
Player meta:
Log identifier
Profiler save:
Status:
I'm under the impression this would cut into the priest/portal mechanics (at least their balance), therefore a no fix.
But what if someone wants to teleport to their bones and a different player rushes in and uses the portal directly after them and closes the first portal, then the first player is forced to spend another gold to open the "right" portal again... yeah, that's bad behavior by the speeding player, but I don't think that would justify something like this.
Still no fix.
Talked with Alias, actually I'm wrong here, Alias does want to give you the coordinates but also change the death screen itself to a Your Land specific one. We're talking something that needs C++ though, so unfortunately it can take a while until we get this fixed.
Temporarily you are shown your death coords.
The death screen is hard-coded on the client side.
There's a moribund PR to change this:
https://github.com/minetest/minetest/pull/8014
Looks like they want to close this feature and it requires not only a server change, but also a client one. That's something we can't roll out ourselves I'm afraid.
playing around with the mt api a bit I stumbled across an idea for this...
It feels very hacky, but it works well on my singleplayerworld...
A
minetest.close_formspec(playername, "")
could be added to close the engine death formspec before, butshow_formspec
removes it relieable too. (Note that this would require to move theshow_formspec
into aminetest.after
again)It still needs some checks to make sure the player who wants to respawn is actually dead...
And a camera repositioning. Atm it's in the bones block in my singleplayer testworld.
Another point are players who leave while beeing dead... They would be redirected to the default death formspec when rejoining. But YL seems to have it's own system to deal with dead joining players (at least I logged off dead but after relog I was alive on spawn)
Not sure if this is fixed on YL already, but I am able to send a dead player any formspec. So if there is no respawn option in this fs, the player will exist in some sort of undead state until relog. I remember beeing in that state twice when a guy attacked popular mt-servers and created terrible lag on YL. You can take stuff from bones, walk around and create log entries like that...
ACTION[Server]: Server: singleplayer tried to interact while dead; ignoring.
(Alias saw that, that's why I found out I'm undead...)But beeing dead without a respawn option is another issue than this one.
Might work. But then the player closes the screen - and forgets about the coordinates.
IIRC there was a book planned that the priests could sell(?) with death coordinates. Guess the priests could use more income...
only one formspec can be shown at a time, showing another automatically closes what's already open (which is honestly a big flaw, as anyone who's ever had the game reset the password they were typing when the server list loads. there's an engine issue for that somewhere).
yeah this is to avoid a bug, where the death message is over-ridden on join by the server news message, and the player then cannot respawn.
#1099 (cf. #2478, #3097, #4634)
this is a decent proposal actually, i'm embarrassed i never considered it. it does inherently create a race condition whereby the player may see two death messages if they dismiss the client-generated one quickly enough. however, other than momentary confusion, there's no real downside to that.