Badge time.png   The Paragon Wiki Archive documents the state of City of Heroes/Villains as it existed on December 1, 2012.

User:Mythobeast

From Paragon Wiki Archive
Jump to: navigation, search

I am a long-term player of CoH, having started playing about a month after the game was released. My primary toon is Mythological Beast, on the Villain side of Infinity server. Along with Miss Anthropy and General Fear, I am a founding leader of the Evil Geniuses for a Better Tomorrow villain supergroup.

As of May of 2008, I am involved in an attempt to create a Base Raid PvP League with other leaders on Infinity server. I figure that this is a good place to allow them to work on the rules for the league in a wiki manner.

Infinity Raid League Rules

Spawn Camping

No Spawn Camping – Once the zone point is identified for the attacking team, the defending team cannot have any active powers that negatively effect the attacking team in the spawn square. This includes tar patch, caltrops, slow fields, bubbles, lightning storms, hurricane, blaze, pets, etc…..

The attacking team cannot be attacked as long as they remain in the spawn point and refrain from using powers that negatively effect the defending team, their base defenses or critical infrastructure. (defined as generators, med bays, and anchors.)

Once a member of the attacking team moves from the spawn point or uses their powers to negatively effect (powers that negatively effect the attacking team are defined as: ranged attacks, melee attacks, debuffs, pets, minions, etc…) the defending team, their base defenses, or their critical infrastructure, that individual attacker is fair game. The spawn point is not “safe”, meaning that an attacker cannot leave the spawn point, fire on a defender, then return to the spawn point and expect attacks against him to stop. Returning to the spawn point after being engaged risks having AOE blasts or debuffs effect your attacking teammates. Don’t do it!

Planting a pylon in the spawn point voids all rules as long as the pylon exists. The defending team can take any measure necessary to destroy a pylon in the spawn point, likely resulting in long lasting debuffs to that location. Don’t do it!

A zero tolerance rule against spawn camping is impossible to enforce. From time to time, [censored] happens. As long as both teams make a good faith effort to enforce these rules, there is no problem. There will be occasional lapses and these are to be expected. However, repeated, long term lapses likely reveal a lack of respect for the rules. For example, early in a match, the defending team may drop a lightning storm within range of the spawn point. As long as they apologize and it doesn’t happen again for the rest of the match, there are no worries. However, if the defending team repeatedly (3+) drops lightning storms within range of the spawn point (and apologizes each time) throughout the match, they clearly weren’t making a good faith effort to avoid spawn camping.

Camping the defender’s base portal is also ILLEGAL.

Pits and Pit Traps

No Pits or Pit Traps in potential spawn points (doorways). This violates the spirit of the “No Spawn Camping” rule. A slow field in a pit will keep many from leaping out of the spawn point – this isn’t any fun. Pits with slow fields or other debuffs are allowed in larger rooms, just not in doorways.

Team Sizes

Minimum players for a team to Raid is 10 and all teams must fight within +/- 2 combatants. Meaning that larger teams may have to bench players against smaller teams. Captains will coordinate expected turnouts in a advance to the greatest extent possible to minimize benching people. However, we’re all here to have fun. If a teams shows up with 8 (for example) because 3 or 4 couldn’t make it for real life reasons, they are permitted to fight. In this eventuality, the minimum for raids is 10, meaning the opposing team could bring up to 12 combatants.

Editor Hacking

Using the Base Editor to render critical infrastructure (defined as generators, med bays, and anchors) impossible to attack is not acceptable and can result in a disqualification. A base that’s impossible to defeat isn’t fun. If you cheat like this, no one will raid you.

Leadership Council

Infinity Base Raid Leadership Council: Consists of the leaders of the groups involved in the Infinity Base Raid Ladder. The leadership council will only be involved in cases of persistent, pervasive anti-social behavior by a group – meaning LOTS of anti-social trash talking or spawn camping over MULTIPLE matches. Sanctions would be imposed on that group by a SUPER MAJORITY of the other captains. In other words, what the group has done must be *really bad* and *most* of the other captains want to impose sanctions.

Rosters

Groups will submit rosters in advance. Additions to this roster come with a two week waiting period before they’re eligible for combat. This two week period begins from the day the addition is posted to the public COX boards.

Teams must identify a leader who speaks for them on the Infinity Base Raid Leadership Council and the forums (global and forum handle). Raid day POC’s must also be identified (globals). Finally, all potential combatants must be identified (globals). Players may only participate on one team – period.

Unsportsmanlike Conduct

The Infinity Base Raid Ladder expects all combatants to comport themselves as mature adults and behave in a sportsman like manner. There is no place for the hated zone or Arena chat style BS. Anything that breeds hostility and bad blood should be avoided as that will only serve to further alienate the already sparse competition we already have. Obviously, as with spawn camping, some level of trash talk is to be expected. “Witty banter” should not be construed as trash talk -- people should do their best to treat each other with respect and recognize that this is a competition and not take what they read personally. Teams who do have members likely to take any level of trash talk personally are encouraged to have those members disable their broadcast and local channels.

Base Jails

Base Jails are not allowed since /stuck does not work successfully all the time.

Character Restrictions

There are no level caps and no restrictions on AT’s or powersets.

Power Restrictions

Temporary powers are legal, including all the pvp zone temp powers.

Scoring Kill Counts

Kill counts are irrelevant and will be ignored

Victory Conditions and Results

This is a LADDER, not a LEAGUE -- If team A wins on both attack and defense, team A wins. -- If team A wins their attack via dropping pylons, and team B wins their attack by any other means, team B wins. -- If both team A and B win on attack by dropping pylons, or both groups win by a means other than dropping pylons, then the team that won in the shortest period of time wins. If both teams manage to do it in exactly the same amount of time, we can call that a draw. -- If each team successfully defends their base, then nothing happens. The higher ranked team has successfully defended their ladder ranking and nothing changes.

Challenge Conditions

Teams may challenge two rungs above themselves and accept challenges from two rungs below themselves. Teams new to the ladder will be added at the bottom and may challenge up to two rungs above themselves. Matches must be completed within 10 calendar days.

Badges

Badge Year 10 Veteran.png Who's Counting?

It's been at least ten years since your first edit at Paragon Wiki, and, like fine vintage items, any more anniversaries are just numbers. This'll do.

Badge anniversary 2.png Documenter

Your efforts at documenting the contents of City of Heroes are greatly appreciated. (Awarded to everyone who made an edit in the year prior to September 1, 2007.)

Badge anniversary 3.png Gatherer

You've gathered more bits and bytes, and added them to Paragon Wiki. (Awarded to everyone who made an edit in the year prior to September 1, 2008.)

Badge anniversary 4.png Transition Maker

You've helped welcome Paragon Wiki to its new home by adding more information about City of Heroes. (Awarded to everyone who made an edit in the year prior to September 1, 2009.)

Badge anniversary 5.png Data Hound

You've left no stone unturned in the search for more content to add to Paragon Wiki. (Awarded to everyone who made an edit in the year prior to September 1, 2010.)

Badge anniversary 7.png Knowledgebase

With your help, Paragon Wiki has become an even more expansive repository of knowledge. (Awarded to everyone who made an edit in the year prior to September 1, 2012.)