Designed by Dino

§1. Definitions

1. Top Ten: The weekly, monthly, quarterly, or yearly issue of a Club Penguin Armies column designed for ranking the community’s active armies statistically.
   • This definition is not strictly just ten armies, but rather a traditional benchmark.
2. Active Army: For the sake of the Top Ten, an active army is an army that has hosted an organized event with tactics and/or organized uniform on a Club Penguin Private Server in the past four weeks.
   • Those who host organized events on army servers shall be recognized as an army regardless of the insular nature of these private servers.
3. Maximum Size: Shortened to just “max,” the largest number of people an army had online at the same time.
4. Club Penguin Private Server (CPPS): Also simply a “private server,” these are fan-made emulations of the original Club Penguin. They are further divided into:
   • Civil Server: A CPPS designed for regular playing use with a native user base and not strictly army-based. Recognized civil servers include New Club Penguin, Club Penguin Journey, and Club Penguin Legacy.
   • Army Server: A CPPS designed to favor armies—especially for battling, like CPA: Battleground.
5. Deduction: Also called a penalty, the decrease in an army’s points due to not following the Top Ten Regulations.
   • Multiplier: A form of deduction where an army’s average size points are multiplied by a decimal—whether a singular time or an extended time.
6. Rogue: A non-enlisted, civil server player that is counted towards the Top Ten if certain requirements are met.
   • Rogue Uniform: Event-specific uniforms wearing easily obtainable items such as (but not limited to) the Pizza Apron, Miner Helmet, and Tuba.
   • Rogue Events: Also sometimes called takeovers, events on civil servers that use rogue uniforms. These may also include organized recruitment session events.
7. Spawn Room: A form of room on a CPPS where people automatically spawn. Examples include Plaza on Club Penguin Army Battleground or the Welcome Room on Club Penguin Journey. Traditionally, Town may also be applicable to this for other CPPSes.
8. Multilogging: The act of a singular person being on more than one account at the same time for an event.
9. Toxic Tactics: Also called inappropriate tactics, tactics conducted by an army that violate either war or Club Penguin Private Server rules.
10. Illicit Sponsorship: A sponsorship by a civil server that offers an unfair monopolization towards only a singular or specific selection of armies without means for others to be granted the same treatment.
11. Administration: The universal heads of Club Penguin Armies, consisting of Chief Executive Producers and Executive Producers.
12. Management: The heads of the Top Ten Committee (“managers”) are responsible for assisting the Administration.
13. Committee: In reference to the Top Ten Committee, the Club Penguin Armies department manages the Top Ten column.
14. Kingfunks4 Mos: The grandfathered original rule for deducting armies for mislabels and exaggerations was started by Club Penguin Army Central on February 22, 2015.
15. Sizaggeration: From English’s “size” (number of something) and Latin’s “aggero” (to increase), the exaggeration of an army’s size beyond a reasonable specific point.
16. Ban Evading: A member of an army that has been banned from an Army Server is found to be logging on with a different account.
17. Event: An army meetup in a CPPS, whether it aims to train the army, battle, or just have fun. It is usually planned, but there are also unscheduled events that happen on the spot.

§2.1. Events

What counts as an event and what does not?

1. In order for an event to count in the Top Ten, there must be at least two participating members. There must also be at least one tactic done, whether that is an emote tactic or a word tactic.
2. Meetups that are announced publicly to the entire server, whether there is a Discord ping included or not, count as events. This is up to the TT Managers and the Administration’s discretion, though.
   • Small training sessions that happen on the spot, in order to train a new troop, aren’t counted as an event.
   • Staff meetups on CPPS that aren’t announced publicly on the server also don’t count as an event. This is not the case if the meetup is a battle or an attempted raid against another army.
3. Meetups that are solely CPPS minigame tournaments, without having an army element – no tactics – don’t count as events. An army can do a tactic if it wants it to be included in the Top Ten.
4. Events that take place very close to each other (example: an army claiming it held two events within ten minutes) will be considered as one event. This does not apply to planned battles or to distinct raids.
5. If a mascot logs on during an event, the pre-mascot max will be counted. If an army wants to try for a new higher max, they have to switch rooms as soon as the mascot enters. Mascot room event pics will not be counted.
6. In order for a meetup to count as an event, it needs to be permitted by a Higher Command or Leader. If random troops, or even people not affiliated with the army, log on with the uniform and claim it is an event, the claim will not be deemed valid.

§2.2. Rogues

• A rogue uniform is the unofficial uniform of an army in a non-CPAB event. It must be made of a color + at least two items. Armies can choose whether to have a different one in each event or keep it the same per CPPS. They have the option to register one single item + color uniform, which they can then use in the CPPS. This item can’t be the item of a single-item historical army, or items that are already registered in other armies’ CPPS uniforms.
  • Administration and Management shall determine if a rogue uniform in a specific room may not be fair to judge on a case-by-case basis (i.e. Miner Helmet at the Iceberg or Inside Mine, or Pizza Apron at the Pizza Parlor). Armies may be required to show proof of movement outside of that room or other elements of participation.
