Code Mutator Development Setup

[Datin]

Hi All,

I was looking on writing up some simple mutators for KF2, but a few of the tutorials that I've seen out there for creating mutators don't seem to apply to KF2. I've downloaded the Killing Floor 2 SDK and found the UnrealEditor, which is useful for map making, but it doesn't appear to be the right avenue for writing mutators.

For example, https://udn.epicgames.com/Three/CustomUnrealScriptProjects.html[url]https://udn.epicgames.com/Three/CustomUnrealScriptProjects.html[/URL]

I've tried to setup a Development/Src/<PackageName> directory structure and added the Package name to my DefaultEngine.ini. I added a simple .uc file in there as a test. I tried launching KF2, which should auto-compile like the above link states, but it didn't appear to have any affect. I then tried launching 'KFGame.exe make' but then I get an error saying that it needs to be running with Steam. So I added the launch argument 'make' to Killing Floor 2, but I got the same error.

I've read that some folks have had success already with creating some mutators (player max, etc) so it appears it's possible at this time to do it. Anybody have some steps or documentation on how to setup the environment for mutator development?

 

[Dark Light]

Any luck?

 

[[TW]Strago]

Mutators aren't officially supported yet until we release script code. There are some ways to make limited mutators, but these may not be around forever so you may want to hold off until we add full support and experiment with mutators on UDK until then. No eta yet, but we're working on adding this.

 

[Datin]

Thanks, appreciate the heads up Strago!

 

[BEEEEEES]

Mutators aren't officially supported yet until we release script code. There are some ways to make limited mutators, but these may not be around forever so you may want to hold off until we add full support and experiment with mutators on UDK until then. No eta yet, but we're working on adding this.

mmmmmeeeeEEEEEEEEHHHHHHH! NEED DEM SOURCE FILES!

 

[Dark Light]

mmmmmeeeeEEEEEEEEHHHHHHH! NEED DEM SOURCE FILES!

I can give you most of the source files if you can tell me how to compile a mod, since KFgame and KFEditor gives a no Steam error.

 

[forrestmark9]

Hi All,

I was looking on writing up some simple mutators for KF2, but a few of the tutorials that I've seen out there for creating mutators don't seem to apply to KF2. I've downloaded the Killing Floor 2 SDK and found the UnrealEditor, which is useful for map making, but it doesn't appear to be the right avenue for writing mutators.

For example, https://udn.epicgames.com/Three/CustomUnrealScriptProjects.html[url]https://udn.epicgames.com/Three/CustomUnrealScriptProjects.html[/URL]

I've tried to setup a Development/Src/<PackageName> directory structure and added the Package name to my DefaultEngine.ini. I added a simple .uc file in there as a test. I tried launching KF2, which should auto-compile like the above link states, but it didn't appear to have any affect. I then tried launching 'KFGame.exe make' but then I get an error saying that it needs to be running with Steam. So I added the launch argument 'make' to Killing Floor 2, but I got the same error.

I've read that some folks have had success already with creating some mutators (player max, etc) so it appears it's possible at this time to do it. Anybody have some steps or documentation on how to setup the environment for mutator development?

Compile the mod from the UDK, just compile KFGame and all that with whetever class you want to use with what vars and functions you wish to use

 

[Dark Light]

Compile the mod from the UDK, just compile KFGame and all that with whetever class you want to use with what vars and functions you wish to use

But then you just errors because KFGame referenced classes from other files, you will need all the source files some of which don't decompile.

 

[FZFalzar]

Make stubs for the functions required but not used by your mutator. Unlike a full binary file, mutators just point toward whichever function referenced, the actual content of the function will then be executed at runtime context