"none" wrote:The "Supply" special only works for ground units, and you can't make a special "supply" plane (out of an ATP) to supply air units...
Yet it would be a nice feature to have, for it would allow tanker planes. In-flight refueling was already experimented in the 1920ies and became a staple of military aviation after WWII.
It would be nice if one could give the "supply" perk to Air Transports, making them resupply adjacent "air" units. It isn't even necessary to add a new checkbox: If you give the "supply" perk to a ground unit (land or naval), it only supplies ground units; If you give it to an ATP, it only supplies air units.
lvjtn wrote:while the healer scenario special sounds like a feature for fantasy efiles only, imo it can be useful for ww2/cold war scenarios too, but it should be restricted
what i want?
healer special working like an army base repairing the lightly damaged vehicles in order to send them back to fight immediately. e.g. israelis fought with mostly repaired tanks in the famous "valley of tears" tank battle in golan 1973. i want to represent this in my scenarios. now the healer gives +x sp for all adjacent ground units, but i want to exclude inf, guns (basicaly everything which can have gtp), and allow the repair only for vehicles (tank, spat, sparty, spad, recon). as i see, an optional $healer_vehicle can do this
why not giving prestige to "buy" replacement?
because you can only fully refit the damaged units with this (except you use terrain, etc. restrictions), while i want to give +1 sp / turn only, and not everywhere on the map
What if units could move as soon as they debark from trains? Wouldn't it be better and more realistic?
(No, the actual "Marine" special doesn't do, because it would apply to all kind of non-organic transports, including naval landings.)
Obviously this would need to be configurable (in the .cfg I guess), so it won't break old stuff and people hating it could avoid it.
We agreed discarding logical operators, as that is dangerous, but I keep wish this open to analyze how can be allowed to enable/disable any of the conditions, which would make setting them easier.i'm just thinking about the possibilities to make the multiple conditions less confusing for the designers (maybe tabs, on the first one any of the all conditions can be activated by a radio button, then logical operator can be selected on a 2nd tab, and on a 3rd tab the possible second condition can be selected (not all, as some conditions are exclusive like "take" vs. "hold" vhs)
... in this way we can prevent winning by "kill all units" which is a "built in" condition now for most other conditions what cannot be disabled
Aleksandr wrote:Right now it is possible to draw airfield, port, rr station... I'd love if the engine would be able to draw a simple city on map.
hy this idea: Cities are the main victory conditions in OG.
With cities drawn on the map, it'll be much easier to use the already available maps without unnecessary modifications. While now you need a graphic program and some kind of skill if you wish to mod the map, with my idea implemented all you would need is to change the terrain in Suite and mark the "paint city" checkbox. It'll be extremely easy to "mod" the available maps, thus it would spare us of hours of photoshopping and lots of redundant maps in repository.
The way to go should be either using tiled maps or editing the map-picture and including the edited map in the efile's MAP folder.mythos wrote:As far as i understand, the request is about an artificial drawing/painting of a hex (respectively a hex type) on a jpg/png map - which is what tiled maps do too. Why not letting the engine draw a "tile" on the "jpg/png" ?
# the engine already knows how to draw/paint
# there is a default icon set for hex tiles
# the city tile is sitting on the same position in the hex tiles file
Teaching the engine to read the city tile and draw it on the jpg/png map shouldn't be too difficult - considering that everything else is already available
Last proposals:Currently there is only one unit's range value, it's PG2 way, and it basically works right for WW2 campaigns...,
I understand and don't negate this...;
There is no problem for WW2 era, as basically all planes have 0 (bomber) or 1(torpedo, rocket) hex of range..., so there is no visible issue ...;
The problem starts with modern campaigns, air units often have few hexes of range and it looks really bad when howitzer (with passive AA=1) fires back from range of 3-4 hexes (or more) ...;
IMHO it's bad enough that some howitzer (with AAMG) can shot down a jet fighter, but the almost unlimited range makes it so much worse...;
My suggestions is:
- new $var called: "gnd_air_range" (or "gnd_aa_range") limiting unit's AA range;
examples:
gnd_air_range = 0 - unit's AA range limited to air units above the ground unit
gnd_air_range = 1 - unit's AA range limited to 1 hex;
gnd_air_range = 2 - unit's AA range limited to 2 hexes;
...
gnd_air_range = 255 - unlimited range(default);
- (optional) separate values for ground and naval units ( "gnd_air_range" and "naval_air_range") ;
Andlguzman wrote:Default value for $gnd_air_range" (not present in CFG files) will be -1 not 255, then engine will use current rules:
- - ad class: no limit;
- - Flak class and CanAA:
- -air defense: limited to $flak_range;
- -attack and retaliation: no limit
- - ADS:
- -air defense: limited to $flak_range;
- -attack: no limit
- -retaliation: limited to $flak_range;
- - rest of units:
- -air defense: disabled;
- -attack : disabled;
- -retaliation: no limit;
Will review this later ...Waldzios wrote:
If you are using -1 as default, then additional condition (whenever $gnd_air_range is defined) will be necessary anyway (no matter what solution used)...
Then, as well you can go like that:
- - ad class: no limit;
- - Flak class and CanAA:
- -air defense: limited to $flak_range;
- -attack and retaliation: no limit (or $flak_range whenever $gnd_air_range is defined);
- - ADS:
- -air defense: limited to $flak_range;
- -attack: disabled;
- -retaliation: limited to $flak_range;
- - rest of units:
- -air defense: disabled;
- -attack : disabled;
- -retaliation: no limit (or $gnd_air_range whenever $gnd_air_range is defined);
I've opened a new topic DEV: More Efile SpecialsWhat if we could add six equipment special attributes without changing the file structure? .
Which ones would you like to have?
