so I know it hasn't been asked in specifics here.
WRONG. It has been discussed here, go over to the AM bug reporting thread, and start there, it had been discussed recently. Then stop starting new posts about shit already being covered.
Last time you told me that, I pointed out that my post was actually made BEFORE it was being discussed, so get your dates right.
What are you babbling on about, I haven't mentioned this before with you. It was mentioned in the bug thread on the 20th, and probably even earlier, but can't be bothered looking for it, before you started this thread, so my dates are right fuckwit.
Second off, when I typed in the search the result was what I stated, I also said I removed my mods INCLUDING awesomemod so did not believe it to be a mod issue, therefore I did not see a reason to search through all the bug reports on the AwesomeMod thread, as to me the issue did not involve AwesomeMod. So I arrived at the conclusion that I best ask if perhaps this was a GAME issue rather then that of an AwesomeMod one.
If you had searched properly, and bothered looking instead of assuming, you would have seen the posts, and the reply from the FOJ, which is the same as the one he gave here. If you knew anything, you also would know that many EAxian bugs get reported in the AM bug thread in the hopes that the FOJ can quash them, while others place the EAxian bugs in the AM request section, which is why you need to search the ENTIRE site looking for previously posted problems and answers, not just where you assume they will, or might be.
Author