Not all resources are going to be useful to you specifically, nor do they have to be. The problem here seems to be people falling into the void, because there aren’t spawns set up. This is supposed to automatically set up spawns unless overridden by an actual spawn point (this is my understanding of it). Again, just because you wouldn’t use it, doesn’t mean it’s not useful to someone else.
5 Likes
Cant you already just place a spawn point?
5 Likes
I mean I see how this could be a useful plugin for lazy developers, but I don’t think playtesting and realizing you don’t have a spawn, and then going back in and placing a spawn takes more than 10 seconds, so I don’t exactly see why this would be useful to many.
2 Likes
It can take more than 10 seconds. Especially on large-scale experiences.
Why can’t you just go to the model tab and insert one, then drag it to wherever?
2 Likes
That’s correct. I made it after falling into the void numerous times while creating smaller models with no base plate as I didn’t have a spawn point set. Although it’s effortless to create a basic spawn point, I found it practical to have this plugin working. At first I had it as a local plugin, but I decided to share it.
A major perk for me, was that the properties of the spawn point were already set.
It always teleported me to the middle of the largest part of my build, which was always the floor. If I had a house I would teleport to the exact center of the inside. I thought it might help other people. So I published it as a plugin.
Finding the largest part is not an efficient method. If you have large, invisible barrier walls around your map then it will place a spawn point on top of the walls. If that happened you’d have to move it to where you want anyways…
Placing a single spawn point is not a process like heavy scripting which will take you a long time, it is a minuscule problem compared to something like building an entire map. If you have trouble placing a spawn point in your map then you are just lazy.
You aren’t speaking for “lazy developers,” you’re speaking for yourself. @https_KingPie said it best:
I’m not saying anything about the plugin, I was just pointing out it is possible that stopping play testing, add a spawn, go back into play testing can take more than 10 seconds. Nothing else.
it divides it by the Y axis. But yes, a large barrier on the X/Z axis in size could potentially trick it
To those saying you can just place a spawn location, I find it as a quality of life feature. It’s why it doesn’t pop up in the toolbar. It just sits in Roblox Studio, invisible. You won’t need it most of the time, but like most of QOL features it’s just for special use cases, and can be helpful in those cases. Also, on massive experiences, it actually can take much longer to get in or out of the game. Not just like 10 seconds lol
For me personally I have seen really good results with the plugin. so far it hasn’t set a spawn point in a bad location. Most of the time, I forget I even have the plugin as its not noticeable. it helps in the background
1 Like
If i’m honest with you, great job doing this but; I don’t see myself using this plugin since I can easily just make a spawn point… 
2 Likes
By your logic, every single feature that isn’t clearly visible should have some stupid QOL feature.
Example:
- We should have a spawn location QOL because it’s too hidden!
- We should have a face controls QOL because it’s too hidden!
Have some common sense.
EDIT:
The spawn location button isn’t hidden at all, it’s in the model tab and goes over to the gameplay section, right there, a spawn location button.
I’ve just looked at the code for this plugin, and it doesn’t take the baseplate as its spawn position in the slightest, it takes the biggest part in the entire workspace, by using GetDescendants to iterate through every single thing.
This is HIGHLY inefficient if you’re using this on a game with loads of parts (i.e showcase games)
sometimes there isn’t a baseplate
Exactly, and the fact that the part has to be named “baseplate” for the script to actually work is super stupid.
that’s not true… the script doesn’t even assume a baseplate exists because it usually doesn’t.
Actually, hold on, what you’re doing is just checking the size of EVERY, SINGLE, PART, which is probably the most inefficient thing I’ve ever seen, and even worse you’re doing this each time the player’s character gets added.
This module shouldn’t be used in any games with two or more buildings, since it will take a hit on server performance EACH TIME a player joins the game.
there is debounce so its not “EACH TIME” a player joins the game. I tested the plugin on maps with like 10k part counts and it runs quite fast. Lua is impressive