RE: SVF 2.0alpha, 20120911: F2 key CTD (Full Version)

All Forums >> [Current Games From Matrix.] >> [American Civil War] >> American Civil War – The Blue and the Gray



Message


Chliperic -> RE: SVF 2.0alpha, 20120911: F2 key CTD (9/15/2012 7:02:07 AM)

"Old Guard" and new methods :-)




berto -> SVF 2.0alpha, 20120911: KY Blockade text errors (9/15/2012 3:05:19 PM)


In "Establish Blockade for Kentucky", the text says:

quote:

The neutrality of Kentucky allowed Confederates to purchase in the North industrial items they lacked. Allowing [emphasis added] this illegal traffic will reduce CSA WSU production but will be resented negatively in Kentucky and State borders [emphasis added] (Maryland, Delaware and Missouri). The Confederate loyalty will be raised in these States. moreover, the kentucky entry Level will be moved by 3 in favor of CSA.

Shouldn't that instead be (with fixes highlighted):

quote:

The neutrality of Kentucky allowed Confederates to purchase in the North industrial items they lacked. Disallowing this illegal traffic will reduce CSA WSU production but will be resented negatively in Kentucky and other border states (Maryland, Delaware and Missouri). The Confederate loyalty will be raised in these states. Moreover, the Kentucky entry Level will be moved by 3 in favor of the CSA.

Instead of "Disallowing", you might otherwise use "Forbidding" or "Outlawing".




Chliperic -> RE: SVF 2.0alpha, 20120911: KY Blockade text errors (9/15/2012 3:08:45 PM)

Fixed :-)




berto -> SVF 2.0alpha, 20120911: NM gain bug? (9/15/2012 8:37:55 PM)


1861, Early July. Playing as Union.

"4/10. Sir, whe [sic] have earned 1 NM from the bright overall situation (more VP than CSA)."

Yet, as reported at the Scores & Objectives display, Union VP 235 < Confederate VP 260. The Union VP trailed the previous turn too, IIRC.

(Union NM 102, Confederate NM 97.)

Save files posted on request.




Chliperic -> RE: SVF 2.0alpha, 20120911: NM gain bug? (9/15/2012 8:42:04 PM)

Yes I need the files and the scripreport file of the turn in the Scripts folder.




berto -> RE: SVF 2.0alpha, 20120911: NM gain bug? (9/15/2012 9:04:28 PM)


Here you go:

http://pikt.org/ageod/acw/NMGAINBUG.ZIP




Chliperic -> RE: SVF 2.0alpha, 20120911: NM gain bug? (9/15/2012 10:06:54 PM)

My events works fne. It seems the EvalVP command to be bugged. Incoherent results for this command:

