When you're ready to publish, use VIDE:
http://www.riintouge.com/VIDE/

Follow this guide for custom content:
http://www.tophattwaffle.com/packing-custom-content-using-vide-in-steampipe/

Nice man, sorry to hear about previous map. Thats always depressing when you lose somehting you poured hours into. Though you do learn alot so the 2nd map is usually the better one anyways!

Its because your mod is conflicting with the server mods. I understand for some people that is frustrating but I always recommend people use minimal mods when on Sernix. Mainly either weapons that we dont mod and or custom scopes which should work for most part.

There are a few reasons why we host our own mods:

-They're universal to our server so all players see the same gun/models. People in the past used skins that made bots stand out like crazy, like red/pink textures.
-Our mods have been optimized a ton to reduce crashing because we push the limit and some workshop mods are using 4k textures/skins which can use up to 400mb of memory for a single weapon vs our 5-12mb.
-We add non-vanilla weapons as their own standalone weapons but most servers do this now but many of them are buggy, don't have proper 3rd person world models etc.

Quantar, screenshot isn't showing for me.

引用自 Budd：

Just tried Karkar and Dust2, min spawning distance causes more wacky spawns than the old code. Might have to roll back or try something else..

The main drawback is during a counter/finale when medics are down, we incidently spawn as a group alot of times due to squad wipe by explosion. There was a fighting chance we could carve our way back if we made a long train rushing back. Now the enemy simply appers in the middle of the train and we all get shot in the back, front, side, etc

Dust2 and or Karkar are NOT using CQC settings. The only change I made was adding dust1 to the min spawning so all other tests you ran were basically the standard code afaik.

Current CQC maps:
bunker busting
cargo redux9
caves coop
chateau tunnels
congress coop
dust coop v1_1
game day
gizab
inferno
launch control
nightfall

I didn't make that dust2 version but mine was buggy so I scrapped it. Ill add it to CQC settings.

Also dust 1 and dust 2 I just made it so they should be slightly increased from base CQC settings but still less than our default settings.

Also I agree on the valley of intensity. I think we can emulate this better with wave spawning but ultimately the long-term vision of AI director controlling intensity based on variables will be key.

引用自 🎄Hodor🎄：

Have you tried spawning smoke grenades at the current mass bot spawn? Not tried the tweak yet, but in spectator mode yesterday on that invasion map I've been seeing bots spawn endlessly 5 meters away from a player leaning behind the wall....


With smokes the gimmicky feel won't be so obvious for players, plus it gives them a few seconds warning to vacate the area to a safer spot or rejoin his squad.

Bots after the bot buff walk through the smoke towards the players anyway, not like in the past where they sit blind. Gives player time to react to a crazy close spawn instead of thinking "wtf magicians" and be overrun before he can aim or speak to his squad.


(this 5m spawn on invasion was before your adjustments above)

Spawns are very random with lots of variable calculations and not static enough for a smoke grenade. Bots can currently spawn as close as 8 meters when out of line of sight (LOS can be blocked by a sliver of a pole and or glass and is not measured by what is on-screen for the player). So squads of players have a bigger umbrella spawn protection. Though I've seen some odd spawn cases of course and I'd have to spectate more to really debug those and see if they are bugs or bad map spawn design.

Okay made some quick adjustments:

dust_coop_v1_1 now should have cqc spawns (this actually decreases min spawn distance which is the opposite of what youre asking but read below). Also the finale spawn SHOULD spawn more vanilla (basically instead of 1 point back, it should be 2 spawn points back.

Also the delay for bombers has been slightly reduced on cqc maps.

The reason we want to decrease min_spawn_distance on smaller maps is because what may happen is if the spawns are too strict, the bots spawn crazy around the map but also really close to a player normally due to the LOS logic (think of a ledge or a pole blocking LOS and permitting spawning in the sweet spot of minimum distance to player. Now this can still happen but the spawns are less likely to be redirected aggressively, meaning theyll spawn vanilla.

This can still be majorly flawed so I may have made it worst.. just let me know the results next time you play.

EDIT: Now that I think about it, its still going to be likely flawed and or worst since the vanilla finale spawn has a semi-broken spawn. Ill increase min distance spawning to mitigate.

Sorry I didn't address the spawn issue head on, I was focusing more on our spawning.

Modding spawn points in hammer is a big no no.. the effort to make the edit, recompile the map, build cubes, pack it, and upload it, then verify you did it all right else rinse and repeat isn't worth the fix unless its substantial and or can't be fixed another way.

Improving spawn points further has been a thing I wanted to do but is a ton of work. Right now for dust I can adjust minimum distance specifically for that map which I probably did already but can do further.

For future, two ways:
1.) Manually create logic (at least finale spawns) to spawn bots around specified points for maps with crappy finale counter attack. This is tedious work but since only some maps are broken, it wont be too bad. Basically if vanilla finale spawn point for bots is F, make it B since B is the best spawn point that closes distance gap and is also still a fair distance away.

2.) Longer term amazing way. Introduce nav spawns again. The problem with nav spawning though is there is over 2000-5000+ potential spawns to loop through each time for each bot death = lag. So a logical method would be to create spawn arrays at the load of the map and separate spawn by distance to point. So if players are assaulting point A, bots nav spawn only around A, then B, and so forth. This will hopefully break the spawns up into 100-500 spawns per point which may be too much still and also may vary per map.

The other issue with nav-spawning is many maps embed their .nav file into the .bsp file which tells sourcemod: "NO NAV FILE FOUND", I'll have to extract each one out server-side to get them to work properly and must do this for all future maps.. just tedious thats all. First is to write the code logic which shouldnt be too hard but testing, debugging, tweaking all takes time. I can probably worst case scenario cap the nav-spawn amounts.

Engineers creating spawn points can be accidental and trolly/annoying. I'd have to program a toggle to disable spawning on engineer points but even if I did that, most people wouldn't know where the point was even unless it was a very communicative team-working server but we have to think about the server that is not very communicative which can cause annoyance/confusion etc..

Engineers already have a big plate.. we need to spread roles around and giving squad leaders the spawn point perk gives them more of a role. With team waves constantly spawning, that role becomes more apparently.

How about this:

-We add a separate deconstruct All for barricades and jammers.
-We add a deconstruct [Target] (whatever you're aiming at that you built). Target gets a refund and if health is < 75% then only half points back, full points if a jammer regardless of health, only one jammer can be built since its a backpack.
-Jammers take 1 second to deploy and refund

So we have to remember that spawning on the point during a counter was how it was before months back.. The issue with that function was it was too easy and the probability of failure goes down dramatically and basically entirely on certain maps.

You can literally camp on a counter attack respawn and just kill 5 enemies a minute and you're actually contributing to the counter attack because there is only a finite amount of bots so it helps your team recover.

Overall I understand the concern and widely the experience varies per map among other factors.

I think the happy medium is wave based spawning. Heres some ideas I came up with that are fairly easy to implement.

Wave based spawning:
-Switch wave base spawning for both teams (logic will be different for bots and will be used for future bot select spawning).
-Security team utilizes scalable spawn time for each wave that loops continuously
-Allow players to toggle respawning off (default on per death) - medics do not nullify respawn if reviving, players must toggle off and risk missing the wave.
-Squad leaders see how many seconds left and how many players are spawning on them.
-Maybe spawning on team leader during counter. Less likely though because now that players will be spawning in waves, theyll have higher chance to inflict damage to enemy and coordinate an assault back to the point.