Bug
Fix
Great Battles Of Alexander
Bug
Bug
Bug
Fix
Fix
Bug
Fix
Bug
Fix
Bug
Fix
Fix
Bug
Fix
Bug
Fix
Great Battles Scenario Editor
In Pelium, playing the Macedonians and choosing the retreat across the river option, why doesn't the battle end when I move 50 rout points worth of troops (per page 89 of the manual) and Alex across the river?
The manual is incorrect in saying rout points. It should be TQ (troop quality) points. Each unit's TQ points may be viewed when the mouse curser is over the unit by looking at the data in the lower left fly-by window.
In Hydaspes, I was defeated at the end of turn 10 even though I had not lost the required rout points.
The manual and help file incorrectly state that there is no turn limit for Hydaspes. There is in fact a 10-turn limit.
Also beware of a bug regarding elephants. If elephants move next to cavalry, causing a hit, and then you undo, the hit will remain. It is thus possible for on elephant to rout a cavalry unit by several undo commands and moving the elephant again. It may not happen each time, but it does happen. Tournament rules prohibit undoing an elephant move next to cavalry.
Prohibit undoing an elephant move next to cavalry.
In Lyginus (Alexander), the loss of a phalanx unit is incorectly tallied on the score card. It shows as 14 point loss but the total point loss works out to 21 points.
No fix is available but the true score for the game can be determined by manual calculation. There is still the problem of end of turn for routing units though if the scores are close.
In various scenarios a leader can be left with no command points left but clicking the 'Finish Leader' button does not move onto the next leader.
No fix is available. If you reach this point, you'll have to go back to a saved position and roll forward again. Save often to avoid this bug having a serious effect on your game.
Double Size Units - The only double sized units one can create with the editor are phalanxes. The two other units in the games (Greek hoplites and Persian cardaces) cannot be created with the editor.
Whilst there are a number of units the editor cannot create, there is to a certain extent a way to create double size units of almost any unit type.
By copying the EIF files you want as double units to the phalanx filenames in the scenario editor you can create a double size unit that looks like any other unit you wish - even cavelry or elephants !
Before you start to change any files ENSURE YOU HAVE TAKEN A BACKUP or you'll have to reinstall the game to get the original settings back. All 3 files have to be replaced as they show the unit at the 3 zoom settings.
- Replace mphalx.eif with the unit of your choice neither ending in a 2 or a 4
- Replace mphalx2.eif with the unit of your choice ending in a 2
- Replace mphalx4.eif with the unit of your choice ending in a 4
When finished replace the original mphalx?.eif files ready for the next game.
Pointer problem. The editor can rapidly get confused if you make a lot of changes at one sitting; so plan what you want to do first.
Enter your scenario in a number of stages making only a few additions or changes at a time before closing and reopening your scenario. Save under a different name each time in case of problems - you can always
go back to the previous version. By limiting the changes and taking backups, you limit the chance of confusion by the editor or of losing your hard work.
Suggest sequence of creating a new scenario:
- Plan your scenario.
- Create the new scenario, give it a name and save it.
- If required, open the unit editor and edit the units. Don't edit too many units at a time. After four major changes, close the unit editor and open it again for the next change.
- Once complete with the unit editor, close your scenario under a new name then re-open it.
- Place your first leader and add all units assigned to him then resave the scenario under a new name.
- Continue with each other leader until all leaders and units have been entered.
- Finally save your completed scenario with the its proper name and delete all previous saved copies.
The Pontine chariot. Though this unit is officially available in the editor, any Pontine chariot will lead to an immediate crash once you run the scenario.
Avoid using the Pontine chariot.
If you create a new skirmisher unit and include the word "Agrian" somewhere in its name, the unit can SHOCK ATTACK! So you can have shock attacking slingers and archers just provided you call them "Agrian Slinger" or "Caesar's Agrians" for example. This bug found by Nik Fincher.
Avoid using the name 'Agrian'.