No error in this script
--------------START OF SCRIPT----------------
Line 1: SelectFaction, selected: Confederacy
Line 3: Started processing event: evt_nam_CSA_NM_VP
Line 3: Event already referenced, current occurences 0 Max allowed: 999 <<Active>>
Line 6: Min date evaluated: 1861/05/13 converted to turn 2674 current turn 2674 True
Line 7: Max date evaluated: 1866/01/14 converted to turn 2786 current turn 2674 True
Line 9: EvalMorale: Confederacy Morale: 95 against 120 - Operator: <= Result: True
Line 10: EvalVP: Evaluating against Union VPs.
Line 10: EvalVP: Confederacy VP: 39 against 109 - Operator: >= Result: False
Line 18: Finished processing event: evt_nam_CSA_NM_VP
Line 18: ------------------------------
Line 22: SelectFaction, selected: Confederacy
Line 24: Started processing event: evt_nam_CSA_NM_VP2
Line 24: Event already referenced, current occurences 0 Max allowed: 999 <<Active>>
Line 27: Min date evaluated: 1861/05/13 converted to turn 2674 current turn 2674 True
Line 28: Max date evaluated: 1866/01/14 converted to turn 2786 current turn 2674 True
Line 30: EvalMorale: Confederacy Morale: 95 against 120 - Operator: <= Result: True
Line 31: EvalVP: Evaluating against Union VPs.
Line 31: EvalVP: Confederacy VP: 39 against 109 - Operator: >= Result: False
Line 40: Finished processing event: evt_nam_CSA_NM_VP2
Line 40: ------------------------------
Line 43: SelectFaction, selected: Union
Line 45: Started processing event: evt_nam_USA_NM_VP
Line 45: Event already referenced, current occurences 0 Max allowed: 999 <<Active>>
Line 48: Min date evaluated: 1861/05/13 converted to turn 2674 current turn 2674 True
Line 49: Max date evaluated: 1866/01/14 converted to turn 2786 current turn 2674 True
Line 51: EvalMorale: Union Morale: 101 against 120 - Operator: <= Result: True
Line 52: EvalVP: Evaluating against Confederacy VPs.
Line 52: EvalVP: Union VP: 300 against 97 - Operator: >= Result: True
Line 55: Entering triggered actions for event evt_nam_USA_NM_VP
Line 57: ChangeMorale Union New National Morale is 102
Line 60: Finished processing event: evt_nam_USA_NM_VP
Line 60: ------------------------------
Line 64: SelectFaction, selected: Union
Line 66: Started processing event: evt_nam_USA_NM_VP2
Line 66: This event is not yet referenced, base number of allowed occurences 999
Line 69: Min date evaluated: 1861/05/13 converted to turn 2674 current turn 2674 True
Line 70: Max date evaluated: 1866/01/14 converted to turn 2786 current turn 2674 True
Line 72: EvalMorale: Union Morale: 102 against 120 - Operator: <= Result: True
Line 73: EvalVP: Evaluating against Confederacy VPs.
Line 73: EvalVP: Union VP: 300 against 97 - Operator: >= Result: True
Line 74: Probability evaluated: Probability 5 rolled 61 False
Line 82: Finished processing event: evt_nam_USA_NM_VP2
In fact, in the line:

EvalVP: Confederacy VP: 39 against 109

39 is the number of free USA conscripts this turn and 109 the Union VP total

EvalVP: Union VP: 300 against 97

300 is the number of USA WSU next turn and 97 the CSA VP total

IMHO an error of register in the code...

Bad news... I have to write another events to get a similar effects.




Chliperic -> RE: New system (9/15/2012 10:51:12 PM)

New system: The cities controlled by CSA at start in the objective ldger are checked each turn for control. One event checks each turn if CSA has won 3 NM in a large battle: so 10 events are checked. If all events are fulfilled, CSA earns 2 NM each turn. For 9, 1NM. For 7 or 8, 1NM ( 75 % chances). At 6, 50% chance of gaining 1 NM…

Results should be the same.

USA will get NM with the same events ( so USA will have to conquer CSA cities).

Next version in a few hours…




Chliperic -> RE: New system (9/15/2012 10:58:50 PM)

For those interested by scripting, the new events chain; 1st tracking events, 10 evnst checking each a condition, 5 events evaluating results, and last event resetting tracker to 0. Written in 15 minutes.I will remove later the unnecessary strings in StartEvent lines.

SelectFaction = $CSA
SelectRegion = $Richmond, VA
StartEvent = evt_nam_CSA_NM_VP_Tracker|0|0|evt_txt_CSA_draft|Event-img_CSA_ConscriptionAct1864|$Richmond, VA|129

Conditions
MinDate = 1861/05/13
MaxDate = 1866/01/14




Actions


EndEvent




SelectFaction = $CSA
SelectRegion = $Richmond, VA
StartEvent = evt_nam_CSA_NM_VP|999|0|evt_txt_CSA_draft|Event-img_CSA_ConscriptionAct1864|$Richmond, VA|129

Conditions
MinDate = 1861/05/13
MaxDate = 1866/01/14

EvalMorale = <=;120
SelectFaction = $CSA
EvalRgnOwned = $Richmond, VA


Actions

SetEvtOccurs = evt_nam_CSA_NM_VP_Tracker;MaxOccurs;1;


SetEvtOccurs = evt_nam_CSA_NM_VP_Tracker;CuOccurs;1;

EndEvent

