The Updated Enhanced AI Mod Thread

By on June 14, 2011 11:41:43 PM from Demigod Forums Demigod Forums

pacov

Join Date 02/2008
+183

Updates:

Public version 1.03 live 1/18/2012 at 6:07 PM EST


 


Download links:

Link to the latest version PUBLIC version of the mod:  http://www.box.net/shared/g8lbbhpojik4tbkjn6su


I created a post that tracks the history of the AI in Demigod and it covers a good chunk of the development that has already been handled by the modding community.  If you are interested, see over here for more details:  http://forums.demigodthegame.com/409712

The Project

Using the last version of peppe’s AI mod (0.26.35), I’ve started development on updated versions of the AI mod.  I’ll be releasing those versions here, tracking bugs, enhancement requests, rebalancing, etc.  I won’t be adding a new version to my combined DG installer until we make a decent amount of progress or come up with some sort of significant enhancement to justify a new release to the community at large.  It took us a long time to get reasonable adoption rate on the existing ai mod – I’d rather not force folks to redownload the bundle over and over.

The Project Team

  • Project lead:  pacov
  • Lead design/coder:  pacov
  • Lead support:  miriyaka – without miri, the majority of the changes we are looking at would not happen
  • Testers:  sledge, plaguewraith, and darkliath 
  • Contributors:  Lord_Orion

If you’d like to help in any way, we are happy to have you on the team.


Current status (what’s being worked on)

  • Build updates (removing inefficient builds and replacing them with new ones) - complete
  • Reprioritization of citadel upgrades, items, trips to the shop - largely complete - some late game tweaking still possible, but its improved quite a bit
  • Implementing a fix for AI’s with summonable minions so that they do not waste mana summoning more after the have created the max number of minions (miri created some code and I’m looking to make it work)  Resolved in 0.26.41
  • Recoding the ShouldSave functionality to improve the coding efficiency and gives us additional flexibility.  If we get this working, it will be a very solid improvement and provide more options.  - this has been implemented

Bug list (unless otherwise noted, these are all bugs from the original 0.26.35 version)

  • Stuck AI – the AI can get stuck on occasion for > 30 seconds
  • Poor scaling based on AI difficulty - this has been improved but there is still room for improvement
  • Not enough shopping trips for the AI unless it is killed or sent back the base with low HP (eg an AI could have 10k gold and still not attempt to shop and get better items) - 1 forced shopping trip at wr 4 has been added... might be good to do more, but much better now.
  • AI is not always getting fs1 in a timely manner (resolved in 0.26.39)
  • Some abilities are not being used as often as they should (a sedna, for instance, with pounce as her only ability would use it once in a blue moon) - continuing to make improvements (pent/pounce/grasp/deep freeze have all been fixed)
  • Some abilities are being used at inappropriate items and wasting mana as a result
  • Customized settings often throw the AI off.  For instance, if you set a game to being at WR10, the AI don’t shop (not sure if we want to try to code this to cover all possible settings) - improved some.
  • AI standing around at the shop at the beginning of the game (introduced in 0.26.38 – happens randomly and seems to only impact 1 ai on a team) - resolved in 0.26.40
  • Not truly a bug, but something I want to change - need to make it so the high gold dg can still buy things for themselves (resolved in 0.26.49 "siesta")
  • AI considers minions as part of a DG's army... this is good and bad - its good to target healers from time to time, but if I can make an enemy target a shambler while I'm wailing on him...

Enhancement requests (these are changes that folks would like to see happen with the AI)

  • Better healer distribution.  The over all goal would be to ensure that monks/clerics/etc are sent to appropriate players.  The basic code works fine, so this is a lower priority change imo.
  • Improve da’s shadow swap usage – plaguewraith suggests removing it completely from his build (might be a good temporary solution until we can tackle this) (removed 0.26.55)
  • Better creep farming with skills.  Plaguewraith indicated that he never saw a tb use circle of fire to farm.  This is something we could tweak, but we’d need to think it through
  • Lord-Orion suggests we remove all ub builds except for Spit/Ooze life - REMOVED 1 OF THE BUILDS 0.26.40 - still 2 left
  • Lord-Orion suggests we optimize all builds for skill dmg output as the AI cannot currently rationalize like a human can. 
  • Lord-Orion suggests we go with a basic item prioritization of 4 life/1 helm builds – I agree to some extent… (pretty much done as of 0.26.52)
  • Come up with a way for the ai’s to intelligently chain stuns or interrupts to go for kills.  In theory, the AI could be even better than a human at this if it was tied to precise timing
  • Teach the AI to teleport for ganks (this could be tricky – would probably result in a lot of pointless tp’s)
  • Find a way to help the AI manage mana better.  Early game the ai’s are almost always out of mana
  • Teach the AI when to shop!  (big improvement with 0.26.49 "siesta")
  • Have the AI always engage a simple enemy opponent if on a flag if hp is good, etc
  • Have the AI choose to engage towers on a regular basis (improved a lot since 0.26.54)
  • Have the AI refuse to run past towers in most circumstances and instead TARGET THE TOWER if no dgs around
  • Improve cataract map logic – the ai often goes into the middle of the map instead of staying in a lane.  This is probably due to the proximity of the creeps when the ai is working on capturing the middle flag (or if all flags are controlled by their team).  Ideal behavior would be to try to capture the middle flag and if its already controlled, then get into a lane on HP or Mana.
  • Override the flee functionality if there is an enemy dg and its likely possible to get a kill
  • Better decision making for flags – Ai heading over from mana side all the way to Hp without capturing mana.  this is likely due to flag weights… just not sure why it didn’t evaluate hp as the priority initially – could be some conflicting code?
  • Send the AI back to base if its low mana (sledge) – We might do something for this, but it would have to be a conditional statement – perhaps add a check to see if they are at low mana around X Ws have > X money, then run back and prioritze getting a helm as an override
  • Plaguewraith suggests removing mist from erb’s build – I’m not sure about this yet.  He says remove it or build a routine to cause erb to use it just to get rid of negative buffs – I agree that we could use a routine like that.  - mist removed in 0.26.40
  • Encourage the AI to react quickly if they are losing a flag that is near 2 or more towers (eg gold flag)
  • Increase the frequency that the AI picks up sigils – not sure about this one – I agree a good player should generally have one, but the AI might just blow a lot of money casting when it doesn’t need to and fall behind as a result.  Perhaps this becomes a conditional statement to raise the priority after ws X (0.26.47 - implemented)
  • Add an override so the ai will only go for flags like gold if the tower is down.  Add another override so the ai doesn’t go for portals early (probably WS related)
  • plaguewraith – delete the tb builds and just stick with 1 fire tb build - REMOVED 1 BUILD - only pure fire and pure ice remain 0.26.40

