there seems to be an issue with the way I selected to transfer the countdown duration to the client (via event)
In server side Execution I run by the g_addevent just fine, however on the client side the event is not called.
there is also a new definition for trigger_airlock.
Signed-off-by: Harry Young <hendrik.gerritzen@googlemail.com>
On the way merged target_postiton with info_notnull
Also added a failsafe to target_selfdestruct so it can only be commandspawned
Signed-off-by: Harry Young <hendrik.gerritzen@googlemail.com>
UI displays status of all systems connected to it's parent target-shiphealth
There is also a slide for relative health
It does not auto update.
Up next I'll try the HUD-Element.
Signed-off-by: Harry Young <hendrik.gerritzen@googlemail.com>
* removed unused cvars and related code
* moved rpg_message cvars into timedmessages.cfg and removed the cvars
* modified list module to support cyclic list access
selfdestructcountdown wouldn't blow. Moved safezonetrigger to 0.1 secs and at another position, to compensate.
selfdestructcountdown will no longer play no futher audiowarning sounds
Signed-off-by: Harry Young <hendrik.gerritzen@googlemail.com>
Added a new command selfdestructcountdown duration [safezone] [target]
It'll do exactly the same as selfdestruct start with the exception that it'll force the entity to think every 0.1 secs. to not do this accidently It got it's own command.
It uses the cp-command for display and disables admin_centerprint autoamtically.
On a more general selfdestruct note I got rid of those long warning sentences in favour of ^1Self Destruct in %.0f:%2.0f
Signed-off-by: Harry Young <hendrik.gerritzen@googlemail.com>
New command safezonelist that lists all safezones in existance.
It returns their targetnames, state (safe/unsafe) and theuir shipflag.
Minor fix to target_shiphealth so it now frees than links when there are missing parameters.
Signed-off-by: Harry Young <hendrik.gerritzen@googlemail.com>
Modified all of them to bertter support maps like rpg_runabout with more than one ship
both selfdestruct and shiphealth now allow for a safezones targetname to be added that is freed before called to list
that required modifications to the associated commands.
Now selfdestruct start asks for a safezone as it's 2nd to last argument and requires it if any safezone is spawnflaged as SHIP
shipdamage now has a 2nd argument that specifies the healthEnt it shall deal to. It requires that argument if it finds at least 2 healthEnts
shiphealth now displays the status of all healthEnts that exist and displays it's targetname in line one of the output
There ar also a few other things associated with this (e.g. healthEnt now frees at spawn if it misses required parameters)
Expanded description of target_safezone
Signed-off-by: Harry Young <hendrik.gerritzen@googlemail.com>