Quote Originally Posted by cjbeagle View Post
I'd love to see the 2m window homogenization go up in flames, but I need to elaborate.

Currently, the 2m window informs (or at least should inform) fight design - this is probably worth preserving to prevent some jobs from getting screwed by downtime while others don't - having downtime timing that works for all jobs prevents jobs from being excluded from specific fights' rosters on those grounds.

However, the 2m window homogenization of job design could use variance - maybe some jobs do work on a 2m rotation, but instead of ALL jobs working based on that 2m window, maybe some could be on 1m rotations while others are on 30s rotations or 40s rotations - as long as they divide into 2m evenly, it works.

The problem with variable timing for raid buffs is that you run into anti-synergy between jobs that provide buffs on a shorter cycle and jobs that are on longer cycles, which would lead to concepts like 30s raid groups vs 2m raid groups, etc.

So I'd say that the important thing is to not have varying buff windows even if jobs have varying cycles, which means leaving the 2m raid buff window as-is is perfectly fine - they just need to stop acting like every job needs to be on 2m cycles - no reason you can't balance a 30s job to have the same output as a 2m job.
I like this idea as well, and that definitely makes a ton of sense!