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
+182

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!
June 15, 2011 8:33:54 AM from Demigod Forums Demigod Forums

for your effort, I´ll gladly try to help.

 

You´re already trying to change the AIs stillstands. I read in another thread that you changed something concerning the creeps (if I remember right).In some games, I experienced that the AI just stood there and do nothing while I shoot at it with Regulus. It´s first action then was to retreat as it´s life went down to approximately 50%. Maybe this is fixed yet.

 

If I´m playing a game with 4 generals on my side, every sends me a monk, even if I´m a general myself. Don´t know if this can be changed. Maybe the AI could check if the the DG is a general or an assasin?

 

It seems to me, that DA just can´t handle shadow swap, you can even lure him to swap into a trap. I suggest to erase that skill from the AI build (even enhanced attributes would be an improvent I guess)

 

When a game starts at Warrank 10 the AI don´t shop. It just saves all of it´s gold for creep upgrades.

 

Farming creeps with skills seems not to be a high priority (never saw a Circle of Fire from TB, but that may be no fire build is included?). Most of them just AA the creeps which is very ineffective when catapults are out. Or even any priority at all because I see AIs standing beside the creep waves doing nothing (maybe UB oozing senselessly ^^). But maybe that is the same thing problem with the other stillstands.

 

So much for now.

 

Reason for Karma (Optional)
Successfully updated karma reason!
June 15, 2011 2:22:53 PM from Demigod Forums Demigod Forums

Getting rid of the builds is probably the best starting place as it will offer the best change with the least amount of effort.

-For certain all the minion builds must go
-All the UB builds except Spit/Ooze Life must go
-Builds should be optimized for skill damage output because the AI cannot rationalize like a human can (eg: AI Oak taking DJ at level 2)
-The AI should probably use 4 life / 1 helm builds (with perhaps Occ being the exception) when the 1 helm becomes Hungarlings and the AIhas Narmoth's, then the 1 low end life item should become Jtreads. (this should prevent an "overpower" phase late in the game when the AI is improperly geared and you can send it running) 

Other stuff that might take some work
-The AI could be godlike at skill jigging, try and implement skill/item cast cancel when one of the DGs in range has an interrupt
-The AI needs some new simple logic to tp for ganks (eg on cata: if primary tower is up, and they push the gold/cooldown flag, TP to the primary tower)

Get those done 1st, and then work on the bugs later (because they might not be solvable, like AIs standing around)

 

Reason for Karma (Optional)
Successfully updated karma reason!
June 15, 2011 2:49:08 PM from Demigod Forums Demigod Forums

Thanks, guys.

Quoting LORD-ORION,
Getting rid of the builds is probably the best starting place as it will offer the best change with the least amount of effort.

I've decided to completely scrap the existing sedna builds (there are 3) and just make 2 instead (heal tank and assassin tank).  Erebus had 2 builds and I'm going to scrap them for just a standard assassin_erebus.  And then there's the qot one - which I think I'll just add my build and keep the other one. 

Anyway, those changes are largely done.  I could use some play tests, though.  I'm wanting to know if you see any improvement in those ai.  Offline playtests are good for a start, but I'd like to see how they handle themselves in an online game. 

Reason for Karma (Optional)
Successfully updated karma reason!
June 15, 2011 3:23:59 PM from Demigod Forums Demigod Forums

We should have an AI tournament

There would be two "trials" for each build
1vs1 mirror match
3vs3 mirror match (the 2 alternate DGs use the same builds)

Maybe even offer up some prizes?

 

Reason for Karma (Optional)
Successfully updated karma reason!
June 15, 2011 3:27:24 PM from Demigod Forums Demigod Forums

Is your new version downloadable yet?

I´ve look in both threads but didn´t find a link.

Reason for Karma (Optional)
Successfully updated karma reason!
June 15, 2011 3:28:12 PM from Demigod Forums Demigod Forums

No - I haven't created the mod just yet.  I just wrote the code for it.  Still have to compile.  I'll post it here and link it in the op when I have it ready, though. 

Reason for Karma (Optional)
Successfully updated karma reason!
June 15, 2011 4:03:51 PM from Demigod Forums Demigod Forums

just finished coding and quick test to make sure I didn't break anything in my changes... looks good.  Will upload a version shortly.

Here's the changelog:

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" followed by the build name.

Reason for Karma (Optional)
Successfully updated karma reason!
June 15, 2011 4:08:05 PM from Demigod Forums Demigod Forums

Here's the link - give it a go:  http://www.box.net/shared/g8lbbhpojik4tbkjn6su

 