SelectFaction = $CSA
SelectRegion = $Richmond, VA
StartEvent = evt_nam_CSA_NM_VP2|999|0|evt_txt_CSA_draft|Event-img_CSA_ConscriptionAct1864|$Richmond, VA|129

Conditions
MinDate = 1861/05/13
MaxDate = 1866/01/14

EvalMorale = <=;120
SelectFaction = $CSA
EvalRgnOwned = $Shelby, TN


Actions

SetEvtOccurs = evt_nam_CSA_NM_VP_Tracker;MaxOccurs;1;


SetEvtOccurs = evt_nam_CSA_NM_VP_Tracker;CuOccurs;1;

EndEvent

SelectFaction = $CSA
SelectRegion = $Richmond, VA
StartEvent = evt_nam_CSA_NM_VP3|999|0|evt_txt_CSA_draft|Event-img_CSA_ConscriptionAct1864|$Richmond, VA|129

Conditions
MinDate = 1861/05/13
MaxDate = 1866/01/14

EvalMorale = <=;120
SelectFaction = $CSA
EvalRgnOwned = $Iberville, LA


Actions

SetEvtOccurs = evt_nam_CSA_NM_VP_Tracker;MaxOccurs;1;


SetEvtOccurs = evt_nam_CSA_NM_VP_Tracker;CuOccurs;1;

EndEvent


SelectFaction = $CSA
SelectRegion = $Richmond, VA
StartEvent = evt_nam_CSA_NM_VP4|999|0|evt_txt_CSA_draft|Event-img_CSA_ConscriptionAct1864|$Richmond, VA|129

Conditions
MinDate = 1861/05/13
MaxDate = 1866/01/14

EvalMorale = <=;120
SelectFaction = $CSA
EvalRgnOwned = $Davidson, TN


Actions

SetEvtOccurs = evt_nam_CSA_NM_VP_Tracker;MaxOccurs;1;


SetEvtOccurs = evt_nam_CSA_NM_VP_Tracker;CuOccurs;1;

EndEvent


SelectFaction = $CSA
SelectRegion = $Richmond, VA
StartEvent = evt_nam_CSA_NM_VP5|999|0|evt_txt_CSA_draft|Event-img_CSA_ConscriptionAct1864|$Richmond, VA|129

Conditions
MinDate = 1861/05/13
MaxDate = 1866/01/14

EvalMorale = <=;120
SelectFaction = $CSA
EvalRgnOwned = $Atlanta, GA


Actions

SetEvtOccurs = evt_nam_CSA_NM_VP_Tracker;MaxOccurs;1;


SetEvtOccurs = evt_nam_CSA_NM_VP_Tracker;CuOccurs;1;

EndEvent


SelectFaction = $CSA
SelectRegion = $Richmond, VA
StartEvent = evt_nam_CSA_NM_VP6|999|0|evt_txt_CSA_draft|Event-img_CSA_ConscriptionAct1864|$Richmond, VA|129

Conditions
MinDate = 1861/05/13
MaxDate = 1866/01/14

EvalMorale = <=;120
SelectFaction = $CSA
EvalRgnOwned = $Arkansas, AR


Actions

SetEvtOccurs = evt_nam_CSA_NM_VP_Tracker;MaxOccurs;1;


SetEvtOccurs = evt_nam_CSA_NM_VP_Tracker;CuOccurs;1;

EndEvent



SelectFaction = $CSA
SelectRegion = $Richmond, VA
StartEvent = evt_nam_CSA_NM_VP7|999|0|evt_txt_CSA_draft|Event-img_CSA_ConscriptionAct1864|$Richmond, VA|129

Conditions
MinDate = 1861/05/13
MaxDate = 1866/01/14

EvalMorale = <=;120
SelectFaction = $CSA
EvalRgnOwned = $Mobile, AL


Actions

SetEvtOccurs = evt_nam_CSA_NM_VP_Tracker;MaxOccurs;1;


SetEvtOccurs = evt_nam_CSA_NM_VP_Tracker;CuOccurs;1;

EndEvent


