Engine bots

[leileilol]

Is there any advantage an engine-side bot could have with functionality over a bot based only in QuakeC?

- Opportunity for an AAS system
- Separate item weights, personality for each bot
- useless things like making something ELIZAey for bot chat
- This list is a silly brief retread of Gladiator Bot features
- no hackery up of mods to put a qc bot in (Testing convenience? doesn't seem effective on menu-based stuff like TF, and FVF...)

No, this isn't a Globot vs Frikbot discussion. It's something rarely explored further regarding Quake...

[Junrall]

- Increased ability to detect surrounding terrain and terrain surfaces?

[Electro]

Seperate item weights can be achieved via qc, in fact that's preferable.

Same goes for personality files, can just parse external files, I was doing this for shockbot.

[Team Xlink]

- no hackery up of mods to put a qc bot in (Testing convenience? doesn't seem effective on menu-based stuff like TF, and FVF...)

I like what you mentioned there, you can use it in any mod without QuakeC editing for the most part.

[Dr. Shadowborg]

I'd advise some form of customizable ability to use items / buttoncombos via external files for Painkeep / TF / Duke / Quake2 style items and also stuff like "double tap then hold to use jetpack" moves. (see hellsmash super jump move for the last bit)

[Junrall]

I'd advise some form of customizable ability to use items / buttoncombos via external files for Painkeep / TF / Duke / Quake2 style items and also stuff like "double tap then hold to use jetpack" moves. (see hellsmash super jump move for the last bit)

An engine side bot using external files would most definitely be an advantage. Very customizable.

[Spike]

A downside of engine-side bots is that they don't understand the rules of the mod.
Which means they can never play CTF or CuTF.
Knowing which weapons the bot already has may also be an issue if you want sensible item weightings.

Routing is a definite advantage for engine bots though. Easier to manage nodes, routes, etc. Having said that, the bot still needs to know how to activate/open doors and things.

Primary advantage of engine-side bots is that you can more easily track when the bot last saw quad get picked up, and time rearrival to get it when it next respawns, rather than just looking at the item regardless of whether the bot was within hearable distance.
Stuff like that.

[Urre]

Make builtins for navigation, do rest in QC.

[frag.machine]

Make builtins for navigation, do rest in QC.

^^^This.

[GiffE]

Make builtins for navigation, do rest in QC.

I second that motion!
Navigation was one of the hardest things, I found, to figure out.