Change log

version 1.03
-Created new UID
-Adjusted hero/squad targeting values to increase AI skill use aggression
-Adjusted range cutoff multiliers to mitigate the chance of the AI from running past towers to cap flags
-Adjusted/fixed errors in Oak, Queen of Thorns, Unclean Beast, Regulus and Demon Assassin AI builds
-Re-enabled Sedna Pounce build and Queen of Thorns Shield_Spike build
-Homogenized AI build names so it is obvious what skills the AI is using.

version 0.28.00 BETA
- removed unclean beasts AA build as the Spit ooze build is generally a little better

version 1.02
- created new UID and incorporated all changes since version 1.01

version 0.27.09 BETA
- Disabled a substantial amount of logging (will result in a substantial performance boost for many)
- added miri's scenario name capture function to CommonUtils.lua (doesn't work now, but isn't being called)
- began to tweak ub's usage of ooze.  Reduced health activation from >= 40% hp to >= 30%.  Also reduced the deactivation health value from < 40% to < 30%
- reenabled the attack override in herogoap
- updated the flee mastergoal to set at 50% HP instead of the current 75% hp
- Added an action time to health pot usage to hopefully keep the AI from using a pot at lower HP, having the pot bring them up to full strength and then having the ai immediately sigil

version 0.27.08 BETA
- Added new action and instant status function in useitemactions to keep the AI from "double locking" flags (eg wasting locks on a flag that is locked)

version 0.27.07 BETA
- increased sigil activation health % from 45% to 50%
- added new hammerslam calculate rates function - should increase the odds that rook will slam if the unit is stunned (should work for any type of stun)
- rebalanced weights of rook's actions to bring them more into logical numbers
- rebalanced weights of erb's  actions to bring them more into logical numbers

version 0.27.06 BETA
- reduced sigil activation health % from 50% to 45%
- changed orb of defiance usage check so that it will consider using it before sigils
- removed grunt check on orb of defiance (previous the AI would refuse to use use the orb if the threat level was < 15)
- added nearby enemy hero check to orb of defiances - if no enemies nearby, then orb will not be used
- reduced the value of narmoth's ring on the AA ub build so that it is not choosen as the only item at the start of a game on nightmare difficulty
- reduced the captureflag override at the start of the game from 60 seconds to 40 seconds
- disabled the attack override to allow the ai to make its own decisions based on weight
- Reduced the reteat values if there are nearby enemy heroes and towers from 85% to 75%
- modified rules for dg vs dg fights.  AI will run if there are more enemies than allies present

 version 0.27.05 BETA
- removed the nonworking per map flag settings
- revised the generic flag settings
- disabled all existing rook builds
- added new "more balanced" hammer slam tower build

version 0.27.04 BETA
- continued to enhance the documentation in heroGOAP
- added new logic to provide a count of heroes/enemies in heroGOAP for decision making
- added rule so that the AI's goal will flee if 3 or more enemies are present vs 1 ai
- changed default value of gold and portal flags to 0.5
- increased unit.movecutoffrange from 1.2 to 2.5 in attackactions
- fixed a problem with da's new swap logic
- continuing to test out flagassets.lua - I don't think values are being loaded for each map

version 0.27.03 BETA
- removed erb's desire to cast stun as an interrupt as its not possible
- increased erb's desire to bite
- increased oak's desire to use surge to kill units
- removed sedna's desire to use silence as an interrupt as its not possible
- added comments to heroGOAP to try to track where the AI is getting stuck (NOTE - this could slow down some lower end pcs)
- added new logic to count the number of grunts near a hero for decision making purposes - previous check was based on threatlevel
- changed the balancing capture flag logic so that the AI will re-prioritize capturing flags if there is a difference of 50 in warscore
- changed AI's desire to buy capture locks from WR 4 to WR 6 - AI will not purchase them prior to WR 6

version 0.27.02 BETA
- major revamp to DA's swap ability - da will now only swap if the number of allies is > enemies near da
- disabled existing DA build
- enabled STANDARD_ASSASSIN da build (eg what most players use when playing da) now that swap is working as desired
- disabled pounce sedna build

 version 0.27.01 BETA
- updated TB's frost nova so that it is used more often

