-
-
Notifications
You must be signed in to change notification settings - Fork 32
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Respawn Location Bug #418
Comments
Hmm. I can't replicate that right now. Do you have any other settings active? Screen.Recording.2025-02-14.at.5.02.15.PM.mp4 |
I didn't really change any configs but I can send you what I am doing later when I am home |
Excuse my late response i kinda forgot |
also why does the spider spawn just erase surrounding blocks |
Also /ob phases does not tab complete without perms but op |
Please share the output of |
island spawn is of course set. But still it sometimes makes me respawn in the default generated world. |
Also it would be cool if /oba setspawnpoint would also take in the rotation instead of only the coordinates |
Thanks for the feedback. I'm busy during the week but I'll look at these when I can. When mobs spawn their hitbox will clear any blocks so that they won't suffocate. Spiders have big hitboxes. Noted on the phases tab. I still don't know why you would spawn in the main world. It maybe that the /spawn is set there? If a safe spot cannot be found then the algorithm tries different spots and eventually tries /spawn. |
Thanks for your attention to this case, i now tried disabling the default world and setting it to oneblock which worked. Now people will spawn on the spawn island at least because of worldspawnpoint but the problem with the respawn location being blocked and then players being sent to the worldspawn still persists. So now players spawn at the world spawn when something changed at their island spawn location until they use /ob go again. Maybe on respawn the plugin does not check if the respawn location is valid. |
Also for future recommendations / bugs, do you want me to create a new issue for every single one or can i continue listing them here when finding ones? Here for as long as you did not respond: Recommendations
|
Great! Thanks. I may break these off into separate ones if needed, but I can start work from this. |
In regards to: [Essential] Spawn Island being editable after being set. rn you cant easily change name / flags -> Island owner being server would be nice When the spawn island is made, any owner is removed because it is now a spawn island. This is by design. Any editing or flag setting can be done by Op when on the island like normal though. |
Regarding: [Bug] Block#getLocation().clone().toHighestLocation().add(0, 1, 0). to ensure that they will spawn even when blocks were placed / removed on the spawn location on respawn or validate spawn location There's a complex algorithm that finds a safe spot. Blocks like cobwebs are not safe of course. You start with a home location on top of the block (you can change it by sethome) but in your case it doesn't seem to find a safe spot around the block. I need to investigate more. |
2 similar comments
Regarding: [Bug] Block#getLocation().clone().toHighestLocation().add(0, 1, 0). to ensure that they will spawn even when blocks were placed / removed on the spawn location on respawn or validate spawn location There's a complex algorithm that finds a safe spot. Blocks like cobwebs are not safe of course. You start with a home location on top of the block (you can change it by sethome) but in your case it doesn't seem to find a safe spot around the block. I need to investigate more. |
Regarding: [Bug] Block#getLocation().clone().toHighestLocation().add(0, 1, 0). to ensure that they will spawn even when blocks were placed / removed on the spawn location on respawn or validate spawn location There's a complex algorithm that finds a safe spot. Blocks like cobwebs are not safe of course. You start with a home location on top of the block (you can change it by sethome) but in your case it doesn't seem to find a safe spot around the block. I need to investigate more. |
In regards: [Bug] Islands that were removed using /oba delete are not erased neither available for the next user using /ob (only after restart) They are. Erasure is done using NMS so if you are floating by them the blocks will be locally cached on your client. If you relogin then you'll see them disappear. Yes, island spots are not reused until the server restarts, which should be done daily for production servers. This is by design right now. |
In regards to: [Essential Request] Warnings in chat for when a mob that removes surrounding blocks spawns (on first sound cue) so that players can remove / evacuate items that are nearby Okay. I'll come up with something. Only blocks should be broken. |
Make this one separate please: [Bug] When being trusted on a players island it will add your names's Island in /ob homes instead of the actual islands owner. Updated when changed by owner tho Good catch. |
This one should be separate too: Bug] /oba delete showing every island the player is trusted on instead of only his own. (Confusion for admins to delete his island) Thanks. |
Good idea for this one: [Essential] Team Members who are online and on the island wont know when the block phase ascends. Maybe show the Title to all memebers on the island or introduce a Bossbar withprogress for players on the island I like the boss bar idea. |
Expected behavior
When the spawn location is blocked by blocks or anything else hinders the player from spawning at the location, the plugin should check again for the highest block at the OneBlock Location
Observed/Actual behavior
Currently when someone places 2 blocks on top of the OneBlock players spawn in the default world for as long as they use /ob again
Steps/models to reproduce
Create a OneBlock
Place 2 Blocks on top of it
Die
Use /ob
Die again
BentoBox version
BentoBox-3.2.3.jar
Addon -> 1.18.1
Plugin list
Other
No response
The text was updated successfully, but these errors were encountered: