Page 1 of 1
How to change kart speed in 0.9.2

Posted:
21 Jun 2016, 17:46
by atkins80
I noticed that the newest version has a new xml file titled kart_characteristics, I know the older versions you could change the karts speed in the stk_config, I was wondering how to go about this, the older file had 4 separate lines for each skill speed one for novice,intermediate,expert and super, that was in the 0.9.1 and earlier versions, this newest one has me confused a bit, I still know how to change values, but it also causes the other skill levels to have the wrong speed.
Re: How to change kart speed in 0.9.2

Posted:
24 Jun 2016, 00:26
by Auria
I will let hiker answer that in more details, but in the new version you will want to take a look at file "kart_characteristics.xml", look for the "<difficulties>" section for simple engine power and max speed multipliers. Otherwise you can dig through the rest of the file for all the parameters
Re: How to change kart speed in 0.9.2

Posted:
30 Jun 2016, 05:27
by hiker
Hi,
the new system is based on the data/kart_characteristic.xml file. It contains documentation at the top of the file (though we should take the time to properly document it on our web page).
The basic idea is that a set of base values is taken, which are then modified in a fixed order: first you take the base, then apply difficulty modifier, then kart characteristics (light, medium, heavy). Each characteristic can either overwrite of modify the previous value. E.g. if the base value of an attribute is (say) 2.0, then e.g. difficulty can say "*1.5+1", kart characteristic could then be "/1.1". No operator precedence is implemented, so it's strictly left to right evaluation.
Hopefully this should make it easier to implement new kart types.
Having said all of this, when I just tried to use some of the values, I noticed a few bugs in our current version (which will also affect the upcoming 0.9.2 release). Negative characteristics don't work (e.g. value="-0.6"), and more than one operator (*1.5+2 as mentioned above) actually does not work either, but that's already fixed in git (and more unit tests will hopefully be added).
Cheers,
Joerg