version 0.27.00 BETA
- created new UID - this is done so folks can still keep the release version 1.0 installed and try out new "beta" versions and help with testing, etc
- added additional documentation to AIGlobals.lua
- adjusted the saving routine so that angels are not saved for until ws 7
- changed the way the AI evaluates additional shopping trips.  Now based on warscore
- fixed a minor bug with reg's mark of the betrayer squad target
- added additional shopping trips (see details below)
    # SHOP PERIODS
    # Warscore >= 300, AI with most money, possible to buy fs1, at least 600 gold
    # Warrank >= 3, AI with most money, possible to buy cur1, at least 1800 gold
    # Warscore between 2450-2575, NOT AI with most money, at least 1500 gold
    # Warscore between 3100-3225, AI with most money, at least 1500 gold
    # Warscore between 3800-3925, AI with most money, at least 1500 gold
    # Warscore between 4150-4275, NOT AI with most money, at least 1500 gold
    # Warrank 8 OR AI already bought the upgrade, priest/angel/cats available, AI can afford the upgrade
    # Warrank 10, possible to buy giants, AI can afford the upgrade

version 1.00
- created new UID
- removed any "pacov" labeling
- changed name to Enhanced AI (peppe's original version was Enhanced_AI
- updated version name to 1.00 (numbering convention will be 1.00/1.01/etc going forward)

 version 0.26.56 (misc fixes + pounce sedna build is live)
- removed CaptureFlag goal weight from oak's pent functions
- removed CaptureFlag goal weight from rook's hammerslam functions
- removed Captureflag goal weight from tb's deep freeze functions
- removed CaptureFlag goal weight from ub's grasp functions
- removed ub's mygraspstatusfunction and replaced with DefaultStatusFunction
- removed oak's myPenitenceStatusFunction and replaced with DefaultStatusFunction
- removed sedna's myPounceStatusFunction and replaced with DefaultStatusFunction
- substantially increased sedna's desire to pounce
- re-enabled sedna's pounce_tank build

version 0.26.55
- fixed a bug that still allowed demon assassin to pick up swap
- fixed a bug with unclean beast's grasp code
- enabled new hammerslam/tower rook code and tweaked desire to hammerslam
- increased sedna's desire to pounce (did not re-enable the pounce build yet)

version 0.26.54
- removed the remaining demon assassin build and added a new build without swap per request
- reworked the valor flags weight.  Should be less desirable for AI prior to ws 8
- tweaked deep freeze to be cast much more often
- re-enabled ai priority to attack structures.  Tweaked the formula so the AI will immediately back off if any enemy dgs come into range.  This should reduce the odds of death and also keep the AI from wandering past towers for the gold flag, etc

version 0.26.53
- increased artifact weight so they will be kept if the AI purchases
- added mageslayer to the generic equipment purchase list with a priority of 110, moved godplate to 120
- enabled oak to cast surge when trying to flee

version 0.26.52
- substantially increased the odds that oak will attempt to interrupt
- removed demon assassin speed_spine build
- re-enabled the graveyard level 1 upgrade
- minor misc changes
- changed ai's desire to pick up locks from level 3 to level 4

version 0.26.51
- rebalanced the general equipment builds
- rebalanced the specific demigod equipment builds
- removed AI's desire to purchase any graveyard upgrades
- removed "cloak of invisibility" from artifact prioritization as the item does not exist

version 0.26.50
- Reduced priority from 35 to 20 for boots of speed on UB HP/ooze build to keep the AI from purchasing boots of speed as the first item if the AI is set to normal
- increased priority of grofflings plate in the general build
- substantially increased ub's desire to grasp in game
- updated flag goal for cataract to reduce the AI's desire to grab the valor flag early (eg the AI running to the middle of the map)
- increased ice tb's goal to make it use deep freeze more often (tb's abilities all need a bit of an overhaul)
- various item selection tweaks

version 0.26.49
- changed desire for flag locks to increase at wr3 instead of wr4
- adjusted AA ub build so that it will never choose mana items (unbreakable is still acceptable, though)
- implemented the "siesta."  At warrank 4, any ai (not the high gold AI), will return to base to shop as long as they have 1500 gold.  Then, towards the end of wr4, the AI that is the highgold AI will shop alone. 

version 0.26.48
- added miri's check to force the tb to stay in whatever mode its build is designed for.  This should improve the AI's usage of abilities tied to the pure ice or fire builds.  Confirmed that fire tb will stay in fire form and ice in ice form based on build.
- continued to balance item selections
- Changed Rook's favor item to blood of the fallen
- TEMPORARILY turned off the attack structure code

