Matrix Games

quote:

SetEvtOccurs = EventName; OccParam; Value

...

Value

Integer; [0, 999]

quote:

Note: To make an event dormant, set MaxOccurs to 0, or set cuOccurs to a number which is equal or greater than the current Maximum number of times it can be fired.

quote:

Description

TRUE if the Number of Battles that change National Morale compares to the Value.

...

Parameters

<Operator>

One of

=, <, >, <=, >=

<No. of Battles>

Integer (1-999)

<Operator>

One of

=, <, >, <=, >=

<Value>

Integer (1-999)

quote:

ORIGINAL: berto


Version: Public Beta Patch 1.01 (released 20121025?)

Bug: Script command syntax/usage warnings.

11 instances of questionable usage of SelectUnqUnit.

---

---

WARNING: in Events/2-GreatMithridaticWar75.sct, at (or near) line 2449: suspicious, undocumented usage of SelectUnqUnit, SelUnqUnit is preferred

in event evt_nam_SLV_CrixosJoinsSpartacus:

2440 MinDate = -073/07/01
2441 MaxDate = -068/03/01
2442
2443 SelectFaction = $SLV
2444 EvalEvent = evt_nam_SLV_SpartacusRevolt;=;1
2445 EvalUnqUnit = Spartacus
2446
2447 Actions
2448 DescEvent = evt_desc_ROM_Reinforcement1
2449> SelectUnqUnit = Spartacus
2450 ChangeFacMorale = 1
2451 Replacement = SLV;$famElite;1
2452 Replacement = SLV;$famMilitia;1
2453
2454 SelectFaction = $SLV
2455 CreateGroup
2456 Posture = $Defensive
2457 SetKind = $Land
2458 Entranch = 0

http://www.ageod.net/agewiki/SelUnqUnit

Syntax: SelUnqUnit = Name [;CondSkip][;OnlyUnfixed][;OnlyFixed] [;RestrictFac]

At the AGEWiki, there is a page for SelUnqUnit, but not for SelectUnqUnit.

IIRC, at one time, there was a SelectUnqUnit page that linked to the current SelUnqUnit page. I also recall seeing a comment like "SelUnqUnit is preferred." But maybe my memory deceives me.

In the kwd database, across all games, there are

---

[root@berto agelint]# ./kwddat SelectUnqUnit | awk '{t+=$1}; END {print t}'
20

---

20 instances of SelectUnqUnit:

---

[root@berto agelint]# ./kwddat SelectUnqUnit
1 SelectUnqUnit = 13e Corps d'Arm�e
1 SelectUnqUnit = 7th Scouting Division
1 SelectUnqUnit = Division d'Espagne
1 SelectUnqUnit = Eduard Vogel von Falckenstein
1 SelectUnqUnit = Erie Squadron
1 SelectUnqUnit = Friedrich Franz II. von Mecklenburg
1 SelectUnqUnit = George Pearson
1 SelectUnqUnit = James A. Lindsay
1 SelectUnqUnit = William F. Williams
11 SelectUnqUnit = Spartacus

---

11 of them are in AJE:

---

[root@berto agelint]# ./kwddat SelectUnqUnit aje
11 SelectUnqUnit = Spartacus

---

But clearly SelUnqUnit is preferred, there being

---

[root@berto agelint]# ./kwddat SelUnqUnit | awk '{t+=$1}; END {print t}'
1281

---

1281 instances of SelUnqUnit across all the games.

A bug? Or another false positive?

The other 10 instances of SelectUnqUnit usage in AJE:

WARNING: in Events/2-GreatMithridaticWar75.sct, at (or near) line 2495: suspicious, undocumented usage of SelectUnqUnit, SelUnqUnit is preferred

WARNING: in Events/2-GreatMithridaticWar75.sct, at (or near) line 2541: suspicious, undocumented usage of SelectUnqUnit, SelUnqUnit is preferred

WARNING: in Events/2-GreatMithridaticWar75.sct, at (or near) line 2584: suspicious, undocumented usage of SelectUnqUnit, SelUnqUnit is preferred

WARNING: in Events/2-GreatMithridaticWar75.sct, at (or near) line 2626: suspicious, undocumented usage of SelectUnqUnit, SelUnqUnit is preferred

