No time limit 1.0 + Hearts of Iron 1.03 + startdate < 1924 = freeze?

[Johan Elisson]

The no time limit patch worked just fine with HoI 1.02 but now I have installed 1.03 (PAN) and continued on our TGW-mod, but then I suddenly realize that the game just freeze (but it doesn't crasch), if you set the start date to anything less than 1924. 1924 and everything about works just fine, but noting below. Why?

/Elisson

 

[Procer]

We will have to ask Timur Lang (aka DiegoV) from HoI Latino.

I have just emailed him telling him about this thread.

 

[Timur Lang]

'suddenly' do you refer at once in that you start?

 

[Johan Elisson]

Originally posted by Timur Lang
'suddenly' do you refer at once in that you start?

Yes, I expressed myself a little bit unclear, what I meant was that I didn't check if the game was runing, I was only checking if everything looked like it should, and then I saw that the time was still 00:00 January 1, 1914.

/Elisson

 

[unmerged(13852)]

On the other end of the spectrum, I set the end date to 1953, and when I started a new game it said the end date was 2199! Not that I'm complaining, but I just wanted a few extra years, not a few extra centuries. This is the part I changed, right at the top of the EUG file for the 1936 scenario:

header = {
name = "Grand Campaign"
startyear = 1936
endyear = 1953


Is that the wrong part to change?

 

[unmerged(13852)]

Nevermind. It was the wrong part to change. This is the right part.

globaldata = {
startdate = {
year = 1936
month = january
day = 0
}
enddate = {
year = 1949
month = january
day = 0

 

[unmerged(13852)]

However, even though I have made the proper changes, in the game it still says the end date is 2199. Any advice? Also, I am using the NA 1.03 zipped patch.

 

[Timur Lang]

I have detected that it is impossible to select the year the game should end.

The enddate variable is not considered by the game. This happens with or without the no time limit (Try changing The Road to War (1936-1948).eug endate to 1945, save the game, then open the save game and you will see that appears endate = 1948)
Perhaps this happens for one of the changes of the patch 1.03 (I am not sure):

"...Now the game will only end before 1948 if there is only ONE alliance around..."

Because of this issue, the No Time Limit 1.0 will make the game to end in 2199 unless there's only one faction left which will make the game to finish earlier.

But I think that it is not so serious, the creators of scenarios can solve it with an event:

event = { 
	id = 50100 # or another id number
	
	name = "End of the scenario"
	desc = "You have now reached the end of the scenario 
date, you can leave him by clicking the 'Surrender' button (Also 
you can see the final victory points). But if you want it you can 
continue playing the game. Note that the events and modifications 
of this scenario are contemplated to play until this date, if you 
continue playing there will no longer be new events or other 
additional effects."

	style = 0
	
	date = { day = x month = x year = x } # the date that finishes the scenario
	
	action_a = {
		name = "OK"
		command = { }
	}
}

 

[unmerged(13852)]

Yeah, I'm not that worried about it. I have yet to complete a full game (was waiting for the 1.03 patch), but I am sure I can finish before 1948, I just wanted to add I few years lee-way, just in case. A few years, a few centuries, as long as it doesn't screw overall gameplay it doesn't matter to me.

 

[Johan Elisson]

Hmmm, it was a long time ago I posted this, but now I've solved the problem. Same thing happened with patch 1.03b and I accidentaly found out that this event screwed things up, the game doesn't find anything wrong with the event at startup, but no time progress is made, anyone who can explain to me why this event makes the game freeze?

# Italian Alliance

event = { 
    id = 6 
    random = no 
    country = ITA 
    name = "The defensive alliance" 
    desc = "Italy has only commited herself to a 
defensive alliance with Germany and Austria-Hungary, 
but our alliance brothers are now on the offensive. 
What should we do?" 
    style = 0 
    trigger = { 
        atwar = GER 
        atwar = U11 
        NOT = { 
            control = { province = 712 data = RUS } 
            control = { province = 713 data = RUS } 
            control = { province = 714 data = RUS } 
            control = { province = 715 data = RUS } 
            control = { province = 649 data = RUS } 
            control = { province = 648 data = RUS } 
            control = { province = 639 data = RUS } 
            control = { province = 637 data = RUS } 
            control = { province = 638 data = RUS } 
            control = { province = 720 data = RUS } 
            control = { province = 719 data = RUS } 
            control = { province = 774 data = RUS } 
            control = { province = 766 data = RUS } 
            control = { province = 767 data = RUS } 
            control = { province = 552 data = BEL } 
            control = { province = 557 data = BEL } 
            control = { province = 554 data = FRA } 
            control = { province = 543 data = RUS } 
            control = { province = 544 data = RUS } 
            control = { province = 935 data = RUS } 
            } 
        } 
    date = { day = 0 month = january year = 1914 } 
    deathdate = { day = 0 month = january year = 1924 } 
    action_a = { 
        name = "Go neutral." 
        command = { type = leave_alliance } 
    } 
    action_b = { 
        name = "Stay allied." 
        command = { } 
    } 
}

As long as the start date of the scenario is between the date and deathdate of the event, the game freezes.

/Elisson

 

[unmerged(12730)]

.

DiegoV (a.k.a. Timur Lang) from HoI Latino answered a frequent question regading the compatibility of No Time Limit 1.0 with Hearts of Iron v1.03. The mod works with 1.03 but there is one problem that cannot be fixed (so far): even if you can set up the game to start at any time, since the new patch it is impossible to select the year the game should end. Even if you try, the game will end in 2199. In short: you can increase the time scope of the game but you cannot make the game to end whenever you want.

this is what the author said

 

[jdrou]

Originally posted by Elisson
Hmmm, it was a long time ago I posted this, but now I've solved the problem. Same thing happened with patch 1.03b and I accidentaly found out that this event screwed things up, the game doesn't find anything wrong with the event at startup, but no time progress is made, anyone who can explain to me why this event makes the game freeze?

. . .

As long as the start date of the scenario is between the date and deathdate of the event, the game freezes.

/Elisson

Try an offset = 1 after the date.

 

[Johan Elisson]

Thanks, it now works!

But it won't fire...

/Elisson

 

[Timur Lang]

Originally posted by Elisson
Thanks, it now works!

But it won't fire...

/Elisson

was the problem resolved?

 

[Timur Lang]

Elisson:

If for the TGW you want a 'special' no time limit, I can make them (e.g. 1000-1930, instead of the current one 1000-2199). I'm particularly enthusiastic with this scenario.

 

[Johan Elisson]

The original problem is solved, the game doesn't freeze, but now another problem showed up, the event won't fire. It should trigger if (Germany is at war) AND (Austria-Hungary is at war) AND (any of the provinces are not under the control of respective owner). Because there is a built-in OR function in the NOT function, right? But it won't fire...

It would be really nice if you could make a January 1, 1924, time limit mod! Thanks in advance!

/Elisson