a style or other reasons

Post new scenarios and mods here to share with other gamers.

Moderator: Joel Billings

Post Reply
HOTEC
Posts: 828
Joined: Sat Nov 23, 2013 3:34 am

a style or other reasons

Post by HOTEC »

My understanding from this event (A) is as follows:
a) the event will be checked each turn from 1.7.1943 to 31.10.1943 inclusive;
b) it will be triggered if its random(25) is less than 25.
c) it will be stopped after 15+1 times as specified by Reccurence of 15.

1 is added because the reccurence of 0 means that the event (B) is just happened once. Recurrence of 1 means that the event will be happened 2 times and so forth.

It is not understood at first of why the surrender of Romania (C) would be occurred twice for setting recurrence of 1. However, this effect is nullified by deactivation of Game Event. If I set the recurrence as 0, would it be not necessary to set the active of Game Event to FALSE. This also finds in Slovakia Surrenders. Is there any hidden agenda or a matter of programming style?

BTW, it is not understood why Recurrence is a typo.
Attachments
Surrender_01.jpg
Surrender_01.jpg (800.86 KiB) Viewed 1066 times
DarkHorse2
Posts: 1070
Joined: Fri Feb 04, 2022 12:08 pm

Re: a style or other reasons

Post by DarkHorse2 »

recurrence

Recurrence

hmm.... not a typo on my end.

aorkaedf

Previous line is marked as a typo.

I think that is governed by your local browser settings. For example "Panzer" was a typo for me, but then I right-clicked on the word and selected "Add to Dictionary", which I believe updates your local browser typo detection settings.

Hope this is helpful....
User avatar
Joel Billings
Posts: 33699
Joined: Wed Sep 20, 2000 8:00 am
Location: Santa Rosa, CA
Contact:

Re: a style or other reasons

Post by Joel Billings »

Only Pavel can probably explain this correctly, but I'll say what I think is going on here:

In the case of the Romanian Surrender, a recurrence of 1 means it will check each turn (1 turn later) to see if it makes the 50% die roll. Since we only want the event to activate once, we need to tell the event to become inactive after it executes, or it could happen every turn (like the partisan events). That's why the last action of the event is to deactivate the event.

In the case of an event we only want to happen once and doesn't have a probability check, we set it to recurrence 0. That way, as soon as it happens once, it will automatically deactivate the event.

In the case of recurrence 15 on the bomber raid, this tells the system to check 15 turns later. I think it will check the 25% chance each turn, but once it succeeds, it won't check again for 15 turns. I recall Gary set this one up so that there was a chance that 2 of these raids might happen. Basically if a raid happens at the beginning of July, there's a small chance another raid might happen in late October. I think that this event will check every turn starting in July 1943 to see if it made the 25% chance. The Recurrence only matters if the probability check is successful. If the 25% is met, no matter if the conditions are met or not, I think it waits 15 more turns to start checking again. In the Romania event, the recurrence is 1 because we want it to check every turn.

As long as events have a non-0 recurrence, there is no limit to the number of times the event can actually happen (just a cut off date, having the event deactivate itself, or having another event deactivate it, will keep it form happening forever.
All understanding comes after the fact.
-- Soren Kierkegaard
HOTEC
Posts: 828
Joined: Sat Nov 23, 2013 3:34 am

Re: a style or other reasons

Post by HOTEC »

Thanks all.
Post Reply

Return to “Scenario Design and Modding”