WARNING: in Events/2b-Spartacus73.sct, at (or near) line 529: suspicious, undocumented usage of SelectUnqUnit, SelUnqUnit is preferred

WARNING: in Events/2b-Spartacus73.sct, at (or near) line 575: suspicious, undocumented usage of SelectUnqUnit, SelUnqUnit is preferred

WARNING: in Events/2b-Spartacus73.sct, at (or near) line 621: suspicious, undocumented usage of SelectUnqUnit, SelUnqUnit is preferred

WARNING: in Events/2b-Spartacus73.sct, at (or near) line 664: suspicious, undocumented usage of SelectUnqUnit, SelUnqUnit is preferred

WARNING: in Events/2b-Spartacus73.sct, at (or near) line 706: suspicious, undocumented usage of SelectUnqUnit, SelUnqUnit is preferred

WARNING: in Events/2b-Spartacus73.sct, at (or near) line 2139: suspicious, undocumented usage of SelectUnqUnit, SelUnqUnit is preferred

---

---

Hope this helps.

More WARNINGs to follow.

[Disclaimer: I make no claim about the significance or insignificance of any discovered bug, problem, glitch, or anomaly. Whether or not it impacts game play, or goes entirely unnoticed. Whether in the larger scheme of things it's important, or unimportant. I just call them as I see them.]

quote:

ORIGINAL: berto


Version: Public Beta Patch 1.01 (released 20121025?)

Bug: Script command syntax/usage warnings.

8 instances of questionable usage of AddDynGraphic.

---

---

WARNING: in Scripts/ScriptSEV193.ini, at (or near) line 6512: non-standard use of integer 0 instead of recommended <TerrainUID> alias

6503 AddDynGraphic = $Zenobia;CastraLegionis.png;CastraLegionis.png;NULL;100;40;strCastraLegionis
6504 AddDynGraphic = $Samaria;CastraLegionis.png;CastraLegionis.png;NULL;10;130;strCastraLegionis
6505 AddDynGraphic = $Mareotis;CastraLegionis.png;CastraLegionis.png;NULL;125;35;strCastraLegionis
6506 AddDynGraphic = $Nubae;CastraLegionis.png;CastraLegionis.png;NULL;285;80;strCastraLegionis
6507 NULL = NULL
6508 NULL = NULL
6509 AddDynGraphic = $Aneda;AntonineWall.png;AntonineWall.png;NULL;10;60;strAntonineWall
6510 AddDynGraphic = $Alauna;HadrianWall.png;HadrianWall.png;NULL;140;-80;strHadrianWall
6511 AddDynGraphic = $Pons Aelius;ProvinciaeCapitolum.png;ProvinciaeCapitolum.png;NULL;147;86;strProvinciaeCapitolum
6512> AddDynGraphic = $Londinium;ProvinciaeCapitolum.png;ProvinciaeCapitolum.png;0;228;287;strProvinciaeCapitolum
6513 AddDynGraphic = $Londinium;Mercatus.png;Mercatus.png;NULL;183;240;strMercatus
6514 AddDynGraphic = $Eboracum;Armoriae.png;Armoriae.png;NULL;125;130;strArmoriae
6515 NULL = NULL
6516 AddDynGraphic = $Aurelia Aquensi;ProvinciaeCapitolum.png;ProvinciaeCapitolum.png;NULL;191;89;strProvinciaeCapitolum
6517 AddDynGraphic = $Colonia Agrippa;ProvinciaeCapitolum.png;ProvinciaeCapitolum.png;7;245;137;strProvinciaeCapitolum
6518 AddDynGraphic = $Vagiones;ProvinciaeCapitolum.png;ProvinciaeCapitolum.png;7;197;70;strProvinciaeCapitolum
6519 AddDynGraphic = $Durocorturum;ProvinciaeCapitolum.png;ProvinciaeCapitolum.png;0;257;70;strProvinciaeCapitolum
6520 AddDynGraphic = $Tegua;ProvinciaeCapitolum.png;ProvinciaeCapitolum.png;0;215;140;strProvinciaeCapitolum
6521 AddDynGraphic = $Burdigala;ProvinciaeCapitolum.png;ProvinciaeCapitolum.png;0;170;115;strProvinciaeCapitolum

http://www.ageod.net/agewiki/AddDynGraphic

Syntax: AddDynGraphic = <RgnUID>;<ImageName>;<AltWeatherImgName>;<TerrainUID>;<CooX>;<CooY>;<Tooltip>

No doubt the engine will accept 0 rather than a proper alias for <TerrainUID>.

But is that good scripting practice?

In AJE, there are

---

[root@berto agelint]# ./kwddat AddDynGraphic aje | awk -F\; 'length($4) == 1' | wc -l
8

---

8 instances of this questionable usage of an integer rather than a <TerrainUID> alias.

In AJE, and across all games, there are

---

[root@berto agelint]# ./kwddat AddDynGraphic aje | awk -F\; 'length($4) != 1' | wc -l
215

[root@berto agelint]# ./kwddat AddDynGraphic | awk -F\; 'length($4) != 1' | wc -l
331

---

215 and 331 instances, respectively, of "proper" usage, i.e., a <TerrainUID> alias.

Other than the 8 instances in AJE, no other game has this "fault":

---

[root@berto agelint]# ./kwddat AddDynGraphic | awk -F\; 'length($4) == 1' | wc -l
8

---

Other instances of this "fault":

WARNING: in Scripts/ScriptSEV193.ini, at (or near) line 6517: non-standard use of integer 7 instead of recommended <TerrainUID> alias

WARNING: in Scripts/ScriptSEV193.ini, at (or near) line 6518: non-standard use of integer 7 instead of recommended <TerrainUID> alias

WARNING: in Scripts/ScriptSEV193.ini, at (or near) line 6519: non-standard use of integer 0 instead of recommended <TerrainUID> alias

WARNING: in Scripts/ScriptSEV193.ini, at (or near) line 6520: non-standard use of integer 0 instead of recommended <TerrainUID> alias

WARNING: in Scripts/ScriptSEV193.ini, at (or near) line 6521: non-standard use of integer 0 instead of recommended <TerrainUID> alias

WARNING: in Scripts/ScriptSEV193.ini, at (or near) line 6522: non-standard use of integer 0 instead of recommended <TerrainUID> alias

WARNING: in Scripts/ScriptSEV193.ini, at (or near) line 6546: non-standard use of integer 0 instead of recommended <TerrainUID> alias

Another false positive, or something to correct? Your call.

---

---

Hope this helps.

More WARNINGs to follow.

[Disclaimer: I make no claim about the significance or insignificance of any discovered bug, problem, glitch, or anomaly. Whether or not it impacts game play, or goes entirely unnoticed. Whether in the larger scheme of things it's important, or unimportant. I just call them as I see them.]

quote:

ORIGINAL: berto


Version: Public Beta Patch 1.01 (released 20121025?)

Bug: Script command syntax/usage warnings.

7 instances of questionable usage of SetEvtOccurs.

---

---

WARNING: in Events/BanditsRaidsPirates_SEV193.sct, at (or near) line 997: suspicious use of negative value -2

in event evt_nam_CMN_TooManyActiveBrigands_A:

988 ChangeFacMorale = -3
989
990 SelectFaction = $CLO
991 ChangeFacMorale = -3
992
993 SelectFaction = $PES
994 ChangeFacMorale = -3
995
996 SelectFaction = $SLV
997> SetEvtOccurs = evt_nam_CMN_ActiveBandits;CuOccurs;-2
998
999 EndEvent
1000
1001 SelectFaction = $CMN
1002
1003 SelectFaction = $CMN
1004 StartEvent = evt_nam_CMN_TooManyActiveRaids_A|999|2|evt_txt_CMN_TooManyActiveRaids_A|Event-Img_Plebis05|NULL|NULL
1005
1006 Conditions

http://www.ageod.net/agewiki/SetEvtOccurs

At the AGEWiki, it says:

quote:

SetEvtOccurs = EventName; OccParam; Value

...

Value

Integer; [0, 999]

It also says:

quote:

Note: To make an event dormant, set MaxOccurs to 0, or set cuOccurs to a number which is equal or greater than the current Maximum number of times it can be fired.

I don't doubt that the engine will accept a -2 value, but are there any bad side effects? Maybe not, but in any case this doesn't conform to the AGEWiki docs.

Of the

---

[root@berto agelint]# ./kwddat SetEvtOccurs | awk '{t+=$1}; END {print t}'
5226

---

usages of SetEvtOccurs across all games, here are the small handful with a negative integer value (the first one, and the last three examples, being for AJE):

---

[root@berto agelint]# ./kwddat SetEvtOccurs | egrep ";[[:space:]]*\-[[:digit:]]"
1 SetEvtOccurs = evt_nam_CMN_SlaveRevoltsInProgress;CuOccurs;-1
1 SetEvtOccurs = evt_nam_CSA_KY_FixAIUnits;MaxOccurs;-999
1 SetEvtOccurs = evt_nam_RED_PartialMobilization_AIActivate2;CuOccurs;-1
1 SetEvtOccurs = evt_nam_RED_PartialMobilization_AIActivate3;CuOccurs;-1
1 SetEvtOccurs = evt_nam_RED_PartialMobilization_AIActivate;CuOccurs;-1
1 SetEvtOccurs = evt_nam_USA_KY_FixAIUnits;MaxOccurs;-999
2 SetEvtOccurs = evt_nam_CMN_ActiveBandits;CuOccurs;-2
2 SetEvtOccurs = evt_nam_CMN_ActivePirates;CuOccurs;-3
2 SetEvtOccurs = evt_nam_CMN_ActiveRaids;CuOccurs;-3

---

Other instances of this "fault" in AJE:

WARNING: in Events/BanditsRaidsPirates_SEV193.sct, at (or near) line 1029: suspicious use of negative value -3

WARNING: in Events/BanditsRaidsPirates_SEV193.sct, at (or near) line 1061: suspicious use of negative value -3

WARNING: in Events/BanditsRaidsPirates_YF68.sct, at (or near) line 997: suspicious use of negative value -2

WARNING: in Events/BanditsRaidsPirates_YF68.sct, at (or near) line 1029: suspicious use of negative value -3

WARNING: in Events/BanditsRaidsPirates_YF68.sct, at (or near) line 1061: suspicious use of negative value -3

WARNING: in Events/SlaveRevolts_YF68.sct, at (or near) line 159: suspicious use of negative value -1

---

---

Hope this helps.

More WARNINGs to follow.

[Disclaimer: I make no claim about the significance or insignificance of any discovered bug, problem, glitch, or anomaly. Whether or not it impacts game play, or goes entirely unnoticed. Whether in the larger scheme of things it's important, or unimportant. I just call them as I see them.]

quote:

ORIGINAL: berto


Version: Public Beta Patch 1.01 (released 20121025?)

Bug: Script command syntax/usage warnings.

6 instances of questionable usage of EvalBattles.

---

---

WARNING: in Events/1-MariusSulla87.sct, at (or near) line 2181: suspicious, undocumented usage of -4 as negative final parameter

in event evt_nam_PON_GalatianExecutions:

2172
2173 SelectFaction = $CMN
2174 SelectRegion = $Ancyra
2175 StartEvent = evt_nam_PON_GalatianExecutions|1|2|evt_txt_PON_GalatianExecutions|Event-Img_Assassination02|$Ancyra|NULL
2176
2177 Conditions
2178 MinDate = -087/01/01
2179
2180 SelectFaction = $PON
2181> EvalBattles = >=;2;<=;-4
2182
2183 Actions
2184 SelectRegion = $Rhodos
2185 SetPillage = 1
2186 ChgFacEngagementPts = 1
2187 ChangeMoneyPool = 50
2188 ChangeFacMorale = 1
2189 ChangeLoyaltyFac = $Area_Galatia;-50
2190 ChangeLoyaltyFac = $Theater_Asia_Minor;-15

http://www.ageod.net/agewiki/EvalBattles

Syntax: EvalBattles = <Operator>;<No. of Battles>;<Operator>;<Value>

At the AGEWiki, it says:

quote:

Description

TRUE if the Number of Battles that change National Morale compares to the Value.

...

Parameters

<Operator>

One of

=, <, >, <=, >=

<No. of Battles>

Integer (1-999)

<Operator>

One of

=, <, >, <=, >=

<Value>

Integer (1-999)

Again, no doubt the engine will not choke on a negative number. And if not a typo, maybe this is some "clever" kludge to achieve some special purpose or another. But it certainly defies the AGEWiki docs.

Other instances of this "fault":

WARNING: in Events/3-CaesarPompey50.sct, at (or near) line 3771: suspicious, undocumented usage of -4 as negative final parameter

WARNING: in Events/3-CaesarPompey50.sct, at (or near) line 3801: suspicious, undocumented usage of -4 as negative final parameter

WARNING: in Events/3-CaesarPompey50.sct, at (or near) line 3939: suspicious, undocumented usage of -4 as negative final parameter

WARNING: in Events/3-CaesarPompey50.sct, at (or near) line 4855: suspicious, undocumented usage of -4 as negative final parameter

WARNING: in Events/3-CaesarPompey50.sct, at (or near) line 4974: suspicious, undocumented usage of -4 as negative final parameter

---

---

Hope this helps.

More WARNINGs to follow.

[Disclaimer: I make no claim about the significance or insignificance of any discovered bug, problem, glitch, or anomaly. Whether or not it impacts game play, or goes entirely unnoticed. Whether in the larger scheme of things it's important, or unimportant. I just call them as I see them.]

quote:

EvalBattles

quote:

ORIGINAL: berto


Version: Public Beta Patch 1.01 (released 20121025?)

Bug: Script command syntax/usage warnings.

2 instances of questionable usage of Attributes, 1 of NativeTag, 1 of CustomNames.

---

---

WARNING: in GameData/Models/168NOMNomadic Cavalry.mdl, at (or near) line 62: missing field (duplicate ||)

53 IsSupport = 0
54 SupplyUsage = 2
55 SupplyStore = 4
56 AmmoUsage = 1
57 AmmoStore = 4
58 ShareSupply = 1
59 SupHitPen = 25
60 SupMovePen = 25
61 SupCbtPen = 50
62> Attributes = *WeatherResist3* 100||*FullPillager*|*screener*|*retreater*|*disrupt*|*SkipAssault*
63 VPValue = 1
64 Money = 5
65 Conscript = 0
66 WarSupply = 0
67 Days = 60
68 Morale = 0

Syntax: Attributes = <Attrib> [|<Attrib>] ...

Another instance of 'Attributes ... ||':

WARNING: in GameData/Models/170NOMNomadic Horse Archer.mdl, at (or near) line 65: missing field (duplicate ||)

---

---

WARNING: in GameData/Factions/0-ROM.fac, at (or near) line 6: missing field (duplicate ||)

1 UID = 0
2 FactionTag = ROM
3 Kind = 0
4 DisplayTag = ROM
5 CoopTag = ROM|SOC|MAS|RHO
6> NativeTag = ROM|SOC|MAS|SYR|PER|NAB|VEN|RHO|OSR|LAG|SEL|JUD|MAU|GLT|CAP|BIT|VAS||CEL|HEL|ORI|BAL|GER|BOS
7 Name = $fac_Name_ROM
8 ShortName = $fac_ShortName_ROM
9 AdjectiveF = $fac_AdjectiveF_ROM
10 AdjectiveM = $fac_AdjectiveM_ROM
11 Text = $fac_Text_ROM
12 PopName = $fac_PopName_ROM
13 InterfElt1 = Flags_Interface_ROM.png
14 InterfElt2 = flag_ROM_alt.png
15 RecoverRate = 100

Syntax: NativeTag = FacTag [|FacTag] [|FacTag] ...

---

---

WARNING: in GameData/Units/14ROMLegio Prov. .uni, at (or near) line 20: missing field (duplicate ||)

11 ModelType1 = $mdl_ROM_Inf0|2
12 FamilyType0 = $famLeader|1
13 FamilyType1 = $famLine|6
14 FamilyType2 = $famSkirmisher|2
15 CmdCost = 3
16 Pillage = 0
17 BuildRule = $recCity
18 BuildWeight = 5
19 Area = $Recruit_Italia
20> CustomNames = I Italia Prov.|II Italia Prov.|III Italia Prov.|IV Italia Prov.|V Italia Prov.||VI Italia Prov.|I Cisalpina Prov.

Syntax: CustomNames = Name [|Name] [|Name] ...

---

---

Doubtless these double '||' are minor problems, mere annoyances (if they are noticed at all).

Hope this helps.

Thus ends my report of discovered syntax/usage WARNINGs in the latest AJE beta release.

Next up: miscellaneous bits and pieces.

[Disclaimer: I make no claim about the significance or insignificance of any discovered bug, problem, glitch, or anomaly. Whether or not it impacts game play, or goes entirely unnoticed. Whether in the larger scheme of things it's important, or unimportant. I just call them as I see them.]

quote:

ORIGINAL: BohémondAJE

quote:

ORIGINAL: berto

WARNING: in Scripts/ScriptSEV193.ini, at (or near) line 6512: non-standard use of integer 0 instead of recommended <TerrainUID> alias

...

But is that good scripting practice?

...

Another false positive, or something to correct? Your call.

Engine will make no difference between a valid alias ($Clear) or his numeric value (0). In fact aliases or only here to help human to script, engine only use numeric value.

So False positives.

quote:

ORIGINAL: berto


Version: Public Beta Patch 1.01 (released 20121025?)

Bug: Missing image files.

301 instances of 142 referenced image files not found.

---

---

In the script and data spec files, there are

---

telemann:/home/berto/games/ageod/agelint # awk '{t+=$1}; END {print t}' chkimages_aje_QA_20121101_lst.txt
301

---

301 instances of

---

elemann:/home/berto/games/ageod/agelint # wc -l chkimages_aje_QA_20121101_lst.txt
142 chkimages_aje_QA_20121101_lst.txt

---

142 referenced image files not found.

Here are the no-finds:

26 Army_Badge_ROM.png
4 Wood_moonsoon.png
4 WoodedHills_moonsoon.png
4 Savanna_rain.png
4 Mountain_moonsoon.png
4 Icefield_rain.png
4 Hills_moonsoon.png
4 Forest_moonsoon.png
4 Deep_Jungle_rain.png
4 Coastal_Waters_storm.png
4 Clear_moonsoon.png
3 Swamp_snow.png
3 Ricefield_rain.png
3 MapShield_WIS.png
3 MapShield_TTR.png
3 MapShield_TRX.png
3 MapShield_SRD.png
3 MapShield_POS.png
3 MapShield_PLP.png
3 MapShield_PHR.png
3 MapShield_OST.png
3 MapShield_ORI.png
3 MapShield_NOM.png
3 MapShield_HRL.png
3 MapShield_HEL.png
3 MapShield_FRA.png
3 MapShield_FLO.png
3 MapShield_CRU.png
3 MapShield_CMN.png
3 MapShield_CEL.png
3 MapShield_BLK.png
3 MapShield_BAL.png
3 MapShield_ATX.png
3 MapShield_ANA.png
3 MapShield_AFT.png
3 MapShield_AEM.png
3 Erroneous.png
3 Base_Flag_WIS.png
3 Base_Flag_TTR.png
3 Base_Flag_TRX.png
3 Base_Flag_SRD.png
3 Base_Flag_POS.png
3 Base_Flag_PLP.png
3 Base_Flag_PHR.png
3 Base_Flag_OST.png
3 Base_Flag_ORI.png
3 Base_Flag_NOM.png
3 Base_Flag_HRL.png
3 Base_Flag_HEL.png
3 Base_Flag_FRA.png
3 Base_Flag_FLO.png
3 Base_Flag_CRU.png
3 Base_Flag_CMN.png
3 Base_Flag_CEL.png
3 Base_Flag_BLK.png
3 Base_Flag_BAL.png
3 Base_Flag_ATX.png
3 Base_Flag_ANA.png
3 Base_Flag_AFT.png
3 Base_Flag_AEM.png
2 TropicalWaters_rain.png
2 TropicalWaters_moonsoon.png
2 Taiga_snow.png
2 Event-Img_Reinforcement08.png
2 Desert_sandstorm.png
2 Bocage_snow.png
1 Wood_tropical.png
1 WoodedHills_tropical.png
1 TropicalWaters_norm.png
1 Taiga_rain.png
1 Taiga_norm.png
1 Taiga_blizzard.png
1 symbol_hq2.png
1 Savanna_norm.png
1 Ricefield_snow.png
1 Ricefield_norm.png
1 RgnDecision_OnMap_Circumvallatio.png
1 RgnDecision_Circumvallatio.png
1 Ocean_storm.png
1 Mountain_tropical.png
1 Mercenarius.png
1 mdl_CMN_Sli.png
1 mdl_CMN_Skirmisher.png
1 mdl_CMN_Raider.png
1 mdl_CMN_Militia.png
1 mdl_CMN_LightInf.png
1 mdl_CMN_Jav.png
1 mdl_CMN_Inf.png
1 mdl_CMN_HvyInf.png
1 mdl_CMN_HvyCav.png
1 mdl_CMN_HJav.png
1 mdl_CMN_HArc.png
1 mdl_CMN_Cav.png
1 mdl_CMN_Archer0.png
1 Icefield_norm.png
1 Hills_tropical.png
1 Freeze_Ocean_snow.png
1 Freeze_Ocean_frozen.png
1 Freeze_Ocean_blizzard.png
1 Fort.png
1 Forest_tropical.png
1 Flags_Interface_WIS.png
1 Flags_Interface_TTR.png
1 Flags_Interface_TRX.png
1 Flags_Interface_SRD.png
1 Flags_Interface_POS.png
1 Flags_Interface_PLP.png
1 Flags_Interface_PHR.png
1 Flags_Interface_OST.png
1 Flags_Interface_ORI.png
1 Flags_Interface_NOM.png
1 Flags_Interface_MCR.png
1 Flags_Interface_HRL.png
1 Flags_Interface_HEL.png
1 Flags_Interface_FRA.png
1 Flags_Interface_FLO.png
1 Flags_Interface_CRU.png
1 Flags_Interface_CMN.png
1 Flags_Interface_CEL.png
1 Flags_Interface_BLK.png
1 Flags_Interface_BAL.png
1 Flags_Interface_ATX.png
1 Flags_Interface_ANA.png
1 Flags_Interface_AFT.png
1 Flags_Interface_AEM.png
1 Deep_Jungle_norm.png
1 Clear_tropical.png
1 Bocage_rain.png
1 Bocage_norm.png
1 Bocage_blizzard.png
1 Army_Badge_SYR.png
1 Army_Badge_SOC.png
1 Army_Badge_SMN.png
1 Army_Badge_SLV.png
1 Army_Badge_REV.png
1 Army_Badge_PIR.png
1 Army_Badge_MER.png
1 Army_Badge_GGR.png
1 Army_Badge_ETR.png
1 Army_Badge_EPI.png
1 Army_Badge_CAR.png
1 Army_Badge_BAR.png

No doubt many, perhaps most, of these are "false positives" in the sense that their absence is (a) not noticeable at all or (b) merely annoying.

But I report this, for what it's worth. (Maybe not much.)

If any are of concern, please let me know, and I will gladly provide you with file:lineno references.

---

---

I did not discover any references to missing data files. Nor did AGElint discover any problems in the Areas.ini and Regions/*.ini files. (Checking the many different file types is still a work-in-progress.)

I believe I had analyzed the latest available public patch, but I may be mistaken. Quite possibly some of my reported "bugs" etc. were corrected previously.

Thus concludes my series of AGElint reports on bugs, glitches & anomalies discovered in AJE Public Beta Patch 1.01 (released 20121025?).

Let me again observe that, for a new AGEOD game, Alea Jacta Est was relatively clean.

In

---

telemann:/media/KINGSTON/Games/AGEOD # du -skh "Alea Jacta Est"
2.4G Alea Jacta Est

---

2.4G of data across

---

telemann:/media/KINGSTON/Games/AGEOD # find "Alea Jacta Est" -type f -print | wc -l
21708

---

21,708 data files, for there to be just several hundred bugs, glitches & anomalies (of lesser or greater importance) is quite an achievement. Good job!

Some clarification:

I have taken 1-1/2 weeks over a couple dozen forum posts to convey this information. Much of the material I presented is not raw AGElint reporting, rather my command-line work -- entirely optional, not mandatory at all for AGElint operation -- to explain and justify the results. You do not have to be a Linux geek in order to run AGElint!

But AGElint itself required just 10-15 minutes to process all those thousands of files, all that 2.4G of data, in multiple passes, and output the various chk* report files. The agelint executable can error check a single script or data file and spit out results (or not, if the file is clean, bug-free) in the blink of an eye, as fast as you can enter the command and hit the Enter key.

With AGElint, you have a toolkit you can run again and again, as often as you wish, whenever you wish. All automated, no manual intervention required. (I used a simple command line, 'dochk aje QA', to generate all reports.)

I'll have more to say later about all of this later. But for now, in closing, two standard bits:

Hope this helps.

And:

[Disclaimer: I make no claim about the significance or insignificance of any discovered bug, problem, glitch, or anomaly. Whether or not it impacts game play, or goes entirely unnoticed. Whether in the larger scheme of things it's important, or unimportant. I just call them as I see them.]

quote:

ORIGINAL: BohémondAJE

quote:

ORIGINAL: berto

Version: Public Beta Patch 1.01 (released 20121025?)

Bug: Bad alias reference.

There are multiple references to an undefined region alias, $Egata.

Examples:

---

[root@berto AJE]# pwd
/media/KINGSTON/Games/AGEOD/Alea Jacta Est/AJE

[root@berto AJE]# ls
Aliases Fonts GameData Includes Saves Scripts Sounds
Events FrontEnd Graphics Logs Scens Settings

[root@berto AJE]# find Aliases GameData Includes Scripts Events Scens Settings -exec egrep -i "egata" {} \; | sort | uniq
AddToRegList = $Sirmium;$Singidunum;$Viminacium;$Mursa;$Egata;$Eravisci;$Racatae
AddToRegList = $Sirmium;$Singidunum;$Viminacium;$Mursa;$Egata;$Eravisci;$Racatae;$Sirmium;$Singidunum;$Viminacium;$Mursa;$Egata;$Eravisci;$Racatae
AddToRegList = $Sirmium;$Singidunum;$Viminacium;$Mursa;$Egata;$Eravisci;$Racatae;$Sulina;$Troesmis;$Tomi;$Scythia Minor;$Dorosturum;$Jatrus;$Novae;$Nicopolis;$Timacus

[that is all instances of the character string 'egata' in any of the relevant game data files & folders]

...

Note ; They are 3 more anomalies with the same ScriptCommand. If you want I can point you where. You help us improving our tool, I can help you improving yours.

quote:

ORIGINAL: berto

quote:

ORIGINAL: BohémondAJE

quote:

ORIGINAL: berto

Version: Public Beta Patch 1.01 (released 20121025?)

Bug: Bad alias reference.

There are multiple references to an undefined region alias, $Egata.

Examples:

---

[root@berto AJE]# pwd
/media/KINGSTON/Games/AGEOD/Alea Jacta Est/AJE

[root@berto AJE]# ls
Aliases Fonts GameData Includes Saves Scripts Sounds
Events FrontEnd Graphics Logs Scens Settings

[root@berto AJE]# find Aliases GameData Includes Scripts Events Scens Settings -exec egrep -i "egata" {} \; | sort | uniq
AddToRegList = $Sirmium;$Singidunum;$Viminacium;$Mursa;$Egata;$Eravisci;$Racatae
AddToRegList = $Sirmium;$Singidunum;$Viminacium;$Mursa;$Egata;$Eravisci;$Racatae;$Sirmium;$Singidunum;$Viminacium;$Mursa;$Egata;$Eravisci;$Racatae
AddToRegList = $Sirmium;$Singidunum;$Viminacium;$Mursa;$Egata;$Eravisci;$Racatae;$Sulina;$Troesmis;$Tomi;$Scythia Minor;$Dorosturum;$Jatrus;$Novae;$Nicopolis;$Timacus

[that is all instances of the character string 'egata' in any of the relevant game data files & folders]

...

Note ; They are 3 more anomalies with the same ScriptCommand. If you want I can point you where. You help us improving our tool, I can help you improving yours.

If I am reading you correctly, you have discovered problems that I have missed. False negatives, i.e., undetected, unreported genuine errors.

Yes, please, I would like to learn what you have discovered here. Improvements of every kind are good.

(Some background: Too many false positives makes it harder to separate the wheat (true positives) from the chaff (false positives). In my zeal to weed out false positives -- so as not to annoy -- in the AGElint code, on many occasions I have made the judgment call to disregard possible errors. Although it may seem that my zeal goes the other way; that I delight in pointing out errors in excess; no, in fact I attempt judiciously to limit my report of them. Drawing a fine line between false positives and true positives is not always easy. I try my best.)