AGEOD Forums

Dear Players,

We are nearing it! The beta patches are more and more stable and soon enough the first official patch will be up.

Another last or near last candidate for you:

http://ageoddl.telechargement.fr/latest/Patch_ROP101i.zip

(this patch delete saved games)



Rise of Prussia Update 1.01i
March 18, 2010

The patch is a comprehensive patch, meaning it can be applied directly over your initial game installation setup version.


All saved games will be erased by the patch, as this version is not compatible with previously started games.
Engine:
* Fixed bug where selection of the last choice in Multi-Choice Event would not allow player to change the selection
* Siege parameters adjusted and new rules and parameters added:
If there is a supply unit or a depot with at least some remaining supplies, then there is a 95% chance that any surrender event is aborted. If there is not such unit or structure, or the chance roll fails, then a surrender event can happen (others possible events are: make a breach or nothing). In the case that besieged units are under siege by a larger force, have some units unsupplied and a breach is already existing, then the surrender event has an increased chance to happen, because it is based on the discipline of the besieged units and such units will get a -3 modifier to the roll.
* You can now select units in the construction mode after the 64th one.

Events
* Added check in Ferdinand to Brunswick event to be sure he is still only a 2* [and still alive!!]
* Modified all Multi-Choice events to have 'default selection' in case player doesn't choose an option
* Saxony Capitulation event [1756] now only eliminates Saxon forces still in the Saxony Theater. 'Escaped' leaders and units survive.
* Swedish Reinforcement Options - added small Brigades 1&2 and Support 1 to setups 1759 and 1760 as appropriate. Restricted "ON" dates for these options to prevent duplicates.
* Danzig: Multi-choice Event. Danzig [Gdansk] POL now, but was more or less an independent autonomous city. Russian and Austrian tried to woo the city to join their side, when their situation was not so good, but Prussian money prevented this. If AUS successful, they take over the city + large amount of supplies + depot there (to be under RUS subfaction). If PRU successful, Gdansk remains Polish and neutral. {PRU has priority: if they spend the money, it really doesn't matter what AUS chooses}
* Fixed duplicate appearances of Kleine Krieg units after 1758

Setups
* Added Riverine Supply assets to allow supply to move on river
* Removed duplicate RUS leader Rumyantsev from 1760 Setup
* Corrected starting 1756 Prussian ForcePool to have Regular Depot Bn in addition to Grenadier Depot Bn [typo in DB had Grenadier twice]
* Corrected on-map display of "1 leader/1 regiment" units to show leader properly
* Added Swedish Brigade reinforcements that were in options to the setups 1759 and 1760

DB
* Corrected Infantry elements of PAL regiments to be PAL, not BRU
* Corrected PRU and SAX Grenadiers Depot Bn to yield Elite replacements
* Added *screener* attribute to most Cavalry models [not heavy cav (cuirassier/gd corps)]
* Added *assault* attribute and 'Assaulter' ability [can assault unbreached fortress] = assigned to Ernst von Laudon

Thanks Pocus.

You forgot to mention Pangi's portraits, Puttkamer and Macquire

Was it intentional to once again lower WSu cost in recruitment?

Yes, Pocus argued that WSU represents only heavy war material...in addition, too many WSU created weird messages (like the one we had where you captured 3 times as many muskets as there were soldiers )

Thanks Pocus, you are a man of your word, just to confirm, has the retreat bug been fixed, I cant see it in the list

I have just had the Duke of Cumberland arrive, but he has not gone to Zastrow's column like he should, he's taken over a Prussian one.

Ebbingford wrote:I have just had the Duke of Cumberland arrive, but he has not gone to Zastrow's column like he should, he's taken over a Prussian one.

nertz! There are two Zastrows!!!!

One Prussian, One Hannoverian...

will fix

lodilefty wrote:nertz! There are two Zastrows!!!!

One Prussian, One Hannoverian...

will fix

Hotfix for Duke of Cumberland arrival in 1757

Extract into RoP/Events
One file will be overwritten

I have just selected the historical option that sends Ferdinand to Brunswick as a 3* general. He was already in Hanover when I selected the option but the event has not worked properly. He is still only a 2*. This event has worked in previous versions even when he has been in Hanover already. I also received no message that he has gone to Brunswick like in previous versions.


Edit.... Ignore the above, the event did fire but 2 turns after I selected it. It was the same with the Danzig option, I selected that in the same turn, but that had the same delay.

Ebbingford wrote:I have just selected the historical option that sends Ferdinand to Brunswick as a 3* general. He was already in Hanover when I selected the option but the event has not worked properly. He is still only a 2*. This event has worked in previous versions even when he has been in Hanover already. I also received no message that he has gone to Brunswick like in previous versions.


Edit.... Ignore the above, the event did fire but 2 turns after I selected it. It was the same with the Danzig option, I selected that in the same turn, but that had the same delay.

We've done some things to create a 'default' for the player who forgets to choose an option. Gotta look again to see if that causes unexpected delays

• Fixes the strange behavior of several Multi-Choice events [Ferdinand, Wesel, Berlin Ransom, and others]
• Corrects tooltips for several Replacements Options [Hannover and others]
• Includes all previous 1.01i hotfix files
  [Duke of Cumberland arrival]

Extract into your /RoP directory
Two folders with total 4 files overwritten

Don't want to hijack the thread so I will be brief: thank you for being so supportive and proactive in addressing essentially minor bugs. Paradox should take a lesson, they are lucky to have you guys. I will continue to put out whatever AGE engine games you put out

This is still from g but as as it has not been listed in i...


Commented before by other players

[attach]10647[/attach]



9 Prussian balance morale decreased to balance the game, is not there another more immersive or historical way to report it? 2 Assassination attempt provided no info?

[attach]10648[/attach]



Goods graphic is misplaced?

[attach]10649[/attach]

Would you like to suggest some "immersive" texts that we could use

Something along the lines of "French forces take all fodder from such and such a province of Hanover, the population grows tired of war". Maybe, or inserting other nationalities and regions, or even "Our armies are forced to requisition supplies from the locals in....".

Well, as the reason seems to be somewhat artificial perhaps the best way is to hide these kind of messages?

Then somebody would complain of strange changes in NM, VP...

Make it optional to disable them?



Let's see if I understand it, regarding the message-events there are:

-Red ones, the most important with paper explanation.

-Text in black with tooltip explanation

-Text in black without any explanation at all, like the assassination attempt. Is it WAD?

Nikel wrote:<snip>


Let's see if I understand it, regarding the message-events there are:

-Red ones, the most important with paper explanation.

-Text in black with tooltip explanation

-[color="Red"]Text in black without any explanation at all, like the assassination attempt.[/color] Is it WAD?

WAD. In this case, it is an event occurring to the other side. The 'notification' given to the opponent carries no tooltip.

You will note that you only get a generic message whe the other side buys replacements, adds a general, etc. All Fog of War

Oh thanks lodilefty.

But at least I should know which king (the king of France here), when read it thought that was Frederick himself

A request then.


This third category of FOW, other side,... messages could be reported using a different color for the text?

Or perhaps better, hold black for them and change the color for the second one blue or green...

Although I cant really think of a more immersive text for the adjusting of the Pruissian morale, I think it would be better received if it was a general rule. Now it feels kind of arbitrary.

So a rule like: A countries morale is is maximal 130, if it gets above this it is reduced 5 points per turn, the country in question gets 5 VP and.... (this should be in the manual, under morale and effects).

As it is it feels like a rather arbitrary rule that punishes you, in order to balance the game, just when you are doing good. (A bit like "you are winning to fast, lets handicap you to keep it interesting"). This of course is made worse by the fact that up till the point your NM is adjusted, you did not know it would, and you were striving to get it a high as possible (especially if you played other AGEOD games, where it could go up to 200).

With a known rule that the morale is capped at 130 (or any other value) and that you get VP (and other goodies) instead, a higher NM is still something to strive for. And the player can choose wheter he thinks the VP are worth it to keep fighting battles for.

Is it WAD that bavarian, saxon, and HRE normal depot regiments bring elite infantry reinforcements instead of regulars?

Longhairedlout wrote:Thanks Pocus, you are a man of your word, just to confirm, has the retreat bug been fixed, I cant see it in the list

Indeed, I confirm I intervened on the retreat code (once again ) and fixed yet another bug. I just hope everything is fine now, the example I had (which was buggy before the fix) was working properly after editing the code, so I have faith.

Panzeh wrote:Is it WAD that bavarian, saxon, and HRE normal depot regiments bring elite infantry reinforcements instead of regulars?

No!

Will fix!

Any word on fixes for the retreat bug identified by a poster a week ago?

All known retreat bugs have been eliminated.

Curious about the current status. Any ETA on when the patch will be out of beta?

There will be a 1.02 release candidate very very soon, which ought to be the official 1.02 later, if nothing major is spotted.