Reason for Karma (Optional)
Successfully updated karma reason!
June 15, 2011 4:52:19 PM from Demigod Forums Demigod Forums

added
version 0.26.37
bugfix - just resolving a syntax issue

Reason for Karma (Optional)
Successfully updated karma reason!
June 15, 2011 5:21:22 PM from Demigod Forums Demigod Forums

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

Reason for Karma (Optional)
Successfully updated karma reason!
June 15, 2011 5:50:05 PM from Demigod Forums Demigod Forums

0.26.38 - commentary:

1 test game vs darkliath 1v1+ 2 ai per team (each team with qot and erb as ai).

Weird bug (not related to my code) where both qot's just stayed at the middle a long time.  Need to adjust item builds and how the ai is designed to save money for currency.  Its saving way too much.  AI is always out of mana early - and I even tweaked ereb's build so that he doesn't get stun until level 6 (when he gets 2 levels).  Qot needs to learn never to summon a new shambler early... would be good if a routine was written so that she's summon shamblers when only at the crystal early mayhaps. 

hmm... I'm liking how ereb is working now for the most part.  Still doesn't quite understand when to mist, but its not too bad.  He opens alot of combats with bite and seems to be swarming when appropriate. 

Noticed in an earlier game that sedna is not pouncing anywhere near enough (especially on my assassin build).  Need to tweak that. 

If I can't figure out how to make the ai manage their mana better, I need to change it so that the ai gets more mana items earlier.

Reason for Karma (Optional)
Successfully updated karma reason!
June 15, 2011 6:19:05 PM from Demigod Forums Demigod Forums

Is the link you provided always updated? As I play a lot of ai games and would probably be a good tester.

Reason for Karma (Optional)
Successfully updated karma reason!
June 15, 2011 6:29:29 PM from Demigod Forums Demigod Forums

Quoting SLEDGE71,
Is the link you provided always updated? As I play a lot of ai games and would probably be a good tester.

Great - and yes - that link will always have the latest version - I just overwrite it every time.  Thanks!

Reason for Karma (Optional)
Successfully updated karma reason!
June 15, 2011 7:16:48 PM from Demigod Forums Demigod Forums

other thoughts about 0.26.38 - the ai needs to know when to shop.  This is much more obvious on nightmare level games.  The ai shops once at the start of the game.  Then, only if its forced to head back the crystal (with the exception of 1 dg going back at ws3 to cur1 - and 8, etc).  Need some sort of formula so it shops at some preset interval or if a certain scenario is met... like if ws < 7 and flag controlled and no enemy dg within 20 then shop else stay.  I'm watching 3 nightmare sednas with 10k gold wandering around... their best items are vlemish.  

Also - when we discuss modifying builds or folks have suggestions, there are a few things to keep in mind.  Right now, the dgs generally have pretty bad mana management.  To mitigate this problem, at least with erb, I decided to postpone when he gets stun.  A level 1 stun eats quite a bit of mana and is generally useless (and almost always useless when an ai is casting it at lv 1).  Waste all that mana on a stun and now you don't have bite available.  So, the solution is to stall on when I purchase stun 2 a bit.  On a normal build, I often get it at level 2 or 3.  On the current build, I'm getting stun 1 at level 5 with batswarm.  Then stun 2 at level 6.  This only gives erb the ability to blow mana on bite and mist until he hits level 5... and, he only uses stun when its starts to become useful (level 2 and >).  I could even alternate this build further so that he doesn't pick up all levels of stun until level 7.  In a human game, this is a pretty big jerk move.  With the ai, it might actually be the best way to handle things so that mana is available when its useful. 

Reason for Karma (Optional)
Successfully updated karma reason!
June 15, 2011 8:47:41 PM from Demigod Forums Demigod Forums

So I spent the last 2 hours going back and forth between AIGlobals and individual dg blueprints to get a better understanding of how these things work together. 

