Search options (Page 9 of 10)

Great to hear! Thanks for testing. :-)  I suppose the map is pretty bug free.

In the batch or console. I can't remember the syntax for batch but with a shortcut it is +set net_ip "0.0.0.0" replaced with your ip. I think it is same for batch. Check your ip with myip.dk.

I do not bother writing much on mobile. But routers, firewalls and systems are different. Only my current router need ports forwarded. So changes are that your friend could run a server with just few clicks.

But a dedicated server is just a bat and you will not be playing it unless you join separately, and probably with a different installation too. so it is possible ppl can join. so use non ded server.

Plus you might have to forward a port for your ip. and ingame set that ip and port with /net_ip "..." and /net_port "27960". This depends on your router. Also firewall can block net access, so exes should have full access.

There are many public servers too you can use.

:-)

Yes I know that ammo clips can be dropped. Not enough imho. Don't want to be constantly praying for others to spare some ammo for me too.

+1 esp on ammo. Slower players tend to run out of ammo, when the fast picks all. Not fun. Asking for ammo is no full solution.

I messaged Fretn about this. But, do you have g_inactivity set to other than 0? For me that caused massive errors on loading AI script in my map. So maybe you can check and set it to 0 and test if  my theory is true? Maybe it could be causing many of these mystical AI problems.

Well it's fine. Makes sure it just resets the old values and counts every time a new command is applied.

So you could do for example this: Start up with numrespawns 10 and after a certain gameplay event that "weakens the enemy" you can change it to numrespawns 3 and it would forget everything regarding that value of 10. And then you could turn it to 0 when players do another event that would weaken them (if 3 is down to 0 already it would not affect ofc). So better team = enemies weaken faster like in reality.

Also we must be able to know when the bot is dead in the script. When finally 100% dead after 10 respawns or just dead for the first time. So don't let this number of respawns be controlled with any cvar or skill setting, mappers need full control over this. Some objectives might require knowing absolute alive/dead count (eg. when everyone is 100% dead, it is safe to do something).

If you make the command for the next release I can be bug testing and experimenting with the feature on my own maps before it would be applied to official maps, if you like.

Ps what came to my mind regarding the death event. Maybe you can execute "death" when bot dies for the first time. And "death1" "death2" "death3"... "deathN" for each death after first respawn. Then we would have full control, plus we would not have to edit any existing maps. So nothing would break..

What I meant is the on/off way. You can define in map's script if and when a bot can or cannot respawn.  So "respawn on/off" command for each bot. And you can turn it on/off when ever you want. Would be "on" by default. Of course these would be ignored when g_airespawn = 0.

Do mind that death event should still be executed. Some scripts are executed from death. Death event must not be executed twice or something can break. You can either stop it in the code or do it from the AI script. Stopping it from the AI script is preferable, but will require more work to go through all the scripts (very easy but would take some hours).

Having max respawn times scriptable for each bot  would not hurt either. But do not include it to the main command.

So atleast (placed like any other AI script command):

respawn on/off (where on is default)

and if you like for extra

maxrespawn <n> (where 0 is unlimited and default)