The "eidolonOverride" night/day switching issue. #2434
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: OpenWF/SpaceNinjaServer#2434
Loading…
x
Reference in New Issue
Block a user
No description provided.
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
With "eidolonOverride" set to "night", the Plains' night lasted only 5 minutes before switching to day. However, when set to "day", the daytime also persisted for merely 5 minutes before reverting to night.
It does seem that the client does not update the time on the open world instance even after resyncing the world state, so I can see that this is not ideal. Unfortunately I'm not sure how much I like the added complexity of an extra constraint of "make it last as long as possible"... certainly not impossible, just... this feature is already quite insane.
If that's the case, could we consider swapping the definitions of "night" and "day" in the "eidolonOverride" configuration? For example, if I want to set the current state to nighttime, I would still define it as "night" in "eidolonOverride," but the program would actually run the daytime logic? The same principle would apply to daytime settings. The required 5-minute wait for switching between "night" and "day" would remain untouched as a transition buffer. Would this implementation be feasible?
Or maybe be able to manually set how many minutes day/night should have available, which gets always resetted after each worldstate sync/update. Not sure how practical that would be.
E.g. user chooses night time to have only 5 minutes available always: they join PoE, play until its for example day, then they leave & worldstate reports again 5 minutes for night. Basically more control regarding how long day & night cycles last for.