Death Warrant Forums

monsTo wrote:so where can i download and how do i install it? (=

you MIGHT want to change the trigger to something a little more obscure. WaveX is just a bit simple and i don't know how common it is in maps out there. I don't know how concerned to be about it tripping up some existing maps. invasion_wavex would probably cut it.

As far as a test setup, did you install all the rpg/druids shit or did you just use the stock invasion?

This is a mutator that will notify a defined set of actors that
the Invasion Wave is starting.

Since this works using a polling methodology there is a delay of between
zero & 'pollSeconds' seconds between the end of the countdown and the
delivery of this notification.

There are several config items that can be set in the mutator's
config file section.  Since this is essentially an extension to
the standard Invasion game-type the standard ut2004.ini (aka the
system ini) is where the config is located.

[MutInvWaveNotify.MutInvWaveNotify]

  pollSeconds       - The number of seconds between polling actions.
                      Default: 5

  debug             - Set to true to see verbose debugging info.
                      Default: false

  bTriggerGeneric   - Set to false to disable the generic wave change
                      notify (see below).
                      Default: true

  bTriggerAllActors - Send notifications to AllActors() rather than just
                      the DynamicActors()
                      Default: false


There is a per-wave tag that is used.  They are sequentially numbered:
     InvWave1, InvWave2, ..., InvWave24

In addition, there is a generic tag that is sent on each change:
     InvWaveChange

This 'generic wave change' can be disabled if not desired (see above).

So, for each wave change (which includes the transition to start of game
as 'InvWave1') there will be either 1 or 2 notifications:

     InvWave1 & InvWaveChange
     InvWave2 & InvWaveChange
     .....
     InvWave24 & InvWaveChange


NOTE: The mutator as distributed is a ServerSideOnly mutator.  This is done
due to the fact that there are no client-side dependencies.  This also means
that there is no need to place the mutator on any redirect server as it will
not be downloaded by the clients anyway.

It should still work in 'Instant Action'.

Have fun.

DW>Snaggle

Snaggle wrote:

monsTo wrote:so where can i download and how do i install it? (=

See the end of this message. :drunken:

you MIGHT want to change the trigger to something a little more obscure. WaveX is just a bit simple and i don't know how common it is in maps out there. I don't know how concerned to be about it tripping up some existing maps. invasion_wavex would probably cut it.

I took your suggestion to heart and changed the names. See the text below. The one issue with doing this is that I am now unable to test to make sure the names 'stuck' as the testing map is using the old names still.

(with all apologies to Kevin Bacon) "Please sir! May I have another?"

As far as a test setup, did you install all the rpg/druids shit or did you just use the stock invasion?

For Instant Action I used plain-old Invasion. For online play I used a copy of the MM server's setup (as of a couple of weeks ago). So the real answer is "Both".

Here's the help file from the zip:

Code: Select all

This is a mutator that will notify a defined set of actors that
the Invasion Wave is starting.

Since this works using a polling methodology there is a delay of between
zero & 'pollSeconds' seconds between the end of the countdown and the
delivery of this notification.

There are several config items that can be set in the mutator's
config file section.  Since this is essentially an extension to
the standard Invasion game-type the standard ut2004.ini (aka the
system ini) is where the config is located.

[MutInvWaveNotify.MutInvWaveNotify]

  pollSeconds       - The number of seconds between polling actions.
                      Default: 5

  debug             - Set to true to see verbose debugging info.
                      Default: false

  bTriggerGeneric   - Set to false to disable the generic wave change
                      notify (see below).
                      Default: true

  bTriggerAllActors - Send notifications to AllActors() rather than just
                      the DynamicActors()
                      Default: false


There is a per-wave tag that is used.  They are sequentially numbered:
     InvWave1, InvWave2, ..., InvWave24

In addition, there is a generic tag that is sent on each change:
     InvWaveChange

This 'generic wave change' can be disabled if not desired (see above).

So, for each wave change (which includes the transition to start of game
as 'InvWave1') there will be either 1 or 2 notifications:

     InvWave1 & InvWaveChange
     InvWave2 & InvWaveChange
     .....
     InvWave24 & InvWaveChange


NOTE: The mutator as distributed is a ServerSideOnly mutator.  This is done
due to the fact that there are no client-side dependencies.  This also means
that there is no need to place the mutator on any redirect server as it will
not be downloaded by the clients anyway.

It should still work in 'Instant Action'.

Have fun.

DW>Snaggle

As this is a serverSideOnly mutator, I am unsure as to the 'public' status of the module.

The question is: Does DW want to keep it internal or release it for general consumption?

I have no preference either way.

I have a protected URL for you. I'll need to catch you on Vent or something.

Snaggle.

Snaggle wrote: As this is a serverSideOnly mutator, I am unsure as to the 'public' status of the module.

The question is: Does DW want to keep it internal or release it for general consumption?

DW_Hornet wrote:Proof of concept map?