About Fragrant Error
wolryang:
My AM will expire today, So I downloaded new one.
But Fragrant error keep pop up.
I use 'aweconf' , so I think because of it.
so I downloaded new one both of it. ( mod & aweconf )
But keep pop up. and keep pop up after deleted all cache.
Plz Help me :'(
varmint:
Well, first of all, we need more information, like your patch versions, social security number, and the exact aroma of the fragrant error you received. When awesomemod throws an olfactory exception, the nature of the error can usually be determined by the odor produced. Did it smell like lilacs? sardines? I can't remember what either of those mean, but I'm sure someone more familiar with the manual will come along who can map them out for you.
Also, there's a thread to report bugs already, this maybe could have gone there.
Simius:
And post a fucking screenshot of the smelly errors so that they can be fixed, Christ.
spaceface:
The new AM is still in testing because of the new expansion pack. If you are not a Beta Tester you should not be using it. You do know that FSE's do not stop you from playing the game in any event.
If you wish to be a Beta Tester, you could post a copy of the error message in the appropriate Testing thread. Otherwise, do not use AM until testing is finished.
nekonoai:
I really do love the smell of error in the morning.
Navigation
[0] Message Index
[#] Next page