Thanks, I'll reflect the correct case usage of Lua in the next version of the guide (I'll probably update it whenever I release an AI update so the two are in sync)
AI Development Guide and M27AI v74 Devlog
M27AI and M28AI developer; Devlogs and more general AI development guide:
https://forum.faforever.com/topic/2373/ai-development-guide-and-m27ai-v71-devlog
https://forum.faforever.com/topic/5331/m28ai-devlog-v112
So I decided I might actually post something more relevant
Full stops vs colons – continuing the above example, oUnit.GetUnitId() will return an error, but oUnit:GetUnitId() won’t.
It's maybe worth mentioning why that happens. oUnit:GetUnitId()
is syntactic sugar for oUnit.GetUnitId(self)
. So if you wanna you the version with .
you have to pass self
as first arg.
F9 opens up the debug window (you may want to change the game resolution to windowed to more easily access this).
That's a log window, not debug. You can open the debugger with Ctrl+F9 or /debug
and that's way better for debugging then trying to print things into the log. Since it works as any debugger you are used to, pauses the execution on the line you seleceted and lets you see whats inside global and local variables.
The below link also appears to give a list of core/global functions that can be used (I’ve not tested these to see if they all work, or even if they’re for FAF rather than SupCom2):
https://supcom.fandom.com/wiki/LUADOC_1.5.3599
It is for FA, some of these functions are documented here https://github.com/FAForever/fa/tree/deploy/fafdevelop/engine
I’m not using Github since I’m working on this on my own, and since I doubt I can get the same ease of use I currently have with changing something offline and instantly seeing the results in-game after a Ctrl+F10 restart. However, Github is used by a number of the AI developers so there’s likely some significant benefits to it.
Git is very useful even if you're working alone, as you have history of changes and you can easily switch to previous versions if something breaks. The game can use files from any location, so for my development, it uses files from my local git repo. It's just a matter of setting your own init file https://github.com/FAForever/fa#running-the-game-with-your-changes
To keep things simple (as I couldn’t get more complex builderconditions{} with multiple variables to work, despite seeing it being used in other AIs people have done)
So build conditions are defined in a table
BuildConditions = {
{BMBC, 'BaseEngineersEnabled', {self.BaseName}},
{BMBC, 'BaseBuildingEngineers', {self.BaseName}},
{BMBC, 'HighestFactoryLevel', {i, self.BaseName}},
{BMBC, 'FactoryCountAndNeed', {i, j, pType, self.BaseName}},
{BMBC, 'BaseActive', {self.BaseName}},
},
so here, you have 5 build conditions, each in it's own table.
local BMBC = '/lua/editor/BaseManagerBuildConditions.lua'
first value ( BMBC
) in the table is thr path the file you wanna use
second one ('BaseEngineersEnabled'
) is name of the function in that file to use
third ({self.BaseName}
) is table of arguments to pass into that function
AI brain is always passed as first argument, and then all other that you specify in the table
So you could rewrite your example to this:
-- Inside the builder
BuilderConditions = {
{MIBC, 'Is1NearbyMex', {11}}
},
-- Inside MiscBuildConditions.lua
function Is1NearbyMex(aiBrain, distance)
local iNearbyMex = MapInfo.RecordMexNearStartPosition(Utilities.GetAIBrainArmyNumber(aiBrain), distance, true)
if iNearbyMex == 1 then
return true
end
return false
end
This way you can already specify the distance for chehcking the nearby mexes.
Determine com start position
This function should do the trick
brain:GetArmyStartPos()
To help with this, I first wanted to understand what the various variables feeding into it were, so made use of the log function for each variable in turn; where it returned an error due to being a table value that I was trying to put into the log
Best would be to use the debugger to see whats what, as you can open the tables.
But if you really wanna dump the table into the log you have to use LOG(repr(table))
@speed2
Thanks, in particular for the debug window - I expect using that would've drastically cut my debugging time! I'll update for your comments in the latest version.
Unfortunately I can't get the debug window to work for me (I just get an error message) and some other people have had the same problem. Asking in the AI discord Jip thought that you need to do an install from the cd version of the game not steam but that you may know the exact procedure?
Error message below in case it helps:
M27AI and M28AI developer; Devlogs and more general AI development guide:
https://forum.faforever.com/topic/2373/ai-development-guide-and-m27ai-v71-devlog
https://forum.faforever.com/topic/5331/m28ai-devlog-v112
unpack this https://mega.nz/file/VlRCXajY#UMsAx9IR1dIOqX72bPpOYytR6FS3zO1DGVPT2AhSPAY
into \THQ\Gas Powered Games\Supreme Commander - Forged Alliance\coderes\Engine
@speed2
Don't think I've got that folder with the steam install, I've got the following:
C:\Program Files (x86)\Steam\steamapps\common\Supreme Commander Forged Alliance
(this doesn't have a coderecs folder, and adding one in doesnt resolve the issue)
I've also got the FAF location:
C:\ProgramData\FAForever
same issue as with the steamapps folder
(just in case I also tried the \Documents\My Games\Gas Powered Games\Supreme Commander Forged Alliance folder but no luck).
Is there anywhere else I may have missed for a steam version?
Although I'd hoped I'd got the CDs for both as well, checking I've only got the CD for the original supcom so cant try a fresh install via disc.
M27AI and M28AI developer; Devlogs and more general AI development guide:
https://forum.faforever.com/topic/2373/ai-development-guide-and-m27ai-v71-devlog
https://forum.faforever.com/topic/5331/m28ai-devlog-v112
It belong to the game instalation folders, and fast few ppl having this issue resolved it by creating those folders
v4 changes (in reality v2, but when I uploaded the mod on its first release I had to rush out a couple of hotfixes where I'd forgotten to remove debug logic and accidently introduced a bug that affected all games!)
- Fixed various bugs (see 3.14.3)
- Slightly improved pathfinding performance (see 3.15)
- New AI logic which will detect enemy threats and send units to deal with them (see 3.16)
- New AI logic which attempts to maintain intel over the map to stop surprise attacks (see 3.17)
I've also updated the guide to reflect speed2's comments (as well as a couple of other minor points/sections, such as a bit on uploading a mod and some tests that I now run before uploading)
M27AI and M28AI developer; Devlogs and more general AI development guide:
https://forum.faforever.com/topic/2373/ai-development-guide-and-m27ai-v71-devlog
https://forum.faforever.com/topic/5331/m28ai-devlog-v112
v5 changes - these were mostly about the ACU, making it more aggressive and less suicidal
- Fixed various bugs and improved some error handling (see 3.18.4)
ACU improvements (see 3.19): - ACU will try to expand to high reclaim or mex locations, while building on mexes it comes across and reclaiming
- ACU will have scout and MAA support
- ACU tries to kite enemies it comes across
- ACU uses manual overcharge to overcharge optimal targets
Also updated the guide slightly to add details of the AI development discord channel in FAF (separate to the main AI development discord), and a couple of common hard crash errors
M27AI and M28AI developer; Devlogs and more general AI development guide:
https://forum.faforever.com/topic/2373/ai-development-guide-and-m27ai-v71-devlog
https://forum.faforever.com/topic/5331/m28ai-devlog-v112
v6 Hotfix - My AI broke with the recent FAF patch, so this is primarily to fix that. I was in the middle of more extensive changes so my AI is less stable than I'd like but I figured it's better than a broken one! I've also held off on updating the dev log for this release.
Main changes made:
- ACU performs better underwater (reclaims units, tries to move to nearby land when it cant shoot)
- Improvements to ACU overcharge behaviour (it should OC when retreating, and also positions better against enemy PD)
- Switch to new error handling approach (orange messages now appear in the log with more detail; this also happens when any ACU dies)
Issues currently present I'm aware of (which shouldnt have a noticeably detrimental impact on performance, but will be noticeable to anyone looking at the log):
- 'MergeLocations' error message on certain maps - should just mean larger platoons dont regroup at a midpoint before attacking
- 'MexRaider' warning about the final waypoint - in most cases just affects which mexes are targetted (in rare cases might cause a delay in the platoon doing anything)
- 'Stuttering'/delays in performance on certain maps (e.g. open palms)
M27AI and M28AI developer; Devlogs and more general AI development guide:
https://forum.faforever.com/topic/2373/ai-development-guide-and-m27ai-v71-devlog
https://forum.faforever.com/topic/5331/m28ai-devlog-v112
V7 Update - T2 is now here! My changes were focused on creating my own engineer and platoon formation functionality (which took far far longer than I was expecting due to various difficult bugs - a lot of work for not much benefit), but at the end I threw in some basic upgrade logic so my AI now gets T2.
Various bug fixes. More notable ones are that the AI should work better on adaptive maps that 'hide' some of their mexes, and should be less likely to try and build on unpathable mexes
Custom platoon formation and engineer functionality. A couple of more notable features of this are that engineers now work together to build 1 building (e.g. power) rather than independently try and build 5 at once, and factor in what mexes theyre already planning to build on when choosing where to expand
Building upgrade logic - AI will now upgrade mexes and land factories (meaning for the first time T2 units can hit the battlefield!)
Load spreading of functionality to help counter the CPU performance hit of these changes
I've also updated the guide for a couple of points (e.g. including a section on events)
As before, much more detail on the changes/my thought process as I went about implementing them is in the dev log.
M27AI and M28AI developer; Devlogs and more general AI development guide:
https://forum.faforever.com/topic/2373/ai-development-guide-and-m27ai-v71-devlog
https://forum.faforever.com/topic/5331/m28ai-devlog-v112
v8 Hotfix - Fixed a game crash that could happen if the AI lost an upgrading building (thanks to relent0r for for flagging there was a crash), along with a couple of other minor bug fixes.
M27AI and M28AI developer; Devlogs and more general AI development guide:
https://forum.faforever.com/topic/2373/ai-development-guide-and-m27ai-v71-devlog
https://forum.faforever.com/topic/5331/m28ai-devlog-v112
v9 Reintroduced air units:
- Air scouts are built to periodically scout locations of interest
- Interceptors are used to help defend against enemy air attacks
- Bombers should target enemy units of interest.
- Air factory should be built early if there's enough power (and by a hydro if one is available)
- Various bug fixes and small tweaks to behaviour - refer to 3.27.6 - 3.27.7 of the guide
M27AI and M28AI developer; Devlogs and more general AI development guide:
https://forum.faforever.com/topic/2373/ai-development-guide-and-m27ai-v71-devlog
https://forum.faforever.com/topic/5331/m28ai-devlog-v112
I admire the guide / developers log that you are keeping
A work of art is never finished, merely abandoned
V10 - Implemented anti-turtle logic:
- Use of T2+T3 MMLs and mobile arti to break firebases
- Ecoing (not very well, but better than before)
- Reduced turtle feeding
Misc changes:
- Large bomber attack for if we end up with lots of spare bombers
- T3 air factories can be built/upgraded
- Support factories will be built/upgraded instead of HQs
- Higher tier power is built sooner
- Engineers can request guards
- Various bug fixes (see section 3.30.2 of the guide)
- Updated the guide with details on how to run in FAF Develop offline
My AI also has a new icon
For anyone that's interested in the background to the last 5 versions/2 months - back at v5 I was crushed by gunner1069 (I usually get them to play a match every couple of weeks against the latest AI version) with a simple turtle strategy on Theta Passage - they didnt bother getting any mexes and instead just rushed T2 PD with their ACU and my AI had no answer despite having 4x the mass income. My primary focus in all the versions since then has been coming up with the logic that will give my AI a chance in that scenario.
Unfortunately, a relatively simple plan for a human (dont send units single-file into PD, upgrade mexes and then attack with MMLs) required a bunch of different bits of logic:
- Checking for PD and running away from it (so the enemy isn't fed kills/mass), without running away when we're already in range of it and able to beat it (I had some frustrating to watch games where my AI would charge in at a firebase, overwhelm the shields, be about to destroy everything, before deciding to run and turning a winning position into a loss)
- Realising there's PD when it kills our land scouts without being picked up by their radar
- Making use of air scouts to reveal 'hidden' PD to avoid suiciding units and the ACU into the PD
- Quickly expanding to uncontested mexes (including on enemy side of the map)
- Focusing on maintaining map control and ecoing if faced with a turtle rather than trying to break them immediately, which in turn requires various logic for identifying if we're against a turtle, upgrading mexes, building T2+ buildings, upgrading factories, making use of support factories, etc. (I've still not got basic things done like capping mexes with mass storage)
- Using indirect fire units to attack PD/long range enemy units while both protecting them from enemy mobile attacks, and not suiciding our own units trying to protect them
These changes also mean my AI will be worse in other situations - e.g. against a non-turtle it might choose to eco when it would be able to finish the game by pressing the attack, and it's also still poor at the mid-T2+ stage so extending the game via ecoing means it's more likely to snatch defeat from the jaws of victory. Long term though it needed to happen as a 'T1 or die' strategy only has a decent chance on 5v5 maps.
M27AI and M28AI developer; Devlogs and more general AI development guide:
https://forum.faforever.com/topic/2373/ai-development-guide-and-m27ai-v71-devlog
https://forum.faforever.com/topic/5331/m28ai-devlog-v112
@maudlin27 Nice list of g
Changes of updates for you Ai mod, I'd like to extend you the offer it have this in a more of a cleaner formate over on the new faf wiki, if this is somtbing your interested in please send me a pm here or on the faf discord and I can set you up with a page
"The needs of the many outweigh the needs of the few" - Spock
v11-v12 update:
The big thing I've been working on in these 2 updates is an alternative approach to pathfinding to replace my use of CanPathTo with a manual method that I can run at the start of the game and then lookup the pre-recorded results later in the game (rather than calculating pathfinding on the fly), since I figured this should be much faster.
Unfortunately I failed to factor in the consequential change this would have on other parts of my code, and while my replacement 'canpathto' check itself is much faster (especially on 81x81km maps), my overall AI is significantly slower! Since my new approach is based on terrain height differences, it will also be less accurate, so I've managed to achieve the worst of both worlds! However, it should at least be easier to get some CPU performance gains in the future, even if my first attempt has failed.
Various misc changes:
- Significant improvement in ecoing speed, including the ability to build mass storage
- MAA and Engineers shouldn't be overproduced as much, and certain T3 MAA shouldn't be treated as land attack units
- Mobile artillery should attack enemies (instead of changing their mind every second)
- Surplus engineers should reassess what they do periodically instead of assisting the same factory
- Minor improvements to building and upgrade decisions to deal with mass overflow and power stall
- SMD can now be built in response to a nuke threat
- AI will now stop ecoing if it detects certain experimental threats
- Various other bug fixes and smaller tweaks to the AI
See 3.34.3 - 3.36.6 for details of the changes and the journey I went through getting an alternative pathfinding logic to work.
M27AI and M28AI developer; Devlogs and more general AI development guide:
https://forum.faforever.com/topic/2373/ai-development-guide-and-m27ai-v71-devlog
https://forum.faforever.com/topic/5331/m28ai-devlog-v112
v13 Update:
My AI should finally have a chance (albeit a small one) on water based maps. Previously, it would ignore naval units (meaning they'd only die if they happened to get within firing range of a unit). It'd also assume it could send land units to attack the enemy base meaning on island maps it'd produce way too many tanks that would do nothing.
Now, it should try and deal with enemy naval threats, while also focusing on building amphibious and hover land units (although it still doesn't try to build any naval units).
Various misc changes and bug fixes, including:
- Fixed hard-crash when sera sniper bots were built
- Improved engineer logic for nearby enemies
- Slightly less suicidal ACU behaviour (but only when it feels life has meaning)
- Engineers are less likely to block units in the base when they have nothing left to do
- Introduced fixes for the pathfinding on several maps where the new logic was giving incorrect results.
M27AI and M28AI developer; Devlogs and more general AI development guide:
https://forum.faforever.com/topic/2373/ai-development-guide-and-m27ai-v71-devlog
https://forum.faforever.com/topic/5331/m28ai-devlog-v112