debiankaios reports: if you fall down log out and r ... #1505
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
3 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: your-land/bugtracker#1505
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?
debiankaios reports a bug:
Player position:
Player look:
Player information:
Player meta:
Log identifier
Profiler save:
Status:
Teleport command:
Compass command:
i think he means that player velocity is not kept between sessions.
if you want to "fix" this, the following code would work:
I'd prefer to save player related values not in mod storage, but on the player.
We could even use https://gitea.your-land.de/your-land/yl_settings
actually, player metadata certainly makes as much or more sense than mod_storage.
it'd be easy enough to use any of these solutions.
i'm also not entirely certain that this would even be worth doing, whether it sounds like a good idea or not. it's going to be incredibly unreliable in laggy situations, both in terms of storing a meaningful velocity value, and because sometimes it takes a moment for things to load when a player logs in, and their client will just nullify the velocity anyway.
i wonder if anyone's ever proposed to the minetest devs, that y-velocity be maintained when a player falls onto an unloaded region of the map - and to keep players from jumping if they're standing on "ignore" nodes :\
apparently this is the way it used to work, but it didn't work well? not going to dig up that closed ticket.