|
bobarossa -> RE: New version of Bombur mod is out (5/13/2017 8:37:10 PM)
|
Based on a 1.5 year test, it was way easier than it seemed. For some reason, the original designer (Vic?) set up the weather to run on a separate counter than the months. May have been so you could do rounds or months. Anyway, I just added a CheckMonth() call and used it to index the weather table instead of the GameSlot that was used previously. I think my weather is changing a half month off of intended, possibly the date gets updated after the weather update event occurs.
The lines I added are to event 11 and consist of 2 lines inserted after line 17.
18 SETVAR TempVar7 = checkMonth()
19 SETVAR TempVar7 - 1
I then modified the new line 20 to use TempVar7 instead of the GameSlot_Empty(#0). I did the subtraction in Line 19 because the weather table rows start at 0 instead of 1. You should also note that the original newdawn code sets the starting month to May but sets the weather index to 3 into the weather table (4th row; makes weather occur a month later than I would like to see). The only way to fix this is to do gyrations with the month or to rotate everything in the weather table down one row.
Test results: Mud went from Dec 30 to Jan14, snow from Jan 29 to March 15, mud on March 30
next year mud went from Dec 25 to Jan 9, snow from Jan 24 to March 10.
edit: and because I'm using GetMonth(), it shouldn't matter how many days we use in a turn.
Strange coding decision of the week: the randomness in the weather appears to be based on the number of regimes in the game (see line 1 of event 11)
|
|
|
|
