Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[TimeDiver]

The Subject header pretty much says everything I'm curious about.

I looked through settings.json (and came up with some really wonky workarounds), but I suspect that JavaScript might be the only way to actually uncap the imposed Burn limit of 20 (excepting that occasional +10).

[xenoargh]

Well, if you just want to go faster, it's suuuuuper easy.

You were in the right place; in settings.json:

   "minTravelSpeed":20, # at max burn 0
   "baseTravelSpeed":0, # in units (pixels) per real-time second (10 sec/day)
   "speedPerBurnLevel":60, # speed per max burn level, in units (pixels) per real-time second (10 sec/day)
   "maxStormStrikeBurn":30,   

Try that... now you're moving really fast!

[TimeDiver]

Well, if you just want to go faster, it's suuuuuper easy.

You were in the right place; in settings.json:

   "minTravelSpeed":20, # at max burn 0
   "baseTravelSpeed":0, # in units (pixels) per real-time second (10 sec/day)
   "speedPerBurnLevel":60, # speed per max burn level, in units (pixels) per real-time second (10 sec/day)
   "maxStormStrikeBurn":30,   

Try that... now you're moving really fast!

Yeah, this was one of those 'really wonky workarounds' I'd mentioned in my opening post of the thread.

Thanks for the reminder, though. I keep it in mind, just in case I no longer give any *** about global gameplay balance.

[xenoargh]

Well, it applies to all parties, so you all zoom around, yeah.  Problem is, the Burn limit of 20 is essentially hard-coded; you can't add 21+ to the game.  So the issue here is largely, "what speed does Burn 20 represent, vs. Burn 1", and there might be a good argument that it should use some sort of logarithmic scalar there or something.