version 0.26.47
- made MANY balance changes - all changes are noted in the files, but too many to detail here (so I'll cover highlights)
- changed ideologies for the mod.  Before the goal was to force the AI to do everything I wanted it to do (simply buy cit upgrades) - now I'm planning on having it scale that back and focus on becoming an arse kicker
- odds your ai will have a sigil is MUCH higher - this improves survival odds ALOT
- ai will always purchase fs1/cur1/priest/angel/cats/giants - that's it.  AI will no longer get any levels of experience.
- ai will VERY OFTEN have locks - I still need to teach the AI how to use locks better though... so at least for now, it will have them...
- MANY item prioritization changes - If you understand the modding side of things a wee bit, there are 2 ways a dg chooses equipment/items:  1 - a general list that contains all recommendations.  2 - a list that is specific to demigod build.  I spent quite a bit of time improving the general list today and started working on the 2nd method that includes build specific items.  I've only started on QoT, but I will likely get her to mimic my standard QoT build for items.
- removed some additional checks to help reduce overhead of the AI

* note - I have not begun to force shopping trips on the AI outside of fs1/cur1/priest/angel/cats/giants.  I'll be looking to start phasing in shopping trips to encourage the ai to get even better items as appropriate.  AI will still shop if it gets its arse kicked, but I want to schedule some trips so the AI will get stronger at different intervals even if its doing fine.

version 0.26.46 (the getting back on track version)
- added miriyaka's changes to the save function so that we can evaluate based on warscore as well
- added saving for fs1 as a priority after ws 200
- updated value for fs1 to increase its priority to 200 after ws 300
- removed log writes from miri's savefor, etc to see if that helps the lag issue that's been mentioned
- confirmed - the generals will now choose monks if they are a normal ai with default settings (instead of saving for fs1)

version 0.26.45 (the lesser of two evils/back to basics version)
- the title gives you an idea - if you play on normal settings with 1 general ai, they will NOT purchase monks at the start.  This is not desired behavior.  But in allowing this, the AI does not freeze between ws2 and 3 for any extended duration.  Sadly, the other option right now is you get monks, but the ai stands around like an idiot at ws2.  
- Added additional documentation for the herogoap file
- disabled the trip to the shop for ws 5 to get cur2
- developed basic test code to send the ai to the base if its not the high gold ai
- backed out the changes that increased rate of fire for bite/pounce/pent.  We'll visit this again, but I'm concerned that the ai is overriding their flee function due to the high priority I put on these abilities resulting in more pointless deaths.  My goal is to simply make them use their abilities more often... not die like goofs.
- tweaked the rules for purchasing sigils.  AI will not buy them until ws 2 and only if the AI has a max health > 2750
- removed assassin sedna build again until I get back to sorting pounce

 version 0.26.44
- hopefully corrected a bug that would cause the ai wait around to purchase an upgrade if it did not have enough money of the ws for it.  This should give us new opportunies for balancing upgraded in the future.  The short version is I updated HeroGoap perform a check if the ai can afford the upgrade they are saving for before heading off to the shop.  Not enough money = no shop.  I'll be looking into explicitly sending specific ai's to shop on some sort of interval in the future
- (not a real change... but started deep dive into integrating miri's savefor function)
- removed cur2 shopping trip for now - it still gets a high priority, though

version 0.26.43
- added miriyaka's save for gold functionality
- disabled ai goal chat function from herogoap 1198

version 0.26.42
- substantially increased the rate that erebus uses bite
- substantially increased the rate that sedna uses pounce
- re-enabled assassin sedna build now that pounce is used more often
- substantially increased the rate of oak's penitence
- added another shop period at ws 4 - the ai with the most goal should head for base a 4.  This might result in a different dg being choosen for highgold after

version 0.26.41
- added miriyaka's summon shambler fix.  The code would work for QoT, Sedna, and Oculus.  I'm only implementing it for QoT as this would be a disadvantage for the Oculus build and sedna does not use yetis in the AI mod
- Removed anklet of speed from all TB builds and replaced with Blood of the Fallen.  The ai is not smart enough to use a speed fire tb build
- Removed the file mod_units. This contains fixes already in uberfix and is not needed here
- Enabled master goal chat - this is a debug function that broadcasts what the AI's goals are - you might find this annoying...
- Re-enabled code that adds a destroy structure goal for the AI.  Peppe turned this off at some point... probably for a good reason, but I did see the AI being more aggressive attacking towers, so I'm leaving this on for now.
- Made some adjustments to the flag weights on cataract.  This SHOULD end dgs running over the the mana flag at the start and then rushing to HP before they capture the mana flag.  Reduced the weight of the gold flag to encourage the ai to attack structures first.  Reduced the value of portals prior to ws8.
- Removed all oak builds and added a new shield/pent focused build
- Minor change for reg's build - added impedance bolt at level 16 instead of stats 1

version 0.26.40
- removed the code that placed a limitation on what items could be purchased at the start of the game (AIShopUtilities 736-741)
- Changed the priority level trigger from WarScore to WarRank for fs1 (AIGlobals 1433) - this appears to have resolved the ai's standing at mid issue.  The Ai will purchase fs1 at ws2 now correctly
- Changed AI's priority to get xp2-xp4 to 0.  AI will no longer purchase these upgrades
- removed mist and added coven 1 as erb's level 2 skill until we get a chance to write a routine for him to use mist to remove negative buffs
- Updated ai priority values for minotaurs to 0/5/10/15 (eg an ai will never buy the 1st level minotaurs now) - I was seeing the ai pick this up as a cheap filler if they have the money - not worth it
- Updated ai priority values for level 1 archers - dropped from 15 to 0 so the ai will never buy
- updated ai priority values for hauberk of life - dropped from 40 to 35 so that unbreakable would be chosen over this if money was available
- updated ai priority values for unbreakable - removed conditional formula and set to a static 39
- removed ub skill build spit_ooze_mana (essentially bots ub)
- removed hybrid_fire_ice build from tb (bots tb)

 version 0.26.39
pacov is learning things…
- reprioritized AI to purchase fs1 at ws2.  Previously, it only purchased it if made it back to base with enough money; this forces it back to base to get it if no one else has
- raised priority for currency 2.  Logic mirrors currency 1 as I want this purchased every time.  Also sending ai with the most gold to purchase at ws 5.
- removed assassin sedna build until I have a chance to look at the pounce training – assassin sed should be pouncing left and right… right now its like once in a blue moon – heal_tank sedna is solid though

version 0.26.38
removed unitstatussensors code – concerned it might be causing an issue
- tweaked erebus build so that he gets mass charm later – he’s not using it well as is

version 0.26.37
bugfix – just resolving a sytax issue

version 0.26.36
copy of peppe’s version 0.26.35
- removed 3 old sedna ability builds
- added 2 new sedna ability builds
- removed old qot ability builds
- added new qot ability build
- removed 2 old erebus ability builds
- added 2 new erebus ability builds
- uncommented some code peppe developed in UnitStatusSensors that might help resolve the frozen dgs
*note – all builds that have been added by me will be announced in team chat at the start of the game and will say “pacov” folowed by the build name.

Pinned, Locked Post 458 Replies +1
Search this post
Subscription Options


Reason for Karma (Optional)
Successfully updated karma reason!
July 20, 2011 8:34:35 PM from Demigod Forums Demigod Forums

miri - any thoughts on the flagassets.lua file.  I've a bit convinced that the custom settings per map are not being utilized (and have never been utilized).  I should be able to insert a simple log message to tell me if one of the "if" paths is being taken... but I cannot.  Which makes me think that these settings are not doing a thing.  For instance, this code with the log added, should populate... I'd think.

Code: c++
  1.     #Zikurat
  2.     if 'lastscenario' == '/maps/map07/map07_scenario.lua' then
  3.         local cooldownWeight = 10
  4.         local experienceWeight = 15
  5.         local goldWeight = 10
  6.         local artifactsWeight = 15   
  7.         local portalWeight = 15
  8.                                 LOG('*AI LOG: Zik flag weights loaded')
  9.     end

Even if the map is zik, that log message does not appear... which makes me think something might be wrong with how the if statement is written.

Any thoughts?

 

Reason for Karma (Optional)
Successfully updated karma reason!
July 21, 2011 11:31:18 AM from Demigod Forums Demigod Forums

So if 1 ai hero sees 3 against him he runs away directly?

Not that great in every situation though. A ranged hero has a bigger chance of staying alive or not getting killed or still dealing damage. A higher level hero also is stronger.
And if they run away in 1 direction and another hero comes to 'help' then that hero will be alone and flee.
Maybe if they hang bang/creep and wait for reinforcements.

Perhaps a 50% health requirement can be thrown in there?

[/hasagainnoideawhatispossibleandjustrambleson]

 

/\ rhetorical 

Reason for Karma (Optional)
Successfully updated karma reason!
July 21, 2011 11:38:36 AM from Demigod Forums Demigod Forums

Quoting miriyaka,
By failing I just mean it will skip that action.  If the AI has multiple actions in its current goal plan, it will process the next one.  In the case of DestroyStructure, there probably won't be any other viable actions in its plan, so it will attempt to re-choose a goal and/or re-formulate the action plan.  Nothing bad will happen, unless the AI is being forced into a given goal and therefore limited selection of actions by external forces that don't take into account a similar target range.

Sorry, I meant bad from the perspective that it is not engaging towers when it should. eg: Fail to engage tower when it 1st comes in range, run past to cap flag.

Reason for Karma (Optional)
Successfully updated karma reason!
July 21, 2011 2:35:19 PM from JoeUser Forums JoeUser Forums

Quoting TcoNL,
Perhaps a 50% health requirement can be thrown in there?

here's the thing though - if an ai has 100% hp, without this check, it would run full on into 3 enemy ai's.  That's the behavior I want to avoid.  Sure, I could add at 50% hp = flee if 3 or more enemies are present, but it would still attempt to attack 3v1 if it had 51% hp or >..  What I suggest is doing some play testing then coming back and letting me know if you think there are issues with this.  Any of these changes could have unforeseen consequences so I'm trying to keep them very basic initially. 

I still could very much use some play testing from folks.

Reason for Karma (Optional)
Successfully updated karma reason!
July 21, 2011 2:52:32 PM from Demigod Forums Demigod Forums

The map overrides aren't working because the string 'lastscenario' will never equal any of the mapname strings Peppe specified, because uh, they're not the same string.  I don't really know what he thought that would do, or what 'lastscenario' is supposed to be, as even taken as a variable name rather than a string, it has no meaning in the context of that file or class.

Pull that whole mess out for now, it is doing nothing and can only do nothing.  If I get time, I'll look into actually getting the current mapname from ScenarioInfo, and doing something with that.  I posted some code for LO to use that did that, but I never got a chance to test it myself, and he never got back to me on whether or not it worked, so I'll have to re-research it.

Reason for Karma (Optional)
Successfully updated karma reason!
July 21, 2011 3:55:27 PM from JoeUser Forums JoeUser Forums

re: 'lastscenario'... yeah, that's what I thought.  Did some in depth testing awhile back and the ai was still prioritizing other flags regardless of what I set it to... then a few days ago I got around to trying to insert a log message when the if chain was used didn't get any output.  I even noticed that lastscenario is called LastScenario everywhere else, so I gave that a go with no luck as well.

If I get a chance, I'll dig around the forums to see if I can find that code... I'm guessing it was in the "crazytown" thread?  Anyway, I might just make some cataract specific overrides (pretty much what I've already done) and set them for all maps in the meantime.  Proper code would help alot of if you get a chance... pretty sure that's beyond me to sort.  Also, I'm not sure, but I think the flag weights are only called at the beginning of the game.  I inserted a log message to populate every time the generic weights are applied and it only seemed to run at the start.  Makes me think conditional logic based on warrank might not work in flagassets.lua, but I'll give it a test.... I've got so much crap writing out to the log now as it is...

anyhow, I'll just comment out the map specific code in the meantime for my next release.

if I get a chance, I'll tackle that tonight.  I'm also going to look into killing more of the overrides and seeing if that helps with the stuck ai rot.  I think I'm starting to understand how to change some of the weights to cause what I want to happen without the overrides anyway. 

Reason for Karma (Optional)
Successfully updated karma reason!
July 21, 2011 4:11:19 PM from JoeUser Forums JoeUser Forums

mri - see reply 42... think this is was you were talking about:

http://forums.joeuser.com/408845/page/2

Reason for Karma (Optional)
Successfully updated karma reason!
July 21, 2011 8:46:32 PM from Demigod Forums Demigod Forums

version 0.27.05 BETA
- removed the nonworking per map flag settings
- revised the generic flag settings
- disabled all existing rook builds
- added new "more balanced" hammer slam tower build

live now.

 

also - did some testing about using a war rank check to update values in flagassets.  Doesn't work (which I expected after some tests).  Test was simply to hit ws 2, change value of xp to like 100, and write a log message.  Log message was never written. 

Note - this version brings us down to ONE rook build that should be a bit more efficient with mana usage, but also might be crap.  We'll see.

Reason for Karma (Optional)
Successfully updated karma reason!
July 22, 2011 12:41:09 PM from Demigod Forums Demigod Forums

Quoting OMG_pacov,
also - did some testing about using a war rank check to update values in flagassets. Doesn't work (which I expected after some tests). Test was simply to hit ws 2, change value of xp to like 100, and write a log message. Log message was never written.

While that should technically be possible to get war score in FlagAsset, it's definitely not the best place to do that, because a flag asset's CaptureReward is only calculated once when that flag is created, which means your war score calculation would be way out of date for almost all flags in the game after a few minutes.

FriendlyAsset.SortHeroCapturePoint would probably be the best place to take WR into account, but you would need some way of determining the type of flag whose CaptureReward you're modifying, which would really mean an overhaul of FlagAsset.FindCaptureReward to also record flag stats or determine what 'type' the flag is (in the case of a flag with multiple structure types attached).

 

If I get time, I'll see if I can come up with something here, but it would need to be a pretty complex multi-file solution to do more good than harm, so no promises.

Reason for Karma (Optional)
Successfully updated karma reason!
July 22, 2011 1:21:48 PM from JoeUser Forums JoeUser Forums

could use some tests if there is a still a tester on earth on the viability of the new rook build.  Thanks.

ok - miri.  I had the impression it was just for initial weights and was not called again.  That said, the AI still goes batshite to get portals late game even with a lower priority.  I'll have to dig around to see where that code comes into play, as that could likely be used as well for setting high priorities on specific flags at certain times.  I'll do a search on that one later.

Whatever you feel motivated for is good.  Even though its not as valuable as increasing flag weights at certain warscores, etc, my primary assistance request would be for being able to add back in flag weights for specific maps.  All I gleaned from that post that you made was that orion never got it work and that you might have had a solution to make it work.  Didn't have a chance to dig any further with my exciting hectic work schedule of late.

Reason for Karma (Optional)
Successfully updated karma reason!
July 22, 2011 3:26:06 PM from Demigod Forums Demigod Forums

I'll try it right now and post feedback in a bit

Reason for Karma (Optional)
Successfully updated karma reason!
July 22, 2011 4:01:00 PM from Demigod Forums Demigod Forums

This mod is superb, game changing.

 

Is there any danger Stardock might incorporate and release as a update? Would save so many games for a player drop->insta concede. 

Reason for Karma (Optional)
Successfully updated karma reason!
July 22, 2011 4:49:21 PM from Demigod Forums Demigod Forums

New Rook

Hardly uses the hammer eg: He'll be auto-attacking someone right infront of him, drop a tower or do a boulder roll, but rarely the hammer when it should be dropped on someone (that is level 7+ and in range)

Likes

How Rook pushes up right infront of the towers, and will actually retreat at full health when threatened.

But, he should be dropping towers while waiting.

This push to the tower behavior does have 2 problems though

1) When he has treb hat, he does not need to be so close
2) If he pushes up to the double towers on the sides of cata, his behavior goes out the window if you come at him from behind. He'll run towards the towers, and start cycling through behaviors while choosing none. (he'll run towards the portal flag, stop, turn around, try and hit a tower, stop in mid swing, start running back to his tower, turn around and attack etc... really funny.

Reason for Karma (Optional)
Successfully updated karma reason!
July 22, 2011 6:57:51 PM from Demigod Forums Demigod Forums

Thanks for the play test.  I'll take a look at that.  I'll likely have a new version out soon as well.  Made quite a few tweaks and sorted orb of defiance usage.

 

version 0.27.06 BETA
- reduced sigil activation health % from 50% to 45%
- changed orb of defiance usage check so that it will consider using it before sigils
- removed grunt check on orb of defiance (previous the AI would refuse to use use the orb if the threat level was < 15)
- added nearby enemy hero check to orb of defiances - if no enemies nearby, then orb will not be used
- reduced the value of narmoth's ring on the AA ub build so that it is not choosen as the only item at the start of a game on nightmare difficulty
- reduced the captureflag override at the start of the game from 60 seconds to 40 seconds
- disabled the attack override to allow the ai to make its own decisions based on weight
- Reduced the reteat values if there are nearby enemy heroes and towers from 85% to 75%
- modified rules for dg vs dg fights.  AI will run if there are more enemies than allies present

Live now

 big changes that need tested highlighted.  Note - these all have a pretty big impact on the ai's behavior.  The question is whether or not the improvement is really an improvement, etc.

 

Reason for Karma (Optional)
Successfully updated karma reason!
July 22, 2011 7:17:04 PM from Demigod Forums Demigod Forums

Changes look nice! I'm curious so i skip bed for an ai battle!

To Rook at 0.27.05

I still stink hammer salm at Lvl 6 would be early enough. It's oom often.

And for sure it would be nice to teach the ai to you boulder roll at close range and immediatly cast hammer slam because it's slam miss often... But it's notmagic wonder land I guess...

Reason for Karma (Optional)
Successfully updated karma reason!
July 23, 2011 5:29:28 AM from Demigod Forums Demigod Forums

Concerning 0.27.06 BETA, normal difficulty, cataract, high towers

3 Rook vs 3 Sedna

Well, I was tired yesterday and didn't look into details but it seems there were more ties. The DG standing out of range of the other and doing actually nothing like waiting for the other to do something. There position was not to bad though, it was in health flag lane two Sednas at the tower, 2 Rooks at the flag when I remember right.

One situation, I guess, the fleeing rule 1 VS 2 failed. It was Rook vs 2 Sednas at mana flag. I think Rook retreated because of low life because he engaged them first.

I'll look deeper into it tomorrow, unfortunatly no more spare time today.

Reason for Karma (Optional)
Successfully updated karma reason!
July 23, 2011 4:14:42 PM from Demigod Forums Demigod Forums

yeah - I feel like the changes I've made have abated the stuck dg issue SOME, but its still certainly there. 

I'll have to do some more test on the fleeing logic.  also, I think I'm going to set the sigil value back to 50%.  For some reason, it doesn't always seem to get cast at 45%.  Noticed this some time ago when I tried even more aggressive settings (like 35%). 

I'm not too sure about changing hs to 6 yet or not... that's actually the most common rook build (get 1st level of slam then)... but on hard difficulty with how I build it, I've found the ai generally is ok on mana.  around then... and if not, will be getting vlemish and/or plenor round about then as well.  Still... maybe. 

I'm not digging the utilization of hs as is though.  Could be used a bit more.  Its certainly improved though.  I'd love to be able to code the boulder/slam routine, but I currently don't know how and its not something I'm looking into atm. 

Thanks for the tests!  +1  you too orion!

Quoting KingBingo,
Is there any danger Stardock might incorporate and release as a update? Would save so many games for a player drop->insta concede.

There is no danger.

Reason for Karma (Optional)
Successfully updated karma reason!
July 23, 2011 5:19:32 PM from Demigod Forums Demigod Forums

Quoting OMG_pacov,
I'll have to do some more test on the fleeing logic. also, I think I'm going to set the sigil value back to 50%. For some reason, it doesn't always seem to get cast at 45%. Noticed this some time ago when I tried even more aggressive settings (like 35%).

It's probably being out-weighted by one of the flee actions, depending on what weights they return at what health percentages.  Make sure its GoalWeights are slightly higher than flee actions, and that those actions' CalculateWeights functions don't return larger values procedurally.

Quoting OMG_pacov,
I'd love to be able to code the boulder/slam routine, but I currently don't know how and its not something I'm looking into atm.

Make sure Boulder Roll's actions have slightly larger GoalWeights (by -1 to -5 at most) than the Hammerslam actions, then add this function above the Hammerslam actions and point their CalculateWeights at this instead of the AIAbility function: http://pastebin.com/TD6JL0QG
This should double Hammerslam weights if the potential target is stunned.

 

I also just found something that's probably messing with a bunch of stuff - the AI mod (unnecessarily) uses GoalWeights in the -50-100 range, while some of the AIAbilityUtilities functions hard-set certain goalweights to numbers in the -3 to -15 range depending on certain conditions.

Two things need to change - the insane goalweights in the mod are unnecessarily and probably harmful - try to stick to below 15 when possible, but those AIAbilityUtilities functions should be setting weights multiplicatively rather than directly.  Add these two overrides to the top of the mod's AIAbilityUtilities hook to fix the hard-set, and consider reducing some of the action GoalWeights to more reasonable values (because there are certainly other places in the AI that use hard-set values in these ranges): http://pastebin.com/KAAg49T2
Edit: GoalWeight normalization is really an all-or-nothing kind of thing, so contrary to what I just said, don't reduce any of them to normal levels until you're going to reduce all of them, otherwise it'll significantly change the AI's behavior/action preferences.

Reason for Karma (Optional)
Successfully updated karma reason!
July 23, 2011 5:37:30 PM from Demigod Forums Demigod Forums

Quoting miriyaka,
Make sure Boulder Roll's actions have slightly larger GoalWeights (by -1 to -5 at most) than the Hammerslam actions, then add this function above the Hammerslam actions and point their CalculateWeights at this instead of the AIAbility function: http://pastebin.com/TD6JL0QG
This should double Hammerslam weights if the potential target is stunned.

I'll take a look at this.  I think build tower on flag routine inpacts the hammer slams usage as well.

re: the ultra high weights - yeah, I started backing down many of the weights to more reasonable numbers, but rook, for instance, still has crazy high weights.  I'll tweak that and we'll see how things go.

I'll also check on the flee overrides.  I'd like to do away with them for the most part, but haven't determined how negative an impact that will have... lots of testing do to there.

Quoting miriyaka,
Edit: GoalWeight normalization is really an all-or-nothing kind of thing, so contrary to what I just said, don't reduce any of them to normal levels until you're going to reduce all of them, otherwise it'll significantly change the AI's behavior/action preferences.

well... what we have right now is a hybrid of normal and insane weights, so we are already in poop town.  I'll keep moving towards getting everything in line with normalized weights.  I'm sure it will be a few versions before I have all of that sorted though.  Thanks for taking the time again miri!

 

oh - one more coding request if you think of it.  I want to be able to evaluate if a flag is already locked.  Currently, the AI seems to spam locks even if one is already on there... doesn't happen 100% of the time.  Anyway, I've been working on the coding to improve the flag lock logic and this is would be a useful piece of code.  Thx

 

Reason for Karma (Optional)
Successfully updated karma reason!
July 23, 2011 6:00:51 PM from Demigod Forums Demigod Forums

Quoting miriyaka,
Make sure Boulder Roll's actions have slightly larger GoalWeights (by -1 to -5 at most) than the Hammerslam actions, then add this function above the Hammerslam actions and point their CalculateWeights at this instead of the AIAbility function: http://pastebin.com/TD6JL0QG
This should double Hammerslam weights if the potential target is stunned.

the code hits the following error:  attempt to call method 'GetPosition' (a nil value)

 

Reason for Karma (Optional)
Successfully updated karma reason!
July 23, 2011 9:52:35 PM from Demigod Forums Demigod Forums

Quoting OMG_pacov,
the code hits the following error: attempt to call method 'GetPosition' (a nil value)

Should have been called on initialAgent (the hero unit), rather than agent (a tracking table somewhere in the HeroGOAP mess).  My bad.

Also, I just realized that the function I gave you won't work universally for both squad and solo attack, so here's a new CalculateWeights for each: http://pastebin.com/TD6JL0QG

 

Quoting OMG_pacov,
oh - one more coding request if you think of it. I want to be able to evaluate if a flag is already locked. Currently, the AI seems to spam locks even if one is already on there... doesn't happen 100% of the time. Anyway, I've been working on the coding to improve the flag lock logic and this is would be a useful piece of code. Thx

This should be very simple - replace the existing 'if table.empty(flags) then' block with this, in both the InstantStatusFunction and ActionFunction: http://pastebin.com/M5KRKy2r

Edit: Actually, I'm already seeing a CanBeCaptured check in the ActionFunction, immediately after this where it chooses the flag to lock.  Are you sure it's doubling up locks?

Edit 2: Oh.  'flag' is not defined as local prior to the flag-choosing loop, so it's being saved as a global when a flag is found.  That means that once an AI has locked a flag, that flag will be stored in a global variable within the UseItemActions script module, and any situation where it can't find a capturable flag to lock, that variable will still hold the last flag that was locked (by any AI on either team) and will still pass the 'if not flag' check.

So, immediately after this line:

Code: c++
  1. flags = SortEntitiesByDistanceXZ(unit.Position, flags)
..and before the flag-locating loop, add this, so the flag isn't saved to a global:
Code: c++
  1. local flag = false
Reason for Karma (Optional)
Successfully updated karma reason!
July 23, 2011 10:50:18 PM from Demigod Forums Demigod Forums

thx miri - i promise I'll read your whole post before coding

Reason for Karma (Optional)
Successfully updated karma reason!
July 23, 2011 11:48:56 PM from Demigod Forums Demigod Forums

On the boulder roll thing with Rook. I tested several games today on bigger maps (I am starting to hate cata). AI rook use roll ALOT.

What I do have an issue with is that the DAMN rook never miss. I played against In1 today and he was a rook. Even he (which is a top player) miss a roll every now and then. Your OVERPOWERED AI dont.

Dont get me wrong....I LOOOOVE your AIs

Reason for Karma (Optional)
Successfully updated karma reason!
July 23, 2011 11:54:04 PM from Demigod Forums Demigod Forums

Quoting Maulkin,
What I do have an issue with is that the DAMN rook never miss. I played against In1 today and he was a rook. Even he (which is a top player) miss a roll every now and then. Your OVERPOWERED AI don

1st - thx for the feedback.  I've actually found that the rook misses quite often, tbh.  You can tact that up to bad luck, but I am 100% certain that the rook does not hit 100% of boulder rolls. 

Reason for Karma (Optional)
Successfully updated karma reason!
July 24, 2011 5:34:29 AM from Demigod Forums Demigod Forums

Right. Just me who dont get out of the way then lol!

Seriously, maybe it was. I was just kinda impressed how that AI always rolled the right way, even when I ran zikzak.

Reason for Karma (Optional)
Successfully updated karma reason!
Stardock Forums v1.0.0.0    #108432  walnut2   Server Load Time: 00:00:00.0000406   Page Render Time:

Stardock Magazine | Register | Online Privacy Policy | Terms of Use

Copyright © 2016 Stardock Entertainment and Gas Powered Games. Demigod is a trademark of Gas Powered Games. All rights reserved. All other trademarks and copyrights are the properties of their respective owners. Windows, the Windows Vista Start button and Xbox 360 are trademarks of the Microsoft group of companies, and 'Games for Windows' and the Windows Vista Start button logo are used under license from Microsoft. © 2012 Advanced Micro Devices, Inc. All rights reserved. AMD, the AMD Arrow logo and combinations thereof are trademarks of Advanced Micro Devices, Inc.