SelectFaction = $CSA
SelectRegion = $Richmond, VA
StartEvent = evt_nam_CSA_NM_VP8|999|0|evt_txt_CSA_draft|Event-img_CSA_ConscriptionAct1864|$Richmond, VA|129

Conditions
MinDate = 1861/05/13
MaxDate = 1866/01/14

EvalMorale = <=;120
SelectFaction = $CSA
EvalRgnOwned = $Warren, MS


Actions

SetEvtOccurs = evt_nam_CSA_NM_VP_Tracker;MaxOccurs;1;


SetEvtOccurs = evt_nam_CSA_NM_VP_Tracker;CuOccurs;1;

EndEvent



SelectFaction = $CSA
SelectRegion = $Richmond, VA
StartEvent = evt_nam_CSA_NM_VP9|999|0|evt_txt_CSA_draft|Event-img_CSA_ConscriptionAct1864|$Richmond, VA|129

Conditions
MinDate = 1861/05/13
MaxDate = 1866/01/14

EvalMorale = <=;120
SelectFaction = $CSA
EvalRgnOwned = $Charleston, SC


Actions

SetEvtOccurs = evt_nam_CSA_NM_VP_Tracker;MaxOccurs;1;


SetEvtOccurs = evt_nam_CSA_NM_VP_Tracker;CuOccurs;1;

EndEvent


SelectFaction = $CSA
SelectRegion = $Richmond, VA
StartEvent = evt_nam_CSA_NM_VP10|999|0|evt_txt_CSA_draft|Event-img_CSA_ConscriptionAct1864|$Richmond, VA|129

Conditions
MinDate = 1861/05/13
MaxDate = 1866/01/14

EvalMorale = <=;120
SelectFaction = $CSA
EvalBattles = >=;1;>=;2


Actions

SetEvtOccurs = evt_nam_CSA_NM_VP_Tracker;MaxOccurs;1;


SetEvtOccurs = evt_nam_CSA_NM_VP_Tracker;CuOccurs;1;

EndEvent

SelectFaction = $CSA
SelectRegion = $Richmond, VA
StartEvent = evt_nam_CSA_NM_VP_results|999|1|evt_txt_CSA_draft|Event-img_CSA_ConscriptionAct1864|$Richmond, VA|129

Conditions
MinDate = 1861/05/13
MaxDate = 1866/01/14

EvalMorale = <=;120
EvalEvent = evt_nam_CSA_NM_VP_Tracker;=;10


Actions

ChangeFacMorale = 2

EndEvent



SelectFaction = $CSA
SelectRegion = $Richmond, VA
StartEvent = evt_nam_CSA_NM_VP_results2|999|1|evt_txt_CSA_draft|Event-img_CSA_ConscriptionAct1864|$Richmond, VA|129

Conditions
MinDate = 1861/05/13
MaxDate = 1866/01/14

EvalMorale = <=;120
EvalEvent = evt_nam_CSA_NM_VP_Tracker;=;9


Actions

ChangeFacMorale = 1

EndEvent


SelectFaction = $CSA
SelectRegion = $Richmond, VA
StartEvent = evt_nam_CSA_NM_VP_results3|999|1|evt_txt_CSA_draft|Event-img_CSA_ConscriptionAct1864|$Richmond, VA|129

Conditions
MinDate = 1861/05/13
MaxDate = 1866/01/14

EvalMorale = <=;120
EvalEvent = evt_nam_CSA_NM_VP_Tracker;<=;8
EvalEvent = evt_nam_CSA_NM_VP_Tracker;>=;7
Probability = 75

Actions

ChangeFacMorale = 1

EndEvent


SelectFaction = $CSA
SelectRegion = $Richmond, VA
StartEvent = evt_nam_CSA_NM_VP_results4|999|1|evt_txt_CSA_draft|Event-img_CSA_ConscriptionAct1864|$Richmond, VA|129

Conditions
MinDate = 1861/05/13
MaxDate = 1866/01/14

EvalMorale = <=;120
EvalEvent = evt_nam_CSA_NM_VP_Tracker;<=;6
EvalEvent = evt_nam_CSA_NM_VP_Tracker;>=;4
Probability = 50

