Inter-War uses a local attack log to enforce bashing limits. When another attack is dispatched, the server checks the relevant attack history in the active universe rather than relying only on what the interface displays.
How does this rule work?
The exact limit and time window can belong to the configuration of the current world, so one universal set of numbers should not be assumed for every server.
What exactly does the server validate?
Validation happens at dispatch. Even if an attack button is visible, the server can reject another mission when the current log shows that the configured limit has been reached.
How does this affect the mission?
If you attack the same target frequently, track your own missions and avoid planning exactly at the boundary. Fleet returns do not automatically erase the history used for the limit check.
When does it matter?
This mechanic belongs to world parameters and can be configured per universe. Do not import a fixed value from OGame or another server when the active Inter-War world has its own settings.
Common mistake
When planning, use the data shown in the current universe and current reports. The server-side rule is stable, while the specific factor or limit can belong to that world’s configuration.
Related FAQ: How do Noob and Strong Player protection work? · What determines how much debris is created after a battle?