Config Parameters separate from mutator info? Autowrite?

[KewlAzMe]

-Changed topic based on Mysterials first post. Please see 3rd post-

[Mysterial]

http://utforums.epicgames.com/showthread.php?t=585046

[KewlAzMe]

http://utforums.epicgames.com/showthread.php?t=585046
LOL how did i miss that! I was even looking for something like that.. but apparently need my eyes checked.


-TOPIC CHANGE-

How do you make it auto-write config variable to the config file?

if I use the bExportMenuData=false in the defaultprops, it doesn't generate the custom ini file and instead puts the info into the UTGame.ini file..which is fine, but the actual config variables don't work under there. There needs to be another section that uses the old method of referencing the mutator:

For example:
I have a MultiJump mutator with configurable number of jumps and configurable boost:

The mutator auto-creates this info:

[MultiJump UTUIDataProvider_Mutator]
ClassName=MultiJump.MultiJump
FriendlyName=MultiJump
Description=
GroupNames=MULTIJUMP
UIConfigScene=
bStandaloneOnly=False
bRemoveOn360=False
bRemoveOnPC=False
bRemoveOnPS3=False


But in order to use the configurable stuff, I have to manually add:

[MultiJump.MultiJump]
iMaxNumJumps=99
iMaxJumpBoost=100


I suppose I could make it auto-add by adding an in-game UI_config_scene but is this "the way it works"?

[BattleMode]

How do you make it auto-write config variable to the config file? You can use SaveConfig(); for that. This will write all config variables to the proper INI file.

[KewlAzMe]

Ah thanks.. where would i put that in my code?

[kisk]

i'd imagine inside a block :D

[KewlAzMe]

lol well i put it right after
Super.ModifyPlayer(P);
SaveConfig();

but it saves the two config variables with 0 values, instead of the defaultproperties values

[Mysterial]

The defaultproperties values for config properties not working is what's getting fixed in the patch.

[KewlAzMe]

The defaultproperties values for config properties not working is what's getting fixed in the patch.

Ya I know that, I just want to make sure that I am doing it correctly and that when the patch comes out, the mutator will automatically work properly and execute the SaveConfig using the defaultproperties values I set.

If all of that is correct then the mutator should fix itself.

[Mysterial]

You'll have to recompile your mutator with the patch for it to work. Currently, the defaultproperties values for config/localized properties aren't getting saved in the compiled package.

[KewlAzMe]

ah.. i see.. ok thanks :)