Actions

ChangeFacMorale = 1

EndEvent

SelectFaction = $CSA
SelectRegion = $Richmond, VA
StartEvent = evt_nam_CSA_NM_VP_results5|999|1|evt_txt_CSA_draft|Event-img_CSA_ConscriptionAct1864|$Richmond, VA|129

Conditions
MinDate = 1861/05/13
MaxDate = 1866/01/14

EvalMorale = <=;120
EvalEvent = evt_nam_USA_NM_VP_Tracker;>=;1
EvalEvent = evt_nam_CSA_NM_VP_Tracker;<=;3
Probability = 25

Actions

ChangeFacMorale = 1

EndEvent

SelectFaction = $CSA
SelectRegion = $Richmond, VA
StartEvent = evt_nam_CSA_NM_VP_Tracker_reset|999|0|evt_txt_CSA_draft|Event-img_CSA_ConscriptionAct1864|$Richmond, VA|129

Conditions
MinDate = 1861/05/13
MaxDate = 1866/01/14




Actions

SetEvtOccurs = evt_nam_CSA_NM_VP_Tracker;MaxOccurs;0;


SetEvtOccurs = evt_nam_CSA_NM_VP_Tracker;CuOccurs;0;

EndEvent





berto -> RE: New system (9/16/2012 12:25:35 AM)


Thanks for this. More, more, I want to see and learn more!




berto -> RE: New system (9/16/2012 1:23:11 PM)


