Grow up.Curunir wrote:I'll just bump this up here for xdeath, seebs and Kurgen. Because it's a single line of code. As seebs enlightened us...antti wrote: The time multiplier was implemented for debugging purposes and it is invaluable when trying to spot animation issues and such. Using it will break things like audio sync and it can introduce a myriad of bugs since it has not been tested. For these reasons it's unlikely that slowing down the game will be an official feature.
Damn those pesky devs for refusing to add a feature that's just one line of code
Developer's attitude and the community
Re: Developer's attitude and the community
Re: Developer's attitude and the community
Ahh, I can see that being an issue.antti wrote:The time multiplier was implemented for debugging purposes and it is invaluable when trying to spot animation issues and such. Using it will break things like audio sync and it can introduce a myriad of bugs since it has not been tested. For these reasons it's unlikely that slowing down the game will be an official feature.seebs wrote:Well, consider if you will the requests people have made for a way to slow down the game to make it easier for people with slow reflexes to complete puzzles. HUUUUUGE amount of work? No. One line of Lua. You can do it yourself if you get a lua console up:Curunir wrote:Feedback that suggests slight alterations or fixes in the current game model is one thing, suggestions that require a TON of coding, change the core concepts of the game radically or are aimed at making the game more like Game X from 20 years ago is quite another.
That's exactly what I have in mind - requests that would either change the core game radically, or would require (I imagine) a lot of coding effort to achieve very minor effects.
gameMode.timeMultiplier = 0.5
So, easy to implement, but not easy to debug or make reliable.
Also, it is hilarious falling into a pit with time multiplier at 0.05.