tain.totalcodex.net

First I'd like to thank the guys who helped me with my last problem, the collections issue. You guys rock and I did manage to get everything to work.

however a new problem has reared back its ugly head.

So I'm minding me own business and I try to start up Fear to begin working with those Collection refs that I was had been working on. Instead of Fear opening, I get the Mac OS script editor. Script editor gives me a dialogue saying the following:

"Open Dictionary

Unable to read the dictionary of the application or extension because it is not scriptable."

Ok, so this is bad right? It gets worse. I have an external hard drive which i have another copy of myth 2 saved on. I copy fear and loathing (loathing has been effected too) and see if that clears the problem. No dice.

So i've reinstalled Myth 2 SIX TIMES, to no avail. I did a permissions repair, as I am running OS X, also no effect.

so here i am again guys. like before i have never had this kind of trouble and I dont understand what happened. the only thing I have done is run Chaos, downloaded HeadEditX and added some tags to the local folder. I am at a loss and once again find myself here begging for help.

Thanks for keeping it all alive and thanks in advance to whoever can help me out with this beast of a problem.

- The Kraken

Well, I've never heard of this issue. Then again I don't have a Mac. I assume you have Fear and Loathing both in the Myth II folder and not somewhere else? They have to be in the Myth II folder where they can access the tags and plugins. Have you done anything to your computer or its settings since the last time it worked fine?

i solved the issue myself. turns out i somehow messed up that account. thankfully this wasnt my main account.

for future reference, if anyone ever hears of this one again, it will probably require that they delete their computer's login account, assuming they have one. Apparently, my luck wasn't so bad, as I had a secondary game login on my computer that i could afford to delete. As soon as I set up a new login account, my problem was fixed.

-_-