Open Xect0r opened 4 years ago
borzaka
commented
4 years ago No point using the latest release version, always use the latest development build.
Please, post your spawn config here.
Have you tried reloading the server/map?
How did you test your spawns?
Xect0r
commented
4 years ago I've been using mostly the Development Version because i figured it would contain a few fixes that the Latest Release one wouldn't have.
Here's the config for Train which is having this issues, although all default maps seems to have the same issue (This is a testing config, hence the 6 bomb spawns on the side of B site): https://hastebin.com/pocivoxipu.lua
I've restarted, reloaded spawns after saving them and even changing maps.
The way i tested the spawnpoints was both through enabling this new spawns in a live environment and also by checking with the !edit where i would spawn (As well as letting the bomb explode).
As you can see on this images, the spawn is set as Never bomb-carrier but i still manage to spawn there and get the bomb planted somehow.
I'm honestly completely lost, not sure what to do and can't find a way to fix it without having to use the default spawn-points which are extremely broken (Stuck in places, spawn looking at the wall, spawns outside of the playing area, etc)
Xect0r
commented
4 years ago Been doing a bit more of testing and no matter which version i try, it results on the same issues.
Definitely lost on this one :/
borzaka
commented
4 years ago The spawns in the latest development version are fine. No known big issues. Maybe you are not updated the spawn configs after updating to the latest development build? Maybe you only updated the .smx and other files, but not the spawn configs.
I have no such problem. I have already made my own spawns, and I managing multiple community retake servers without any big issues.
I haven't tested your spawn config, but it looks strange; you have only one T spawn with type 1.
What do you expect? You setup no bomb carrier spawns.
The error appears when the plugin can't find suitable spawns for the bomb carrier: aka a "Normal" or "Bomb-carrier only" spawn that is inside the bomb site.
Try to disable the autoplanter plugin during testing.
Xect0r
commented
4 years ago Alright, did a fresh install with the latest SM, MM and Retakes using the development version and still got the same errors (Even when trying to setup the spawnpoints msyelf).
Considering that you're mentioning that the Spawn Types are wrong (Even though when loaded through !edit it shows 6+ spawns for Bomb Carrier Only on B site), i'm starting to think that for some reason the Plugin might not be saving properly? I've done spawns both locally on my own computer and on my GSP Environment but still get this behavior.
Tried removing the AutoPlant Plugin and same results, completely lost on this.
Thanks for spending some time trying to assist me on this btw, really appreciate it.
Expected behavior
Spawn correctly on any of the Bomb Carrier Only Spawnpoints established and saved via the !edit menu when you have the C4 and not on Normal or Never Bomb Carrier spawnpoints (Therefore, causing the bomb to be planted on weird places).
All of the above without falling back to default spawnpoints when there are spawnpoints setup properly.
Actual behavior
Once the round starts, players have a chance to spawn correctly on another site (This is okay, that's the intended way). For some reason, it will in most cases cause the plugin to use the fallback spawnpoints.
Literally added 8 spawnpoints inside the marked zone in the minimap on de_train (On the sides, in the middle and in the back on top of the train). None of them would be detected, would spawn and plant the bomb automatically (Due to AutoPlant) on Upper B or B Ramp (Or well, any other spawnpoint marked as Never Bomb Carrier)
Steps to reproduce
Other things i tried
I literally tried everything to diagnose this and make sure it's not just me being bad at setting it up:
Current Setup (Plugins)