• Rogues shall be allowed to be counted towards an army’s maximum size if they meet two out of four of the following requirements (with the exception of the 2&3 combination):
  1. Wearing that army’s rogue uniform. The uniform should be the same for all rogues, without colour or item variations. Rogues that deviate from it won’t fulfill this requirement.
  2. Followed an army to multiple rooms in relation to the other requirements (such as during Igloo Raids) and not spectators.
  3. Sitting in the army’s specific formation – the formation must be visible and not just a scatter.
  4. Doing the same emotes, or word tactics, as the rest of the army (excluding E1/E2 grin and smiles, EH hearts, and any emotes relating to a room, such as EC coffee in the Coffee Shop).
• Rogues who are later recruited to the army — either during the course of (or shortly thereafter) — the event shall be automatically counted regardless of the four aforementioned requirements, as rogues should be civil server players who are interested enough to be recruited as enlisted members.
• Although armies may start there to build up their members, maximum-size pictures for rogue events can never be taken in Town or spawn rooms due to their heavily crowded nature, even on smaller servers. Rooms such as Docks, Stadium, or inside rooms are usually recommended (although any outside of the proscribed ones may suffice). Rooms such as the Inside Mine, Iceberg, or party-specific, high-traffic rooms may also be disregarded for the maximum size picture and will default to the next closest. This shall be decided on a case-by-case basis depending on the activity in those rooms.
• Committee members for all civil server events are required to remark claimed maxes to verify the size, especially in the case of rogue events, to make sure they meet two of the three requirements.
  • Committee members are asked to provide a copy of their recounted markings in their assigned army’s thread for record-keeping purposes in case an army contests a recount.
  • Committee members should review all event pictures submitted by an army (ideally, an army provides a minimum of three, if possible) to make sure people are verified. They should also reach out to the leadership of an army or scour through an army’s event pictures channel.
• Armies that fail to produce enough documentation or proof for their claimed size in a rogue event by more than six people will be warned, with continued infractions leading to deductions for sizaggeration.
  • An event found guilty of sizaggeration post-warning will be deducted one point from its recounted size in line with the Kingfunks4 Mos.
  • Egregious claims (more than ten) and a history of sizaggeration may lead to further point deductions or a 0.8 multiplier. Sizaggeration of more than thirty may result in even harsher punishments.
• Administration and Management may determine on a case-by-case basis if an army’s rogue event is valid, and these regulations are not absolute, functioning as formal guidelines. Committee members and army leaders alike are expected to follow this to the letter, with Administration and Management making the final call if necessary. Army leaders may appeal any decisions to them, including submitting further proof, if necessary, although they reserve the right to determine if valid.

§2.3. Sponsorships

1. In the aftermath of the CPForever controversy, as well as past history of Club Penguin Online favoritism towards armies, events on civil servers will not be recognized on the Top Ten if an army’s event benefits from the following means:
   • Publicly announced and/or encouraged by the administration of the civil server;
   • Hosted or led within the Discord of the civil server;
   • Benefits from an in-game mechanism to artificially inflate their size with a rogue uniform (such as an in-game event hosting feature); or
   • Offer any exclusive in-game benefit, such as coins, items, codes, Discord Nitro, spawned mascots, or other forms of in-game currencies, such as Robux or VBucks, for just the attendees of that army.
   • Administration and Management shall have the right to review loopholes and future cases. Loopholing will result in the civil server in question being banned from being considered for events for a period of time.
2. Sponsorships are encouraged, however, and may be greenlit if the following are done:
   • The sponsorship stops short of special custom items, spawned mascots, and led or promoted in the Discord for an army;
   • The benefits do not differentiate for armies due to legacy, size, or status;
   • The benefits are offered to all armies, regardless of legacy, size, or status, who request and meet that civil server’s requirements; and
   • Have a public open-door policy for applying for said benefits (meaning a civil server can’t have a non-public application process for armies close to their staff, like in regards to the SuperCPPS and NewCP Doritos controversy in 2020 and 2024, respectively).
   • Administration and Management shall have the right to review if a sponsorship policy by a civil server is fair, and may negotiate with them on behalf of the organization’s participating armies on a uniform standard for all armies, regardless of relationship to Club Penguin Armies.
3. Sponsorships for language-specific civil services must still follow these regulations to have events on their civil server to be counted. They may, however, exclude armies that are language-centric to their community or have a language-specific division (Club Penguin Avalanche controversy). That still does not mean it can offer benefits beyond the aforementioned regulation, though.

§2.4. Multilogging and Botting

1. Any multilogging – unless permissible by the administration (See Multilog Mayhem 2026) – is prohibited and will be met with deductions.
2. Any and every additional penguin will be deducted from the event’s max size (e.g. If an army claims a max of 35 with 4 alt accounts, handled by one multilogger, it will be initially reduced to 30).
   • In the event of excessive multilogging, a harsher punishment in addition to the primary deduction might be applicable. Administration and Management can decide on a case-by-case deduction. These decisions take into consideration several aspects of the multilogging incident. These include the rank of the involved person, the longevity, the number of multilogged accounts, and more.
