|
ADDITIONAL
INFO ... |
Blow/Repair/Build
Each option requires to be enabled
on scenario file, so some scenarios could be designed to allow blow and
repair but not enabled for building, or could be enabled to build but
not to repair.
- Units having equipment
file's
special
"sapper"
or "engineer" attribute can blow up Bridges, Airports, Cities and Ports.
Unit must be placed on hex to blow, and should have not taken any action
- Units having "sapper"
special attribute can either repair blown hexes or convert terrain to
be Bridge, Airports, Ports or Fortification (build)
Unit must be placed on hex to blow, and should have not has fired,
reinforced or moved
.
|
Victory
Conditions
- Killing all
enemy units
This is standard victory conditions always enabled
- Taking all
Victory
Hexes (VH) within specific turns (BV,V,TV,LS)
This are standard victory conditions always enabled
- Holding a
number of VH after last turn. Result depends on how many player
got to hold
(this will allow true defensive scenarios). This victory condition
should be enabled on scenario file.
- Retreating a
given
number of units using scenario designed EH (escape
hexes) to achieve a BV, V or TV
This victory condition should be enabled in scenario file, and at least
one EH should be defined
- Killing all
enemy unit
defined as "Must Survive Units"
This should also be enabled in scenario and at least 1 unit should be
marked as Must Survive.
Note. Victory
conditions 2 and 3 are alternative, so if VH to hold is enabled, taking
VH has not effect.
|
Minefields
Mines are implemented as
a new terrain attribute. Can be defined in scenarios at design time,
but can also be dropped by certain units.
For Land mines:
Any land unit (not naval) having "ClearMine" attribute can try to
remove land mines
Any land unit (not naval) having "DropMine" attribute and at least 1
ammo, can drop land mines
For Sea mines:
Naval units, Tactical Bomber and Level Bombers having special atribute
"ClearMine" can remove sea mines
Naval units, Tactical Bomber and Level Bombers having special atribute
"DropMine" can drop sea mines
Minefields have no side, so they
can damage any unit regardless which side dropped it
- Entering spotted
minefields (ground/sea) require spend full movement (cost 254, like
rivers)
- Entering un-spotted
minefield can cause some losses - up to 3 strength points - depending
on unit experience and engineer attribute
- When any unit is on
a minefields its movement is limited to 1 and gets reduced its defense
by 3.
- To clear mines, unit
must be in the minefield, but not always will success and if no
success, unit can suffer some loses
|
Campaign's
core units
Open General allows to define units to
become core on any scenario of a campaign, not only the first one.
Also there is a new flag on campaign file to reset all core units on
any scenario, as it first scenario will be replayed.
|
Barrage
Fire (Bombard)
Scenario must enable this optional
feature.
Then, artillery units and capital ships, having non zero "bomber size"
value (same than level bombers), can fire to empty hexes in order to
blow up bridges, towns, airfields,... on that hex.
If hex had any unspotted enemy unit, then:
- Unit's entrenchment is reduced
by 2
- Unit strength can suffer up to 1
strength point - although cannot be destroyed by this action
- Unit can suffer some lasting
suppression
- Unit can get reduced ammo and fuel
|
AD
and Flak units can intercept
planes while flying
This option must be enabled on
scenario.
If AD/Flak is hidden plane is fired as soon as it enter any surrounding
hex. Plane can go on flying after fired.
If AD/Flak was spotted, it only fires if plane stops on any surrounding
hex.
|
|
Extended
LOS
Must be enabled in scenario file.
This option reduces spotting ground units:
- mountain, hills and
cities cut spotting from 2 and up for ground units
- forest cannot be
spotted from distance>1
- if gnd unit is
obstructed, no further spot from behind that hex
And for Air units:
- forest and cities
cannot be spotted from 2 and up from air.
|
|
External
tables
Some of the internal tables used by
the game, can be overridden by using external tables (text files).
These are the tables you can currently override:
- Weather.txt - modify weather tables
- Terrain.txt - to modify
base-entrenchment, initiative-cap and cost to enter
- Eyear.txt - to
override default base year.
An alternative way, which takes precedence, is to include this
token: "BYEAR = ####" within first equipment item name (first
record of Equipment File)
|
Alternative
Air System
- Need to be enabled as scenario option
- When enabled planes won't use fuel and
scenario designer can define a bigger movement range for planes
- Planes must be assigned to a free "air-base"
(not assigned to another plane)
- any Air Supply Hexes (ASH = hexes
surrounding owned airfield terrain)
- Any hex having a dirt airfield
- A carrier
- When game engine finds a plane not in an ASH
at start of any game, engine will move to HQ at start of scenario.
- When player select a plane, a floating menu
pop up showing possible mission choices (similar to blow/build/repair
menu)
- Once a mission is selected, possible hexes
to fly would be highlighted (same than now), but restricted according
the air mission type.
- Possible missions would be:
- #0
Do nothing, that is plane will refit at the end of player turn.
- #1
Change Base (move to another free ASH). This would allow to fly, within
full movement range, to another free air-base.
- #2
Normal
Move/Attack/Bombard. Almost the same than now, except plane will return
automatically to its air-base at the end of enemy turn.
- #3
Recon fly. Plane
will fly to spot some hex. Plane will not be attacked or intercepted
from spotted enemies, but can be intercepted by hidden fighters and
AD/Flak if interception option is enabled. If intercepted they will
abort the mission flying back to air-base. Once fly is completed they
will return immediately to air-base. Planes require an special
attribute to be defined in efile for this mission type
- #4
Wild-Weasel. Plane
will fly to attack ground AD/Flaks. Plane will not be attacked or
intercepted from spotted enemies, but can be intercepted by hidden
fighters and AD/Flak if interception option is enabled. If intercepted
they will abort the mission flying back to air-base. No Air Defense nor
interceptors will support defender during the attack and once attack is
completed they will return immediately to air-base. Planes require an
special attribute to be defined in efile for this mission type.
- #5
Supply ground
units. Plane will fly to supply the friend ground unit under plane.
Planes require an special attribute to be defined in efile for this
mission type. At the end of enemy player turn, it would fly back to
air-base
- Supply of planes will only happen when it
has not played any mission (not moved) at the end of player turn or
manually like you do now.
- when unit is embarked in Air Transport,
player should move and disembark it (option to disembark keeps enabled
after movement), otherwise unit will be carried back to the air-base
and disembarked there. If unit is not airborne, only airfield terrain
will be selected to move, so player should check carefully the map as
some hexes can be hardly noticed.
Planes will return to their base
automatically, and will find an alternative one if their air-base is
not available. If found any out of range they will fly anyway but with
some loses and if no one is found, they will withdraw from map -
although will be available for next scenario if core units.
|
| New
scenario choice type
This is a new file-type .xsch
to be added to campaign path in any slot designer wants to run choices.
.xsch
files define a map to show in game (and Suite) and a list of choices
(no hard coded limited); each one defining which campaign's slot to go
next, a flag to click on and optionally a prestige to increase / reduce
(added after previous scenario award and so not affected by any cap - .xsch
do not define any cap and neither a date. There is also an option to
allow any choice to be played only once.
New Suite will include a new tool to edit .xsch
files, once added to campaign path (new button added to bottom of
scenario list)
This is a screen-shot from Suite campaign editor for .xsch
entry
http://i157.photobucket.com/albums/t50/lguzval/barbarrosa-choice.jpg
and this from the .xsch
editor
http://i157.photobucket.com/albums/t50/lguzval/barbarrosa-north.jpg
And this is how it will show up in game
http://i157.photobucket.com/albums/t50/lguzval/barbarrosa-choice-in-og.jpg
You can close the dialog to open another
option and once you click on OK button, choice will be close and
scenario slot for that choice will start as if it had followed in the
campaign path - that is prototypes are not checked in the .xsch
scenario but in the one you selected to go on.
|
| New
Rail movement/class/transport
Railways is done as a map layer similar than
roads, so they can be defined on any terrain and any hex can define
both roads and rails
Map can define also rail stations (stations for short) as main bases
for embark / disembark in trains. This is also a map layer, so it can
be set on any terrain having railways. Stations can be also built by
sappers during game if building is enabled
Units must load/unload using stations although efile designers can use
a new special attribute "No Station needed" to make units able to
load/unload on any railway hex
Unit can carry their organic transport when loading/unloading at
stations, but cannot carry when loading out of stations unless
transport has also the "No Station needed" special attribute. So if
unit has "No Station needed" attribute and transport has not, then
embarking/disembarking out of Station would mean losing the transport,
but if transport also have "No Station needed" attribute unit could
carry it.
Same than for roads, cost to enter each terrain using rails can be
defined using Terrain.txt file.
Trains is a non-organic transport and so it requires to be configured
at design time how many trains can be used at any time (trains pool)
similar to air and naval transport
|
| New
trigger hexes
New scenario map data can define any hex as
be a "trigger" so any ground unit entering that hex will trigger the
action defined
These are the current trigger types available:
- "Cheerful welcome" .- replenish fuel and ammo
- "Troop improvement".- Random experience or
defined by parameter
- "Prototype".- Units available from next
month to current scenario date with a 9 months time frame
- "Commendation" .- Can get a random leader if
available
- "Extra Prestige/Good press".- Random or
defined by parameter increase in prestige
- "Change AI stance".- Parameter not
meaningful, just toggles AI stance
- "Reveal to the player the map for one turn
(spy info on enemy )".- Random or defined by parameter the radious of
map revealed for that turn
When player's unit enters a trigger-hex, a
pop up message will inform on what happened, but not when AI triggers
any
|
New
Counter Battery fire (CBF)
How it works:
1.- When any artillery or surface-ship fires to enemy unit, counter
battery fire (CBF) is checked
2.- First enemy unit having CBF attribute able to fire to attacker,
will fire using half of its strength, as far as it has not made another
CBF in that turn yet
So:
* Only 1 unit can fire as CBF each combat.
* Any unit can fire as CBF only once per turn.
* Only artillery can do CBF to another artillery
* Only ships can do CBF to other ships.
|
New
option for dropping airborne units
When this new option is enabled, airborne units dropping on hex not
airfield, have a chance to actually drop in a different hex than the
one player select.
Probability for normal drop is affected by:
- weather
- 70% if weather is good
- 40% if overcast
- 30 if raining
- 20% if snowing
- Unit's bars, +5% for each bar
- if unit has leader adds +5%
If unit fails to drop on desired position,
it can finish on any of the six surrounding hexes the unit can enter
(so no impassable rivers or escarpments) randomly selected. When this
result in the unit being dropped into an hex occupied by an unspotted
enemy unit, airborne fights a surprise combat against that enemy
|
Custom
languages
Open General interface can be translated (up to a point) to different
languages as far as no Unicode is required.
Text files for campaigns and scenarios can exist also to allow reading
in different languages and then Open General will load when possible
Language mechanism is completely optional, as all strings are included
in executable. Default is English
To enable additional languages you need to set up a String-XX.txt file,
being XX the ISO 639-1 code (http://en.wikipedia.org/wiki/ISO_639-1).
for desired language, and place it into your main OPENGUI folder.
When Open General finds one or more Strings-??.txt files, it adds
additional entries to language combo-box available in User Settings
Dialog. So if you drop down the list and select a different language,
all strings will be read from that Strings-XX.txt file.
Efile folders can also include different Text-XX subfolders to hold
text files in different languages, so translated NATIONS.tx TERRAIN.txt
STRINGS_EFIlE.txt ... can be placed into Text-XX subfolder and
translated text files for scenarios and campaigns can be placed in
Text-XX/SCENARIO subfolder so when XX language is selected OG will try
to load text files from those Text-XX subfolders first and any not
found will be loaded from normal folders
Installer includes for EFILE_OLGWW2 a Text-ES subfolder with a
Text-ES/SCENARIO including text files translated to Spanish for DAK
campaign
|
Attachments
This is a completely optional feature allowing to assign any unit up to 2
attachments. All attachments settings are defined by .cfg files.
- Each attachments implies a fixed hard-code behavior
- All types can modify 2 aspects of unit (parameters), first one supposedly is a
bonus and second one supposedly is a penalty
- When parameter is a number it is customizable. Second parameter is always a
number so designer can set as zero to disable any penalty.
- Negative numbers are converted, so no parameter can be reversed from bonus to
penalty or reverse.
- Cost of parameters is made by a fixed number plus a percentage of the unit cost
receiveing the attachment.
- All number related to attachments can be customizing by using Equip, Campaign or
Scenario .cfg file
- Attachments are optional by nature, as they must be enabled using a .cfg file
(Equip, Campaign or Scenario)
- .CFG filesallow customizing:list]
- If attachments are used (attach_on=1)
- Default minimal cost for each attachment (attach_mincost=30)
- Default percentage factor of unit cost ( attach_factor=25)
These values can be further customized for each type
* attachment cost = attach_mincost + (unit cost x attach_factor) /100
- There are these types of attachments to pick:
- Recon:
+ Increase Spot according first param
- Reduce Movement according second param
- Air Defense:
+ Increase AA/AD according first param
- Reduce Inititiative according second param
- Bridging:
+ Gives Bridge special to unit
- Reduce Movement according second param
- AntiTank:
+ Increase HA according first param
- Reduce Movement according second param
- Support :
+ Increase MaxAmmo according first param
- Reduce Movement according second param
- Forward Observer:
+ Increase SA and HA to adjacent indirect targets according first param
- Reduce Inititiative according second param
- Special Munition:
+ Increase dice used to fire according first param
- Reduce Movement according second param
- FastEntrench:
+ Increase TerrainBaseEntrench according first param
- Reduce Inititiative according second param
|
Green replacements
This is a completely optional feature allowing to change default behavior for replacements.
Settings must be enabled and configured using .cfg files by defining certain $parameters
to modify default behaviors.
- Cost for green replacements, default=25%
- Cost for elite replacements, default=100% (so you could set as 150% for elite and 100% for green).
- The percentaje of green replacements that will come with same experience that unit. Default 0.
- Limit for unit experience. Here default could be 599 or 65535.
- Factor for bars reducing experience gained in combat, default 0 (no decrease)
but can set as 10 (50% for 5 bars) or even 20 making no experience increasing once unit gets 5 bars
- If Leaders must be removed when unit loses all bars, default=0.
- If automatic refit on next scenario should use greens, default=0 (use elite)
... as far as campaign option to "disable autorefit" is not enabled.
|
