Jump to content

Strange game behaviour with overrides typo


Serpens
  • Pending

Just to report it the offical way.
see this post:

 


Steps to Reproduce
see post



User Feedback


Can you check your log file and look for the following print?

WARNING! Found value 'vershortseason' for setting 'autumn', but this is not a valid value. Use one of {noseason, veryshortseason, shortseason, default, longseason, verylongseason, random}.

I'm not sure how it is messing up your game so hard. From looking at the code it should be treating it the same as setting the value to "noseason"

Share this comment


Link to comment
Share on other sites

no, the only thing about season that can be found in logfile is:

Quote

[00:01:14]: OVERRIDE: setting    autumn    to    vershortseason    
[00:01:14]: OVERRIDE: setting    summer    to    vershortseason    
[00:01:14]: OVERRIDE: setting    winter    to    vershortseason    
[00:01:14]: OVERRIDE: setting    spring    to    vershortseason    
[00:01:14]: removing onetime override    autumn    
[00:01:14]: removing onetime override    winter    
[00:01:14]: removing onetime override    spring    
[00:01:14]: removing onetime override    summer   

But "noseason" is a good catch, cause it also happens when I set "noseason" to everything.

So I would suggest you:
1) If it is set to a setting that does not exist, make it the default setting instead of "nothing".
2) If a mod tries to make "noseason" for every season, let it crash at gamestart with error message. The game will crash after startseason anyway. But without a proper crash log. So you have to cause the crash with a error log, that every season was set to noseason.

Edited by Serpens

Share this comment


Link to comment
Share on other sites



Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

×
  • Create New...