I'll throw in advanced Github permissions for future maintainers.
Do any devs want to fix/maintain Phantom-X?
"Nerds have a really complicated relationship with change: Change is awesome when WE'RE the ones doing it. As soon as change is coming from outside of us it becomes untrustworthy and it threatens what we think of is the familiar."
ā Benno Rice
@femboy I've already done a decent bit of lua for FAF 
I may eventually look into fixing Phantom-X, but I have other things on my plate these days. Hopefully someone will volunteer 
pfp credit to gieb
I won't commit to maintaining it, but if no-one volunteers in the near future I might have a brief look both to see if it's an easy fix, and if my AI is compatible with it. However my experience of Phantom is a grand total of watching 1 cast and part of 1 replay.
M27AI developer; Devlog and more general AI development guide:
https://forum.faforever.com/topic/2373/ai-development-guide-and-m27ai-v70-devlog
https://forum.faforever.com/topic/5331/m28ai-devlog-v4
@maudlin27 it is likely related to this:
We completely re-implemented how the game state was computed to fix the infamous draw bug. In particular lua/sim/MatchState.lua
A work of art is never finished, merely abandoned
@jip it seems like phantom does its own thing for full share vs no share so maybe something in that is outdated. Ill look through it when i have a free period.
I, for one appreciate the effort, folx.
"Learn Lua and be the change" is something you've almost tempted this zero-experience old-guy to try, but now is not the time in my life where I have the time, so thank you to those of you that do. Best I can do at this point is try to isolate things we find in our games and bring them up to smarter people. 
@SpikeyNoob I can look at it tomorrow, can you share the link here?
A work of art is never finished, merely abandoned