Vgstation13: AAC can be messed up by spooky ghosts

[D3athrow-Issues]

(WEB REPORT BY: kranenberg REMOTE: 172.93.109.202:7777)

Revision (Should be above if you're viewing this from ingame!)
1cca8e3cec8d193ab73be864480a3586c400f689

General description of the issue
spooky ghosts can mess up with specific AAC automation functions

What you expected to happen
to not be able to do this as a ghost aaaaaa

What actually happened
I was able to mess up with setting up air injector modes and names in an if/then/else block, including their addition and removal

Steps to reproduce if possible
be ghost
click aac
go wild

[jknpj]

ghosts were a mistake

edit:
Not even log'd in the poltergeist log, and you can't even tell a ghost did it in the href log unless you compare it with other log

[troots]

celt i love you and you're my favourite canadian but i was still able to change a scrubber mode from closed to open in an aac ifthenslse block

[Exxion]

God damn it

[PJB3005]

This is why we do not trust celt.

[ghost]

I found a different exploit with it - if you have a look at the code I had in that PR you'd be able to tell instantly the issue that I found absolutely fixed an issue with an AAC - I couldn't find a way to reproduce the issue in the original OP other than on that specific machine.

Now I've been shown how to reproduce the specific issue he's referencing, I can make a fix for it right away;
that is, if @PJB3005 doesn't actually live up to his rhetoric of banning me from the github forever and vetoing all PRs with code by me

[Exxion]

Yeah as far as I'm aware it's not actually possible to ban someone from the repo
Or if it is, only Pomf can do it

[PJB3005]

I wouldn't veto any bug fixes you nerd.

[Exxion]

Someone link the bugfix he closed

[PJB3005]

I wouldn't veto any bug fixes because he failed his 100 bugs challenge.

I still stand by my decision to close the air alarm one.