Featured ABPS - Acid's Bot Placement System 1.1.1

I have zero issues using this with Fika. You'll need to provide more information - preferably in their Discord in my thread.

My bad mate. Your mod is fine. I've found the broken one

Thanks for this mod

Group Size 2 =

Leader PMC

+ 2

The group size is the amount of followers, not the total size of the group. This is confusing but I haven't fixed it yet.

That’s done the trick, thank you!

ABPS doesn't do anything with zombies

Did you disable them in the config? Did you turn off vanilla for them in the config?

Does changing the config in the middle of the raid while the game is open affect spawns?

ABPS handles rogues vanilla spawns by default, you don't need to mess with the config.

Changes in ABPSConfig require a server restart to take effect. Changes in F12 denote whether or not they take effect in the current raid or next.

Okay, thank you for the reply. Love your mods btw!

Once they are spawned my mod is done. Looting bots only gets them moving around their initial area if there is loot, you'd have to wait for questing bots

Starting scavs should spawn a couple seconds after the raids starts to ensure that PMCs spawn first. If you lowered your map caps then there may not be room for them.

Acidphantasm, what is the recommended bot cap to not block spawns for bosses and other special bots?

On my CPU numbers of bots like 15-25 is making FPS stutters and game unplayable for me. In SWAG+Donuts that maybe worked differently I had to set up SCAV limits to about 4-5 and PMC to 2-3 to have playable FPS for me. So about 8 PMC+SCAV was the safe limit and rare stutters as bosses and other type of bots like raiders etc had their own cap in SWAG+Donuts so I only focused on setting SCAV+PMC spawn cap which is at around 8 overral (I refuse to play SOT even with a f#@$ 2 bots as this s$#@ stutters from time to time even on empty map xD) so how it is with your mod and what is the safe MAX BOT CAP to set to not block other bots?

If you lower the cap you just need to lower the PMC/scav initial spawns counts. The scav waves will utilize the new cap space.

If you're lowering the cap I would avoid enabling PMC waves though, as scavs may never be able to spawn.

Bots can only spawn in spawn points, period, no matter what mod you use. They don't activate if there's no point.

This mod does not add new points, yet.

Pre raid controls scavs, kinda, but not really. Its random. ABPSConfig controls PMCs/bosses.

Great, that's what I concluded from my testing as well. Thanks!

I have zero issues with marksman scavs, so if you're having an issue with it you're probably either spawning too many PMCs or you lowered the map caps so they don't spawn. It works just fine for me with default configs.

I also dont have issues with the switch for raiders. They aren't guaranteed to spawn, it's the same chance as vanilla.

I've extended map caps, though maybe it's true about pmc horde config... Is there any chance for u to add guaranteed at least snipers spawn? Like init spawn pmc, bosses, snipers and only then leftover slots for scavs, I've already set to init 10 scavs and postponed to like +80% pmc wave timer, though didn't notice any changes. So looks like that it's kinda hard to play with pmc waves and with canonical sniper spawns.

Also tell us pls: are raiders and other special non-pmc bots counted towards scav limit?

And is there any chance to respawn snipers or they are only for init spawns?

Because you configured it wrong or iinstalled it wrong, or you have something like SVM overwriting it.

But I didn’t configure anything. I just installed the mod and started the game. I do have a SVM, but there are no features that would affect bots.

Conversion doesn't exist anymore. Right now it's a flat 50/50 but I can make that configurable.

Unlikely, but possible. I have no plans for this, especially this early in development.

I can't fix this. It's literally the same app I use in APBS and it doesn't get detected like this one does.

Submit it to your AV for a false positive - because I can't do anything about heuristic antivirus detections. It thinks it's malware because it happens to read/write things to a JSON file. If you don't trust it then don't use it.

I don't know how many more times I can say I have zero control over this. I can't make it go away without just deleting the config app, and most people like APBS/ABPS *because* it has an easy to use config app.

Latest version, 1.1.1 isn't flaged as malware in virustotal.

Published version on github and checked version on virustotal link are not the same. I suppose the checked version is a Github pre-tag 1.1.1 or an error in the process.

File hash checked in virustotal published link is ad3bfe1b3a11fff1ea673328c65319b0788830bf5c67d6c6f57a21c4e147a8e7, but Github release version 1.1.1 has 04eeabf8adb5e324e1e1dbf6a6d1a53df962686b997c1a3e21413b0e1fdd5222 sha256 hash when download, so they are not the same file.

Maybe a variation before the build process, I don't know.
https://www.virustotal.com/gui…b997c1a3e21413b0e1fdd5222

This is the correct link to a virustotal analysis with no flags.

But I recommend don't trust me and download de file (where no antivirus should detect anything) from Github and uploaded manually to virustotal if it is true by yourself.

As I said, I literally can't do anything about false positives. Sometimes it happens and sometimes it doesn't. Its going to vary release to release.

I'm very much over the constant false positive flag discussion and it's making me want to stop developing this mod.

If you don't trust something, don't use it.

I was trying to help you out, man.

I think you're going into a spin when you see the word antivirus in a comment.

Let me simplify: version 1.1.1 is NOT been tagged as malware by any antivirus.

I really appreciate the effort and time you put into the mod.

That's probably because I've had like 50 people ask about this in the past 3 days. It gets old very quickly, especially when it has nothing to do with anything I can control.

I know it's not flagging now, but I also can't say why it was flagging before. It'll likely flag again in a future release.

I know you're trying to help. I'm speaking in general. The more times this is brought up, the less likely I am to continue work on it. Its so much easier when you do a server mod and it never flags for anything because it's typescript.

go to anti virus settings and turn off real time protection

A self-proclaimed "war crimes fan" tells you, "You know that message telling you the file you downloaded is a Trojan, forget about it and disable what is probably the only security system you probably have on your PC".


I haven't the knowledge or time to say what acidphantasm is using in the code to trigger the antivirus alert, if it is a dependency or a bad practice, but I prefer not to use this version to disable my antivirus.

I already had the experience to be infected with a Trojan and I prefer to wait for an "undetetected version".

Take care of yourself.

I can't tell you why it's flagging. Its the exact same base as my app for APBS.

Everytime I do a new release and have to rebuild the app, it gets flagged initially and goes away eventually because all these vendors use heuristic detection which always follows the practice of "it's an EXE/DLL in a zip, must be a virus"

If you don't trust it then don't. But the source is linked to the hub page and can be reviewed or manually built.

I unfortunately cannot fix their crappy detection from detecting nothing as a virus, even though I wish I could. The only real thing I could do is purchase a trusted certificate and sign my app with it - but I'm not paying $200-500/year for a certificate when I do this in my spare time.

I'm sorry if I was misunderstood, but I wasn't criticizing you or your work. In fact, I still use the previous version of your mod because I find it very useful.

As I said, I don't have the knowledge or time to figure out why the alarm is triggered, but normally, downloading executables or libraries is allowed even if they're not signed; it's the execution what is blocked by windows if the file is not signed (not the antivirus). So, I'd neither spend money buying a certificate. Antivirus neither omit the check of files signed by a certificate. Would be a bad practice blind trust in developers, don't be offended.

What I don't agree with is telling a user who receives an alert from their antivirus saying they've downloaded a Trojan "turn off the real time protection and go on". We have to be a little more cautious in life and ignore the first person who says that, especially without justifying their response. Because if we like risk, we can always include whatever triggers the antivirus as an exception rule and not disable the real-time protection that's supposed to protect us against that and any other potential threat.

From a place of ignorance and interfering where I'm not supposed to: if you suspect the alert might be from the .exe in a .zip, have you tried extracting the .exe from the zip and serving it separately?

Anyway, in version 1.0.1, the zip had an .exe inside and it didn't trigger the antivirus. So, either it's something random in the build process (and I don't believe in randomness), or it's something that's changed since version 1.0.1. Maybe in the next build the alert disappear, shouldn't be the first time.

I have no intention of separately distributing the configuration app, especially because the source is required and I cannot put two source links.

I don't agree with their solution of turning off your AV, but I can't directly fix the flag. You can whitelist the app, or not use it. That's pretty much your choice until those vendors stop flagging it. Maybe the next release won't flag, maybe it will. Its not something I'm going to dedicate any time to solving - because I can't.

go to anti virus settings and turn off real time protection

Whoever is running the server is whose changes take affect.

go to anti virus settings and turn off real time protection

thank u

Just the host I believe.

It used to be that way in past client versions but it appears that BSG now allows multiple bosses per zone.

I can maybe look into that but I make no promises.

ABPS absolutely explicitly sets spawn chances for bosses, stop using SVM to do it. Its also not capped at 25 so I'm not sure where you're getting that from.

I want bosses to spawn with a 100% chance, which I’ve configured using SVM. However, when launching the game with your ABPS mod enabled, bosses no longer spawn reliably—even though the Progressive Boss Chances setting in ABPS is disabled.

The settings show:

• Minimum spawn chance: 25%
• Maximum spawn chance: 100%

Yet, even with progression disabled, bosses don’t spawn at the 100% rate set via SVM. Does this mean ABPS still overrides these values despite the option being turned off?

Am I understanding these settings correctly? If so, is there any way to make SVM and ABPS work together for guaranteed 100% spawns?

Did you look at the config tab on the mod page?

There's a server side and a client side. Client only handles progressive chances, server handles it if you don't use that.

Thanks for the help! I didn't realize that's how it worked. I appreciate your responses.

me too

It tends to happen with client mods unfortunately. They usually stop getting flagged after awhile, but any new updates usually re trigger the flag

I know it's safe because I wrote it, but ultimately it's up to you. The code is linked on the source and you can review it or build it yourself if you'd like.

Yeah I know its safe, just wanted to make you aware its flagging up. No drama.

p.s. I am grateful we now have a bot spawning mod

Windows won't even let me interact with the file

yeah I do that

Yes

PMCs will spawn in a player spawn position if possible, if not possible they spawn anywhere a bot can.