Playing 1.24 version of Awesomemod-Idiotic question from an idiot in general
Vriska:
Scientist- I checked, and it said my version expired on 11/27/2011 09:40:09. I tried changing the value to 560, and when that didn't work, 1000. The expiry notice persists. Perhaps I am going about editing the value wrong, but I have no idea what factors are affecting this. Has this method worked for you before?
Scientist:
It is odd that your "build days" was at 0. That means the mod expired the day it was made. Usually it set at 7 - 14 when a new patch comes out and then lengthen once the mod has stabilized.
My version of AwesomeMod is set to expire 8/13/12. I just change the value to read <BuildLifeDays value="560" /> and set my computer's date to 9/1/12 and the game loaded fine. The new expiration date is 12/30/2013. Double check that your syntax is correct, and make sure of changes were saved. If that is the case, another issue must be involved. Could the version of S3PE you are using be an issue?
Vriska:
I updated my S3PE but I'm pretty sure that isn't the issue. I have no idea why my BuildDays were at 0. Does this look correct to you? Maybe I'm editing it wrong. All I do is right-click the _XML and click Notepad as shown below. At this point I think it's something else. My build didn't expire the day that it's saying it is either. It just started throwing that prompt at me about a week ago.
Scientist:
Your mod edit looks the way it should. The fact you only see the prompt now is also strange. Maybe EA has its own expiration date on its patches. Anyway, best of luck.
Vriska:
Thanks, I'll figure this out eventually. It'd be terrible if EA set their own patch expiration, though.
Navigation
[0] Message Index
[#] Next page
[*] Previous page