3. If multilogging is found – such as 2 or more accounts on the same IP address noted by the CPAB Bot – the Administration will reach out to the army’s leaders to allow them to present their case and provide evidence against the accusation. The evidence can be in the form of:
   • Non-doxxing photos (a thumbs-up photo) of the parties involved and the individual devices that were used for the accounts. The photos would have to prove the existence of the number of people on the same IP address and match the number of devices.

§2.5. General Deductions and Behavior

1. Additional deductions can occur in any of the following instances.
   • An army has been found to fake events (claiming a higher number of events than the ones actually hosted, in order to boost their overall score).
   • An army has been found hiding events.
   • An army has performed toxic tactics, especially against another army. This can happen either during a battle, a raid, or a solo event in which a tactic is aimed at another army.
     • In this instance, the Administration will conduct an investigation. The punishment may vary, depending on the severity of the offense. Whilst the Managers will likely be informed and possibly consulted on the matter, the decision on the severity of the punishment is ultimately up to the Administration.
   • A member of the army has been found to be ban-evading.
   • The army has been involved in unsavory/inappropriate situations that are not revolved around events, such as scandals. The Administration will once again conduct an investigation prior to any decision, and the severity and duration of the deduction will be based on their judgement.
2. All instances will be met with a deduction, but in the event of repeat offenses and offenders, further punishments might be enforced, such as multipliers.

§2.6. Committee and Leader Expectations

1. The Top Ten Committee is responsible for verifying the number of events an army has had, the type of event, and the maximum size for each event.
   • The Management is also responsible for this, as well as supervising the Committee’s work, and conducting further investigation into any misconduct mentioned above.
   • The Administration aids in the aforementioned part, and they are responsible for the calculations, since they are not affiliated with any army.
2. Every week, armies are assigned to individual Top Ten Committee members, and they are responsible for those armies. It is noted that people are not allowed to work on armies that are affiliated with/enlisted in.
3. The Top Ten Committee is expected to provide the relevant information regarding their armies’ events by a set deadline, so the Top Ten Post can be completed promptly. However, leniency is applied if an army fails to submit by the time of their deadline, and also when taking someone’s timezone into consideration.
   • An effort is made to assign armies to people who submit closer to their timezones, however, it is not always possible to predict perfectly.
4. If a maximum size needs to be verified (primarily when it comes to rogue events), Committee members will be using the same requirements that are stated in Section 2.1 of this document. In order to do so, they are expected to:
   • Cross-reference with event pictures to locate people of interest doing tactics, being in form, etc., to then verify them.
   • Reach out to an army leader about any people who cannot be verified by event pictures.
5. Committee members are also to get in touch with an Army Leader if said leader has not submitted their army’s events for the week.
6. Army Leaders are expected to submit their events the latest by Saturday at 10:00 pm Eastern Time. They are encouraged to start submitting from Friday, since assignments are distributed on Fridays.
   • Armies that do not submit by the deadline (Saturday, 10:00 pm EST) will receive a warning for hiding events for the first offense. Any second, third, or more offenses will result in a penalty (decided by both Top Ten heads and admins).
   • If an army did not host an event that week, the army must state so in the #event-results channel.
   • Armies that host events on the Club Penguin Journey are required to use the “;” key feature that hides the UI. This helps the Top Ten Committee verify penguins near the chatbar more easily. Failure to use this feature in the submitted event pics may result in penguins covered by the chatbar not being counted.
   • At the same time, events that are not in CPAB should contain several event pics, rather than one, to help with verifying rogues. Ideally, armies should make website posts for their events.
   • Exceptions to the deadline can be granted if an army has an event after 9:00 pm Eastern Time. In that case, the events should be submitted at 12:30 am Eastern Time at the latest.
   • If all army leaders of an army are unable to post the event results on time, they can request that CPA grant permissions to an HCOM or Advisor of their choice, so that they can submit them.
7. Leaders must also submit their events in a comprehensible and thorough form.
   • A link to an event post on their website.
   • Event pictures sent in the #event-results channel, with a message including:
     1. The Title of the Event, if applicable
     2. The Region (EU/US, or AUSIA)
     3. Whether the event was a battle/tournament/raid/solo event
     4. The maximum size (and event pics if it is a non-CPAB event)
        • Note: If an army chooses this form of submission, each event must be submitted in its own individual message.
   • Regardless of the form of submission, the leaders must provide tactic pics from the event alongside the max picture, so rogues can be verified. If the event pictures are not sufficient to verify everyone, a Committee member will reach out, but the process gets slowed down naturally.
   • Maximum size pictures that are taken during a CPPS-wide event — mascots, parties, etc. — that are submitted will be nullified and not be counted towards size and event points for that respective week. If a mascot logs on to the same room during an army’s event, only pics taken before that will be counted.