For those of you unfamiliar, AIGlobals contains all of the items (amongst other things) that a demigod can purchase.  It basically assigns a priority number to each item, and the dgs all use this global list to shop from.  So, in short, you come up with a reasonably decent kit that you think all dgs would benefit from and assign a priority (high = will buy 1st, low = will buy last, 0 = won't buy).  Anyway, this is where the bulk of the item selection logic comes in. You can also randomize the purchases by assigning an identical value (eg if plenor = 40 and nimoth = 40, then it is random as to which item the dg will buy first).  This is how the logic for getting priests/clerics works.  I'm guessing random in demigod might just mean alternating order.  Anyway...

The second piece of this are the individual dg blueprints.  In this, I can override the priorities for specific dgs.  For instance, let's say that all dgs start with 3k gold.  I decide that the base build is that all dgs will get nimoth (1500) and unbreakable (1500).  However, if you are using oak, and I decide the best build for him would be to skip unbreakable and get plenor at the start, I can override the values in the dg blueprint by assigning a higher priority there for the plenor.  Anyway, its a bit of a juggling act because you need to be aware of all of the values assigned in AIGLOBALS and then figure out what the impact will be if I choose to increase the priority on plenor.

Anyway, the sad news is that I'm leaning towards doing a rewrite of AIGlobals.  I just need to decide the best logic to use.  For instance, there are logic checks already in there that go off the current game time (eg if game time is < 20 seconds, then set a really high priority for X item - otherwise, set it to a normal level).  I can do all of that stuff.  Its just covering the various amounts of gold you get for easy/normal/hard/nightmare ai that gets tricky.  Not to mention all of the possible gold settings. 

Anyway, still trying to wrap my head around the best course of action.  Also, even though the layout of the items is logical (its grouped by item type - eg gloves, boots, etc), that organizational scheme does nothing to help me quickly see the priority levels associated... which means I have to sift through the code anytime I want to create an override to ensure that I'm not breaking anything.  For instance, I worked on a plenor override for sedna.  The override worked great, but on hard difficulty, it meant that she would get plenor and NOT monks or clerics.  Which.... is not desirable.  Anyway, I'm considering a rewrite that organizes the priorities in descending order instead of by type and then changing the priorities as appropriate. 

Maybe I can run a check on starting gold and update values based on that.  hmmm...

Reason for Karma (Optional)
Successfully updated karma reason!
June 16, 2011 12:46:01 AM from Demigod Forums Demigod Forums

There is no catch-all way to do what you're trying to do short of having hundreds of exceptions in each item priorityfunction.  This is a bad idea, both because this would be a ton of work and because these functions are run quite often.  If each of them is doing a dozen checks, you just added a lot of extra CPU work to the AI.  The citadel upgrade priorityfunctions are already a bit ridiculous, and the whole system really needs to be re-architected, but that would take a lot of time and energy (as well as a completely new approach to prioritization).

If you really want to try adjusting item priority based on AI difficulty, there should already be a utility function in AIGlobals for returning AI difficulty level, from 1 to 4 (1 being easy, 4 being nightmare).

Reason for Karma (Optional)
Successfully updated karma reason!
June 16, 2011 8:37:45 AM from JoeUser Forums JoeUser Forums

Quoting miriyaka,
If you really want to try adjusting item priority based on AI difficulty, there should already be a utility function in AIGlobals for returning AI difficulty level, from 1 to 4 (1 being easy, 4 being nightmare).

But even if I go that route, you are saying that would also likely be way too cpu intensive?  Believe me - I'd rather not take all the time only to have it bog the systems down and be a mess.

Reason for Karma (Optional)
Successfully updated karma reason!
June 16, 2011 12:50:51 PM from JoeUser Forums JoeUser Forums

miri (or anyone else for that matter) - I'm noticing some comments in AIGlobals like #Ai sensor wants to shop.  Where can I find the code that drives this?  Eg when the ai will shop.  I know there's a code that forces an ai to get currency 1 at ws3, but I'm not sure where it is.  If its in AiGlobals, I'm just missing it.  appreciate any help pointing me in the right direction.  My overall goal would be to reverse engineer that code and perhaps mirror it by sending a random AI back to shop if they hit certain parameters. 

Reason for Karma (Optional)
Successfully updated karma reason!
June 16, 2011 11:09:15 PM from Demigod Forums Demigod Forums

Created a spreadsheet that should help quite a bit in updating the priority levels in AIGlobals. 

https://spreadsheets.google.com/spreadsheet/ccc?key=0An02sqdF5v-EdFdzMENSTlRsTEhJV2tlMjltSUpNUGc&hl=en_US

I did not include artifacts or consumables.  Added citadel upgrades 12:21AM. 

 

 

Other quick thoughts - I'm not going to release a finalized version until there is a reasonable improvement or enhancement.  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; instead, when its worth a real release, then it will have one.  That's prob a bit in the future... but who knows, I've probably dumped a good 6 hours over the past 2 days alone in going through the code and various tests to make sure I understand how it works.  As you can see, I'm starting to document the priorities/existing logic.  Once that's complete, I'll probably make a few minor tweaks, but nothing super interesting. 

Also - if you are testing and manage to get another game going with another tester, BOTH OF YOU should redownload the mod and install prior to playing.  I expect I'll be releasing some updates fast and furious and you will likely get a desync as I'm using the same UID for each version... at least if I remember right.

What does the existing ai mod do well? --note, very minimalistic view based on what I'm looking at now

  • ai consistently gets currency 1 right around ws3 (this means I can also reverse engineer the function and force other things to happen at certain times - trips to shop, for instance)
  • ai FORCES 1 ai to save for cur1 (eg forcing to save functionality exists - i just need to understand it)
  • ai consistently is on top of creep upgrades when ws 8 hits - and the other team's ai will attempt to match - works perfect
  • existing logic for healers (monk/cleric, etc) is excellent.  The generals vary what they get and don't all stack bishops end game.  This could only be improved by forcing a 3rd general (if present) to stick with clerics for heal bonus potential.  Additionally, the code that assigns healers is generally pretty great.  Could be improved some though... but quite a bit of additional logic required to maximize 

What does the existing ai mod do poorly

  • does not always get fs1 when its needed - it does a great job of this if the ai is set to normal, poor job if ai is set to hard, terrible job if ai is set to nightmare
  • ai does not scale intelligently based on different levels (easy,normal, etc).
  • ai does not consider shopping enough.  We need to strike a better balance that takes into account the dg's total money and required upgrades.  If I have 3 ai's at ws6 with 10k gold, maybe they should have spent a little bit of that money shopping.  But, we must make sure they also reserve money for important or CRITICAL upgrades
  • mana management... this gets more tricky... I could write a ton of code, but I'm told that will slow things down if I make conditional statements for usage... and the logic could get crazy to emulate a human (eg bite if full mana and enemy at < 1k hp.... bite if 50% mana if enemy at < 1k... anyway, that would be the most detailed level of tweaking and awesome... but the code get's crazy and then I overtax the cpu... especially if I apply this logic to all dgs... with 10 or so conditional statements per ability... anyway, bad idea.  Perhaps my approach with erebus is most appropriate - stall on getting mana intensive skills until they can serve a huge purpose. 
Reason for Karma (Optional)
Successfully updated karma reason!
June 17, 2011 12:21:10 AM from Demigod Forums Demigod Forums

Quoting Plaguewraith,
for your effort, I´ll gladly try to help.

Thanks!  Obviously, I'm looking for feedback on any version I release and bugs/feedback on the current version as well.  When you post, please let me know what your test scenario was (eg I played solo vs ai... XvX on what map... what difficulty the ai was set to).  Thanks!

Reason for Karma (Optional)
Successfully updated karma reason!
June 17, 2011 1:30:03 AM from Demigod Forums Demigod Forums

Quoting OMG_pacov,
But even if I go that route, you are saying that would also likely be way too cpu intensive? Believe me - I'd rather not take all the time only to have it bog the systems down and be a mess.

As long as you keep the conditions simple, and don't apply them to every single item, it should be ok.  Checking AI difficulty is an extremely simple check, as is game time, so those kinds of things are fine.

The main problem right now with citadel upgrades is the ShouldSave function, which I think peppe added to AIGlobals (if not, it's in AIShopUtilities or FriendlyAsset).  That gets run on every single upgrade, and it's long and convoluted.  That's also the answer to your second question - it's what determines what an AI should be saving for, but I can barely understand the logic peppe used in it, and am not entirely sure what his goal was.  Again, it's something that really should be re-written to only run once per shopping trip, instead of once per available upgrade.

Part of the issue with that function is that it's trying to do something that certain people requested that hurts the AI in another way.  Its general purpose is to force the AI to save for citadel upgrades, so that human players in a multiplayer game don't have to.  The obvious downside to this is that the AI spend 95% of their income on upgrades, and become liabilities in combat, and their general behavior and health sensors aren't tweaked finely enough to keep them alive against human players with their inferior item loadout, level, and skill use.  There is no good solution to this, and any of the half-assed solutions would be very complicated.

Reason for Karma (Optional)
Successfully updated karma reason!
June 17, 2011 8:56:28 AM from JoeUser Forums JoeUser Forums

Quoting miriyaka,
ShouldSave function

Quoting miriyaka,
Again, it's something that really should be re-written to only run once per shopping trip, instead of once per available upgrade.

OK.  I'll look into this.  Thanks.  On the other side of things, though, at least whatever code he wrote does work... hopefully its something that can be refined.  I'm not exactly sure how to write it so that it would be restricted to checking each shopping trip, though.  When you say once per available upgrade - what does that mean in practice? 

Quoting miriyaka,
There is no good solution to this, and any of the half-assed solutions would be very complicated.

Guess we'll see.  I'm not looking to implement a half assed solution at any rate.  But I am going to try to come up with improved logic for what should be done.  And likely that will queue, at least initially, off or ai difficulty level. 

Here are a few of the things I'm thinking

  • Send the ai to shop at more appropriate times - if the ai can be forced to return at ws3 to buy cur1, then it should be possible to send the ai to the back if certain criteria is met - possibly even stagger when the ai would head off to shop
  • Adjust the logic for saving after cur1 is bought.  We still want creeps at ws8 if possible, but we need much more tweaking to make sure the ai is buying for itself.  Maybe some sort of total deaths check would prioritize who would save for late game. 

Anyway, there's definitely room for improvement and I'm willing to sink some time into development, so it will, at the very least, get a little bit better than it is. 

Reason for Karma (Optional)
Successfully updated karma reason!
June 17, 2011 9:37:01 AM from Demigod Forums Demigod Forums

Hey!

I´ve done two games yet, where I simply stand at the crystal and watch the AI doing it´s job. I may miss some things because I don´t sit at the monitor all the time.

 

Well two things seems odd to me.

(Uberfix 1.05 is always on)

Zikurat (4vs4)

QoT casts Shamblers even if there are still 2 alive. You already mentioned that it has problems with that. I don´t know if a check can be apllied that make the AI only cast them, when there are none (or only two at skilllevel 3 if the build skills shamblers higher than one)

 

Cataract (QoT & LE vs Rook & Reg)

QoT and LE stood in the middle at the edge of their base (where the creep wave split). Reg stood just in sight behind the exp flags which was owned by his team. And that was it. They stood there this way for at least 90 up to 120 seconds. The tie was broken when Rook teared down the tower on the health side and creeps engaged the tower of the center.

It seems that they were stuck in the awaiting of the other to act. And because both sides where waiting it was a tie, maybe?

 

If that is so, the AI maybe should more act and less not react. Like checking if the flag is ours or not and if not just go for it.

If another DG is in sight and no enemy structures are near, it should engage. The same for towers when reached a specific lvl: No DG near but a hostile structure: engage it. (if such behavior can be realized)

 

 

Another thing for cataract in general is, that the AI very often takes the way through the center and try to catch both creep waves. This may be a tactic for DG with AoE, but still it´s very selfish. The other have their problems with the creeps and it is easy to catch them their with less HP. I would suggest that the AI splits up the lanes and just "think" about the middle if the flags is being captured or holded by the enemy.

 

One thing that would be good to know is, if the AI can check the perception of a controlled DG. Like how many friendly structures and DG and how many hostile are aroung to check if retreat or fight is the better option. And if the AI can check the HP of an opposing DG. I can start a fight with the AI with half life, knowing it will retreat if I manage to damage it enough. So it leaves me alone when it´s life down to 50%, but mine is just around 20%. (Sometimes, the other way around, it simply fights to death and don´t try to retreat even if the odds are against it. Seems to be some kind of random decision?)

 

Reason for Karma (Optional)
Successfully updated karma reason!
June 17, 2011 9:55:48 AM from JoeUser Forums JoeUser Forums

Thanks, Plaguewraith!

Bug list

  • QoT will waste mana resummoning shamblers even if she is already has her current max.
    • The desired behavior would be for QoT to summon all possible shamblers at the crystal whenever she is there and ONLY resummon them away from the crystal if she has X mana
  • Frozen AI > 30 seconds - ai will at times refuse to do anything unless approached by another dg.  Need some sort of idle check to give them a kick in the rear if they are just standing still for X seconds... might be something in the code that does this already, but peppe commented it out
  • 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.

I'm pretty sure there is currently functionality that tells the ai how to behave it mutliple dgs are present, but that code can be refined more.

Reason for Karma (Optional)
Successfully updated karma reason!
June 17, 2011 10:28:43 AM from JoeUser Forums JoeUser Forums

Miri - if you have the time and inclination, would you mind taking a look at the QoT summoning shamblers problem and see if you can come up with some code?  At its most basic level, I just don't want her trying to summon more shamblers if she is already at the max for her level (eg shamblers 1 and 2 = max 2, shamblers 3 and 4 = max 4).  I'm going to stay focused on re prioritization for a bit and probably won't get around to trying to sort this for a bit. 

Reason for Karma (Optional)
Successfully updated karma reason!
Stardock Forums v1.0.0.0    #101114  walnut1   Server Load Time: 00:00:00.0001407   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.