Joining a Tournament
- Register
- Sign In
- Sign Up under "Preregister for Events"
- Join #tournament-room on Discord
- Wait for announcements from the Tournament Organizer
- Matches will be played in Constructed, Specialty, Freeform Tournament Practice room
Number of Rounds
|
Rounds |
|
| Players |
Swiss |
Knockout |
|
| 2 |
0 |
1 |
(single match) |
| 3-7 |
3 |
0 |
(swiss only) |
| 8 |
3 |
2 |
(top 4) |
| 9-15 |
4 |
2 |
|
| 16-31 |
4 |
3 |
(top 8) |
| 32+ |
5 |
3 |
|
Priser
Loading…
| Finish |
Prize |
| 1st |
4 tix |
| 2nd |
3 tix |
| 3rd |
2 tix |
| 4th |
2 tix |
| 5th |
1 tix |
| 6th |
1 tix |
| 7th |
1 tix |
| 8th |
1 tix |
Prizes from our sponsor Cardhoarder in credit. Prizes will be credited within a few days of the Friday following the tournament. After that the credit will appear when you trade with one of their bots on Magic Online and on their website.
Vi tillåter folk att spela med buggar som vi känner till i Penny Dreadful med vissa kriterier.
The important rules are:
- Do not play cards with game-breaking bugs (exception: cards that are only bugged in multiplayer games).
- Gaining advantage from a bug unintentionally will result in a game loss. The player with the bugged card should concede the game and begin the next one (if any).
- Gaining advantage from a bug intentionally will result in disqualification.
- Your opponents have no obligation to accomodate your bugged cards and cannot be penalized for not doing so.
- The Tournament Organizer's decision is final.
Note for examples: Living Lore used to have a bug whereby it would count double the (combined) CMC of a split card when imprinted.
Example of Game Loss: Playing Living Lore with two cards in graveyard and opponent removes one at instant speed with a card from their hand forcing the Living Lore player to imprint a split card.
Second example of Game Loss: Playing Profane Command using the mode that targets an opponent. Opponent plays Gilded Light in response.
Example of Disqualification: Playing Living Lore and intentionally choosing a split card from a stocked graveyard to get an oversized Living Lore.
In the case where a bugged interaction only becomes known to a player during a competitive match, at the Tournament Organizer's discretion, a game loss or match loss may be imposed rather than a disqualification.
The game loss should be enacted by the bugged cards controller conceding the game.
Any confusion should be discussed with the Tournament Organizer before conceding the game or ending the match, on the bugged card player's clock.
When a new bug is encountered for the first time (does not appear at pennydreadfulmagic.com/bugs) during a competitive match both players may agree to play on.
If either player does not agree the owner of the bugged cards must swap out the bugged cards (only) from their decklist, restart the match, players concede games in the correct order until the record matches the record before the bugged game. Sideboarding then takes place if it was not game 1 and the rest of the match plays out.
For all these matters the Tournament Organizer has the flexibility to rule as they see fit and their decision is final.
List of all known bugged cards
Other Notes
If a player starts a sideboarded game with less than 60 cards (quite possible due to a known Magic Online bug) and either player notices before the end of turn 2 and either player wants to restart the game, the game will be restarted. The result of any game played beyond turn 2 with less than 60 cards in maindeck will stand.
Matches should use 25 minute timers.
A player may not play games under more than one account in a Penny Dreadful tournament.
Please do not double queue Penny Dreadful tournaments with other tournaments nor double queue in the league.
Only players completing the tournament will be awarded prizes.
Because of a bug removing all stops is not allowed.
You may only enter a given tournament once (either on the same account or multiple accounts).
Penny Dreadful tournaments follow official Magic Online tournament rules and do not allow draws, unlike some other player-run events.
