Hm? This is still the case? I had thought I'd made it public. Let me check one more time.
Posts by PhantomInTime
-
-
PhantomInTime added a new file:
QuoteDisplay MoreIMPORTANT: DO NOT HAVE ANY OTHER ACTIVE PRODUCTION MODIFIERS SUCH AS THOSE IN AIO OR SVM. DISABLE THOSE IF YOU WANT TO USE THIS MOD.
AREA CONSTRUCTION NEWLY ADDED! CHECK CHANGELOG!
Hello there! Thanks for your interest in my first mod! As the name would suggest, this mod allows you to reduce production times on items down to a percentage of the default value. I made this mod as an alternative to other production time modifiers that simply make crafting instant. I, however, wanted to have something that allowed you to simply reduce production times down to a "singleplayer" amount of time without getting rid of production times entirely.
Here are some examples based on reducing to 30% of the default value on Level 0 Crafting Skill:
Default:
Reduced:
Default:
Reduced:
Next planned addition (which will take considerable time to work out): Custom times for individual recipes!
-
This issue occurred even when I had no mods installed. I’ve come to think it’s likely a systems setting issue when the server looks at my system clock for a reference.
-
As the title suggests, I've had an issue where, after roughly 7-8 raids, the time displayed on a time sync will not be the actual time when the raid starts. It's usually about 5-6 in-game hours earlier than the selected time.
This does not happen gradually. It is very sudden where I might go in at what I think is a 10am time and it turns out to actually be 4am.
I've used mods that restart the timer at a certain time after each successive raid, effectively "freezing" the clock (through FAIT I believe) and never experienced this issue when doing that.
When this issue occurs, I am forced to shut the program down and restart the entire server in order for the time syncs to match up with their displayed time again when selecting it.
I don't believe these most recent logs will show this as I only started the program, had to do something else, then shut it down when I came back without ever entering a raid. If it is necessary for me to cause the bug to happen and then share new pastebins of the logs when it occurs, I will do so.
