It's just my opinion and it's all up to the Devs anyway, but I can't see that re-naming the "When is it Tuesday?" problem to the "When is it non-Gregorian arbitrary Loreday #7 of 9" problem will make it any easier to intuitively track it. (Edit: lots of edits for typos/clarifications, should be done now.) I'm also not defending their choice to maintain their current design
I'm not saying your proposal wouldn't, perhaps, improve things for some players (though there are additional difficulties I haven't spelled out there), but it won't be viewed as elegant by the developers as it conflicts directly with design decisions they have thus far refused to revisit. That is (apparently) "a problem" for the Developers, who have not been willing to abandon the constraint. Your proposal requires them to abandon that constraint. But the whole problem of in-game time arises because the developers insist on having once-a-week events (e.g., in-game-Tuesday-night-only events). So the events will occur 2x a week, not once a week. "Tuesday only" events would now occur 2x in a single realworld day - once before 4pm and once after. Or is your in-game Day2 a Tuesday because it is occurring IRL on a Tuesday? Then you have duplicated in-game Tuesdays, and have likewise duplicated all the Tuesday-specific events. Is it in-game Wednesday, because in-game Tuesday has ended and so we "tick" up to the next day? Then in-game days will very rapidly become detached from real-world days and players will quickly be lost wondering "When is it Tuesday?" This is a problem for Players, and is arguably not an improvement over the current problems for players. What in-game weekday is your in-game "Day2" ? Let's assume Day1 was an in-game Tuesday. Then your "Day1" has expired by 4pm Tuesday. Suppose we implement your plan starting Midnight on the crossover between Mon/Tue. The difficulty with proposals like this is that you either confront the "When is it Tuesday?" problem or the "Too many Tuesdays!" problem (or both).
0 kommentar(er)
