Fandom

Castle Age Wiki

Guild Battles/iOS Festival Battles

< Guild Battles

1,054pages on
this wiki
Add New Page
Comments0 Share
Main article: Guild Battles

iOS Festival Battles are battles where two full guilds (created on the iOS platform by an iOS account) match up for a 2 hour battle of up to 100v100 players.

Battle Schedule

Guilds can opt in to single, two-hour timeslot at a time. This time slot can be changed when there is not an active battle at no penalty to the guild. Time slots for iOS festival battles are as follows:

  • 2am PST / 3am PDT
  • 8am PST / 9pm PDT
  • 2pm PST / 3pm PDT
  • 8pm PST / 9am PDT

Guilds are matched by their festival rank and their record over their last 5 battles. Guilds without an exact match will be paired with the closest match, and guilds that aren't ranked may be skipped entirely.

Festival battles last for two hours, or until all players on one side are dropped below 201 health.

Players and Gates

In Festival battles, each guild has 4 gates (labeled North, West, East, and South) with up to 25 players in each gate. Players can be assigned to a gate by a guild officer, or players will be automatically assigned to a gate.

Stun information

In Festival battles, players are considered stunned when they fall below 201 health, and cannot use active skills, nor can they have active skills used on them, at this time.

Token Regeneration

Players receive 10 tokens when joining, and regenerate new tokens every 5 minutes, for a maximum of 33 tokens during a single battle.

Rewards

Players receive Guild Coins and experience as usual. Players have 1 hour to collect their reward, though if they do not manually collect, they will receive their reward at their next time opening Castle Age, provided their guild has not been involved in another battle since then.

Ad blocker interference detected!


Wikia is a free-to-use site that makes money from advertising. We have a modified experience for viewers using ad blockers

Wikia is not accessible if you’ve made further modifications. Remove the custom ad blocker rule(s) and the page will load as expected.