In the (second) 20120916 alpha release, the scen list has two SVF choices:

  • 4. Struggle for a Vast Future (Ap. 1861)
  • ...
  • 8. Struggle for a Vast Future (Ap. 1861)

    The scen description text are also the exact same.

    That's better than before, but still confusing.

    If one selects #4, the "Enter the name of your game" box suggests "1861 April w-KY Campaign".

    While the #8 selection has "1861 Struggle for a Vast Future". That's The One!

    So, better, but still not quite right.




  • Chliperic -> Union AI is done (9/17/2012 10:24:22 PM)

    I've indeed written the first complete set of events for Union AI....Testing will take one or two weeks, but if this first version is as satisfying than the CSA one, I will integrate it in open beta version sooner.
    I may at last resume my play in FY and test myself SVF 2.0. Not only a pleasure but a necessity: never trust someone modding games or developping them without really playing them. Never.

    Another interesting news of the day is this Turkish AAR by Baris against the CSA AI:

    http://www.paradoxfan.com/forum/index.php?topic=29633.0;prev_next=prev#new

    Google translate helps a bit of course :-)
    I'm always thrilled to see how my mod is played. After all, the AI is applying my plans :-).

    The schedule on SVF 2.0 is met. I think the next months will be devolved more on tweaking and play than large script writing effort, but there's yet for SVF the 1863-1865 period to cover. Time needed is small however.

    Expect a public beta SVF for SVF 2.0 in the very next days.


    First screens of Union AI:

    July 61

    I haven't moved at all as CSA but it wouldn't have changed much.

    AI settings: normal difficulty, more time, activation level +1 ( default), AI fow +1 ( and not +2, a test to see if AI bonus may be reduced). In short, AI has very few bonuses.

    Missouri: Rolla and Lexington under Union control

    [image]http://struggleformodding.files.wordpress.com/2012/09/missouri-latejul-61.jpg[/image]

    Kentucky: Union AI has invaded KY in June 61 ( very rare occurrence) and is step by step taking control with the first available brigades. In short, the AI is able to cope with the poor strategical decision to invade KY

    [image]http://struggleformodding.files.wordpress.com/2012/09/ky-invaded.jpg[/image]

    Virginia: you will note Union AI has captured Grafton with a rather small force coming from Ohio. Mc Dowell is trying to turn Beauregard, forcing him to choose between attacking him or retreat to Fredericksburg. Union AI is yet garrisoning Harper's Ferry, Alexandria and Washington, cancelling real hope for CSA to storm the Capital.

    [image]http://struggleformodding.files.wordpress.com/2012/09/virginia.jpg[/image]







    Chliperic -> SVF 2.0 public beat has started (9/18/2012 9:13:00 PM)

    The SVF 2.0 public beta is available from my blog ( see my sig)

    Heavily under works yet, no manual. Union AI isn't tested and could be performing poorly.

    Installation:


    First, you should create a copy of your AACW directory, so a copy will be left untouched by the mod, and the second modded.There are no side effects as having several copies of any AGEOD game based on the AGE engine ( BOA, WIA, NCP, AACW, ROP And RUS of course)

    The modded copy should have as path C:\ Struggle for a Vast Future. This path will be the one used for installation. If you choose to apply the mod to the normal directory, or to give another name to the second RUS folder, you will have to enter the new path manually when prompted.

    Then

    1) Unrar contents of the archive in the C:\ Struggle for a Vast Future\

    2) Launch SVF2.0.exe

    3) Follow the instructions ;-). When prompted click yes to all.

    If the mod isn't properly installed? That's certainly because the path of your SVF2.0 folder isn't the default one, C:\ Struggle for a Vast Future. The path could be C:\Program Files (x86)\Struggle for a Vast Future or C:\Program Files\Struggle for a Vast Future.

    It could be C\:Struggle for a Vast Future or D:\Struggle for a Vast Future. In such a case, just enter the right path when prompted.

    Important: there's a movie showing step by step install of the mod here:

    http://www.youtube.com/watch?v=BtU0m_oZXcw&feature=player_embedded

    The movie is about Fatal Years install, but the process is the same.

    For support, you may send a email at:

    fatalyearssup@yahoo.fr

    IMPORTANT:

    The scenario is named 1861 Struggle for a Vast Future ( Ap. 1861)

    This version is only playable against CSA AI.The Union AI exits but hasn't been really tested and could be really subpar...

    AI settings are :

    AI ranking: Sergeant ( normal one)

    Use all behaviors

    Activation bonus easy or normal ( + 0 or +1; +1 under test by me)

    AI detect: +2 bonus prefered, but +1 should be fine too. 0 isn't advised

    aggressiveness: normal

    Give AI more time: checked ( this one is mandatory)

    -----------------------------------------

    As a side note, FY downloads have yet reached a new peak. Considering it is a mod on an obscure game, and as such discarded by 90% of the players, and it has been marked by periods with daily updates, it says a lot. :-)

    -------------------------------




    berto -> RE: SVF 2.0 public beat has started (9/18/2012 9:21:28 PM)


    Compatible with save games from (private) beta release ~20120912?

    (I have a game underway playing as Union.)




    Chliperic -> RE: SVF 2.0 public beat has started (9/18/2012 9:23:08 PM)

    yes.




    berto -> SVF 2.0 public beta 20120918 -- localization bug (9/19/2012 7:47:35 PM)


    [image]http://pikt.org/ageod/acw/LocalizationBug_evt_nam_USA_Palyer_units1_20120919.jpg[/image]



    telemann:/home/berto/games/ageod/agelint # ./dochk acw 1.16bRC1.SVF2.0_20120918
    doing chklint...
    doing chkaliases...
    doing chklocals...
    doing chkimages...
    doing chkfiles...
    doing chkselfac...
    doing chkselreg...

    report files generated:

    chkaliases_acw_1.16bRC1.SVF2.0_20120918_20120919_lst.txt
    chkaliases_acw_1.16bRC1.SVF2.0_20120918_20120919_pat.txt
    chkaliases_acw_1.16bRC1.SVF2.0_20120918_20120919_rpt.txt
    chkaliases_acw_1.16bRC1.SVF2.0_20120918_20120919_sorted_rpt.txt
    chkfiles_acw_1.16bRC1.SVF2.0_20120918_20120919_lst.txt
    chkfiles_acw_1.16bRC1.SVF2.0_20120918_20120919_rpt.txt
    chkfiles_acw_1.16bRC1.SVF2.0_20120918_20120919_sorted_rpt.txt
    chkimages_acw_1.16bRC1.SVF2.0_20120918_20120919_lst.txt
    chkimages_acw_1.16bRC1.SVF2.0_20120918_20120919_rpt.txt
    chkimages_acw_1.16bRC1.SVF2.0_20120918_20120919_sorted_rpt.txt
    chklint_acw_1.16bRC1.SVF2.0_20120918_20120919_error_rpt.txt
    chklint_acw_1.16bRC1.SVF2.0_20120918_20120919_warning_rpt.txt
    chklocals_acw_1.16bRC1.SVF2.0_20120918_20120919_lst.txt
    chklocals_acw_1.16bRC1.SVF2.0_20120918_20120919_rpt.txt
    chklocals_acw_1.16bRC1.SVF2.0_20120918_20120919_sorted_rpt.txt
    chkselfac_acw_1.16bRC1.SVF2.0_20120918_20120919_lst.txt
    chkselfac_acw_1.16bRC1.SVF2.0_20120918_20120919_rpt.txt
    chkselfac_acw_1.16bRC1.SVF2.0_20120918_20120919_sorted_rpt.txt
    chkselreg_acw_1.16bRC1.SVF2.0_20120918_20120919_lst.txt
    chkselreg_acw_1.16bRC1.SVF2.0_20120918_20120919_rpt.txt
    chkselreg_acw_1.16bRC1.SVF2.0_20120918_20120919_sorted_rpt.txt

    telemann:/home/berto/games/ageod/agelint # egrep -i palyer chklocals*.txt
    chklocals_acw_1.16bRC1.SVF2.0_20120918_20120919_lst.txt: 1 evt_nam_USA_Palyer_units1
    chklocals_acw_1.16bRC1.SVF2.0_20120918_20120919_rpt.txt:/media/KINGSTON/Games/AGEOD/AGEod's American Civil War SVF/ACW/Events/USA Events.sct:584: evt_nam_USA_Palyer_units1 not found
    chklocals_acw_1.16bRC1.SVF2.0_20120918_20120919_sorted_rpt.txt:/media/KINGSTON/Games/AGEOD/AGEod's American Civil War SVF/ACW/Events/USA Events.sct:584: evt_nam_USA_Palyer_units1 not found

    telemann:/media/KINGSTON/Games/AGEOD/AGEod's American Civil War SVF/ACW/Settings # egrep -i evt_nam_USA_Palyer_units1 *.csv
    [nil]



    [;)]




    berto -> RE: SVF 2.0 public beta 20120918 -- localization bug (9/19/2012 7:48:39 PM)


    One reason why I need a chance to review and edit the SVF text string *.csv files.

    [;)]




    Chliperic -> RE: SVF 2.0 public beta 20120918 -- localization bug (9/19/2012 8:05:13 PM)

    Fixed. In fact , this event shouldn't generate messages...




    berto -> RE: SVF 2.0 public beta 20120918 -- localization bug (9/19/2012 8:17:36 PM)


    Is there a consistent, organized way to designate such no-message events?

    By naming them, for example:

    evt_nam_USA_Palyer_units1_NOMSG

    Or maybe:

    evt_nam_USA_Palyer_units1_NOLOCALIZATION

    That way it's easier to edit them out of the bug reports.

    Or some other way to mark such events?




    Chliperic -> RE: SVF 2.0 public beta 20120918 -- localization bug (9/19/2012 8:37:06 PM)

    It could be indeed. As I know, event names may be very long. Now, I will not for my own do this as all AI events are mute, occurence of such display message for 0 message events glitches are very rare. It could be done your way however.




    berto -> SVF 2.0 public beta 20120918 -- AI oddity? (9/19/2012 8:57:11 PM)


    [image]http://pikt.org/ageod/acw/SVF20Beta20120918LoneConfArtyTriggKY.jpg[/image]

    A lone, unaccompanied Confederate Arty unit in Trigg KY advancing by itself aggressively forward of the Southern front line -- the AI shouldn't be doing that. Panzer battalion? (Reminds me of the AI in the JTS/HPS American Civil War series of games.)

    Or is it perhaps escaping southward from Henderson KY (across the Ohio River from Bull Nelson's command)? In which case it makes more sense. (But I don't recall seeing that Arty unit in Henderson KY the turn before. Could be wrong.)

    Save, Script, Log files here.

    (In that .zip file -- too much detail? or just right?)

    Going forward, every time I see some suspect AI behavior (or genius move!), I will try to send you a report such as this.




    Chliperic -> RE: SVF 2.0 public beta 20120918 -- AI oddity? (9/19/2012 9:38:31 PM)

    Send me the files, but I've not found a way to eliminate this. IN FY, the hard AI is using the same way the aerial units, in AACW the artillery forward unit is there since the release of the game. Generally the unit is moving toward a stack, without taking into account sufficiently enemy is near...




    berto -> RE: SVF 2.0 public beta 20120918 -- AI oddity? (9/19/2012 10:14:26 PM)


    If that is hard-coded AI behavior (over which you have no control), that sucks. [:(]

    What I would do, then, is to adopt a house rule that: in the case of such obviously stupid AI behavior, turn a blind eye to it, pretend Fog of War. ("Did I really see that? Naw! FOW. I just imagined it.") Or just dismiss it as an obviously false intelligence report. (Excuses, excuses...) And refrain from taking advantage of it.

    ("Send me the files"? I provided a link.)




    Chliperic -> RE: SVF 2.0 public beta 20120918 -- AI oddity? (9/19/2012 10:19:28 PM)

    Didn't see the link.

    Such case are rare. Perfection isn't reachable but on the whole, such cases aren't penalizing much the AI.




    Chliperic -> RE: SVF 2.0 public beta 20120918 -- AI oddity? (9/19/2012 10:43:29 PM)

    Looked at your save. On the whole, the CSA AI isn't stupid.

    Now, for this strange artillery move: the artillery was issued from a larger group having cavalry. he stak name is yet Cavalry something even if only composed of the Artillery unit. It receives an attack order. My explanation, maybe wrong,would be that Stacks are conserving some precedent orders, at at least type of orders varying with their types. Here, the orders would remain those of a stack having cavalry even if after splitting only remains a support unit... Nothing I can do. The good news is the Artillery should retreat the next turn or merge with another stack.




    berto -> RE: SVF 2.0 public beta 20120918 -- AI oddity? (9/19/2012 10:51:00 PM)


    quote:

    ORIGINAL: Chliperic

    The good news is the Artillery should retreat the next turn or merge with another stack.

    Yes, the next turn, it appears to have done exactly that (retreat).




    Chliperic -> RE: SVF 2.0 public beta 20120918 -- AI oddity? (9/19/2012 10:57:53 PM)

    I suspect indeed the computation of the region value with the enemy threath on it, coupled with the low power of the artillery unit has made retreat the most valued solution. It happens almost always. It would indeed be better if such a computation would occur to cancel the attack move, but frankly it must be a nightmare to adjust several algorythms in the hard AI. In my modest way, it's the same with events: the pore they are, the more diffcult to adjust the AI without having unexpected side effects. Fortunately, SVF uses simpler method than FY and the first results are sufficient to keep tweaking to low level until now.

    Apart that, it would maybe be time to retake Alexandria and Harper's Ferry, no ? :-)




    berto -> RE: SVF 2.0 public beta 20120918 -- AI oddity? (9/19/2012 11:53:37 PM)


    quote:

    ORIGINAL: Chliperic

    Apart that, it would maybe be time to retake Alexandria and Harper's Ferry, no ? :-)

    I'm trying!




    Chliperic -> RE: SVF 2.0 public beta 20120918 -- AI oddity? (9/20/2012 7:13:58 AM)

    After more in depth look at your save, I really feel the CSA AI to be really enjoyable as oppponent at least until 1863. Your game confirms the point drawn from other games. Let's work a bit more on the union AI!




    berto -> RE: SVF 2.0 public beta 20120918 -- AI oddity? (9/20/2012 11:23:38 AM)


    I'll start a new game as the Confederates later today, then.




    Page: <<   < prev  1 [2] 3 4 5   next >   >>

    Valid CSS!




    Forum Software © ASPPlayground.NET Advanced Edition 2.4.5 ANSI
    8.789063E-02