issues
search
CodeF53
/
Horse-Buff
Makes Horses better by removing stupid things
Other
10
stars
6
forks
source link
End Portal Travel
#10
Closed
CodeF53
closed
2 years ago
CodeF53
commented
2 years ago
What we know:
prior to running
startRiding
the player is successfully moved have a perfectly functional horse entity
after running
startRiding
, the player is permanently attached to the horse, following a relog the horse is gone, but all changes to chunks have saved
this state will be called a bad mount from now on
using
/data get
after getting a bad mount always returns the same data for the horse, no matter where you move it
Idea spitballing for possible solutions
Given everything is fine before we call it, perhaps
startRiding
is failing
[ ] force player interaction with horse entity, so we aren't the one calling the startRiding
[ ] make a new startRiding method
Perhaps we have a bad instance of the horse at this point, using
/data get
after getting a bad mount always returns the same data
[ ] after teleporting the player, look for horses near it and remount onto those instead
[x] (really stupid) teleport both horse and player to the overworld again
[ ] teleport the horse after the player, then move the player, then remount
[x] send uuid instead of actual entities and get them in the method
Proper solutions that would take more than an hour to try.
[ ] painstakingly go through all entity attributes of the horse and player to try finding the cause of the buggy mount, then fix the bug.
Boxes checked are things I have tried
What we know:
startRiding
the player is successfully moved have a perfectly functional horse entitystartRiding
, the player is permanently attached to the horse, following a relog the horse is gone, but all changes to chunks have saved/data get
after getting a bad mount always returns the same data for the horse, no matter where you move itIdea spitballing for possible solutions
Given everything is fine before we call it, perhaps
startRiding
is failingPerhaps we have a bad instance of the horse at this point, using
/data get
after getting a bad mount always returns the same dataProper solutions that would take more than an hour to try.
Boxes checked are things I have tried