PLANESCULPTORS.NET

Tutorials

1. Formatting text content
2. Search reference
3. How to import sets into PlaneSculptors

Formatting text content

Most input where you enter a block of text, such as set description or user profile page content can be formatted using an extended Markdown syntax. This tutorial will introduce you to Markdown and descibe of all the extensions provided by WebDrafter.

Introduction to Markdown

Markdown is a markup language used to format text on websites like Reddit and GitHub. You can see a quick "cheat sheet" below. For more advanced guide see Mastering Markdown. In addition to standard Markdown, WebDrafter also supports GitHub-style tables (see example below).

# Heading level 1
## Heading level 2
### Heading level 3

*Italic text*
**Bold text**
~~Strikethrough~~

* Unordered list item
* Unordered list item
* Unordered list item

1. Ordered list item
2. Ordered list item
3. Ordered list item

[Link title](http://www.google.com)
![Image title](http://www.github.com/images/logo.png)

First Header | Second Header | Third header
------------ | ------------- | ------------
Content from cell 1 | Content from cell 2 | Content from cell 3
Content from cell 4 | Content from cell 5 | Content from cell 6

Magic symbols

These are all the Magic: the Gathering symbols that you can use in text. The symbols will correspond in size to currrent font size (for example, if you include a symbol in a heading, it will be enlarged appropriately).

[C]

[W]

[bW]

[1]

[T]

[UT]

[Q]

[WU]

[2W]

[PW]

[P]

[S]

[CHAOS]

Most input where you enter a block of text, such as set description or user profile page content can be formatted using an extended Markdown syntax. This tutorial will introduce you to Markdown and descibe of all the extensions provided by WebDrafter.

Introduction to Markdown

Referencing cards

Unlike on traditional Magic: the Gathering message boards, many sets can contain different cards with the same name. Additionally, each set can exist in multiple versions. Because of this, the syntax used to reference cards on WebDrafter is slightly more complicated. Card refernce will be transformed into a hyperlink leading to that card's page, and will also display image of that card when the user hover with his mouse cursor over the link.

The most basic syntax is this:

[[Lightning Bolt]]

This only works when used in a context where it is completely obvious, which set the piece of text content relates to - on set page (the lastest version of the card will be referenced) or on set version (the card fom that version will be referenced).

You can also specify to which set the card belongs to using that set's URL name (applies for set with URL https://www.planesculptors.net/set/modern-masters-2015):

[[modern-masters-2015:Lightning Bolt]]

This will always reference the newest version of the card.

Next step is to specify which version of the card is referenced, by adding that version's URL name (considering version with URL https://www.planesculptors.net/set/modern-masters-2015/version-3):

[[modern-masters-2015:version-3:Lightning Bolt]]

You can also specify text of the link, without affecting which card that link points to using the pipe symbol (works in combination with any of the above):

I love [[modern-masters-2015:version-3:Lightning Bolt|bolting]] my opponents!

If you want to include an image of the card, instead of a link, you can add an exclamation mark symbol before the initial [[ (also works with any of the above notations):

![[modern-masters-2015:version-3:Lightning Bolt]]

Additionally, you can set the image to align left or right:

!l[[modern-masters-2015:version-3:Lightning Bolt]]

!r[[modern-masters-2015:version-3:Lightning Bolt]]

Either of these will also make text flow nicely around the card image (if you don't specify alignment, the image will be placed inline into the text).

Font Awesome

Font Awesome is publically available library of hundreds of symbolic icons for web applications. You can use any of these icons using following syntax, where fa-thumbs-up is name of the icon:

[fa-thumbs-up]

Which will result in this: . All icons from all FA versions up to 4.4.0 are supported. As with the Magic symbols, all of these will scale with current size of the text. :) and :( will be transformed into appropriate Font Awesome emotes even without the explicit syntax.

Inline HTML

You can use HTML arbitrarily in combination with any other syntax offered by WebDrafter, with inline CSS being allowed as well. With HTML, you can achieve many things that the simple markup syntax wouldn't allow you to. Please take care not to interfere with layout of the website, otherwise yoru content will be taken down.

Page source code

You can view the source code of any user-submitted formatted text on any page (user profile, set page etc.) by adding "?source" to the URL of that page, for example https://www.planesculptors.net/set/modern-masters-2015/version-3. If that page specifies a hash fagment (#detail), always add the source parameter before it.

Search reference

This section describes how to use the "Explore cards" field.

The simple "language" used to search the card database is based on the query language used by magiccards.info and Scryfall. As a quick comparison to Scryfall (which has slightly more feature that magiccards.info), these are the main differences:

• Features that don't make much sense in relation to custom cards, such as blocks, formats, borders, nicknames, reprints, "funny" etc. are not available.
• OR operator is not available (this will hopefully be improved in the future).
• Several other minor features are not available, such as planeswalker loyalty, color identity, ~ etc.
• You can search using card author, upload date and set status.

Basics

The search query is composed from terms that are separated by spaces. Each term may include a keyword, such as color: which determinews what attribute of the card the term applies to. If the keyword is not provided, the term will apply to the card's name, types and rules text. These terms are never case sensitive. Unless specified otherwise, all terms must be matched for the card to match the query.

• legend (cards that include "legend" in their name, types or rules text)
• bolt color:red (red cards that include "bolt" in their name, types or rules text)

Terms that include spaces need to be wrapped in double quotes (otherwise they will be considered multiple terms):

• "deals 3 damage to target creature" (cards that say "deals 3 damage to target creature" in their name, types or rules text. If this term wasn't wrapped in quotes, it would also find cards that say for example "deals 3 damage to target player. Creatures you control gain trample until end of turn.")

! operator can be used either as prefix (exact name match) or infix (exact attribute match):

• !"lightning bolt" (cards named exactly "lightning bolt")
• color!redblack (cards that are both red and black and no other colors)

With some keywords that represent numeric attributes such as "toughness", you can also use numeric comparison operators <, <=, > and >=. You can generally use operator = instead of : (they are treated identically). With most keywords, you can use the != meaning "not equals to".

Negating terms

Prefixing a term with - will match all cards that DO NOT match the term:

Colors

You can find cards that include a particular color using c: or color: followed by a full color name or a single letter. colorless or c and multicolor or m are also supported.

This color includes all the colors in the mana cost if not specified explicitly by a color indicator (in which case the color is determined by the color indicator).

Examples:

• c:rg (cards that are both red and green)
• c!rug (exactly temur creatures)
• c:bluewhite (cards that are both blue and white)
• c:mu (multicolored cards that include blue)
• t:warrior c:r -c:g (red warriors that are not green)

Order of colors doesn't matter, even when the exact match operator (!) is used.

Card types

You can use t: or types: followed by a string to find cards including particular type (or types) on their type line. If you use a string with multiple words, these words have to appear on the card in the exact order in which they are on the card.

Examples:

• t:farie (cards that include "faerie" on their type line)
• t:"legendary creature" (cards that include "legendary artifact" on their type line, but doesn't match "legendary artifact creature")
• t:"creature legendary" (doesn't find any cards - "legendary" always comes before "creature" on the type line)
• t:creature t:legendary (cards that include both "creature" and "legendary" somewhere on their type line, so it matches "legendary artifact creature" unlike the examples above)

There are also shortcut classification terms is:spell and is:permanent that match the appropriate card types. is:token also works.

Rules text

You can use o: or oracle: or rules: or text: or rt: followed by a string to find cards including that string in their rules text.

Examples:

• text:"you win the game" (cards that say "you win the game" in their rules text)
• o:draw type:creature (creatures that deal with drawing cards)
• o! type:creature -type:token (completely vanilla nontoken creatures)

There is also a shortcut term is:etb for cards that include "enters the battlefield" in their rules text.

Note that automatic replacement of "~" with the card's name is not supported.

Mana costs

You can use m: or mana: followed by a mana cost to find cards that include specific string in their mana cost. There are three different ways to enter mana costs:

• "Naked" syntax - eg. 5GG. Hybrid mana symbols can't be entered this way.
• PlaneSculptors syntax with square brackets - eg. [5][G][G]. Hydrid mana symbols are entered as [2U][RG]. Phyrexian mana costs are entered as [PW]. For more information see the formatting syntax reference above.
• Scryfall syntax with curly brackets - eg. {5}{G}{G}. Hydrid mana symbols are entered as {2/U}{R/G}. Phyrexian mana costs are entered as {W/P}.

These syntaxes can be liberally combined even in a single term.

Order of the symbols matters.

Examples:

• m:2[2U] (cards that have a followed by a   in their mana cost)
• m!WW (cards that cost exactly )

You can also use cmc: to find cards with specified mana costs. Arithmetic comparison operators are supported.

• c:u cmc:2 type:creature (mono-blue two-drop creatures)
• cmc>7 is:spell (spells that cost more than 7 mana)

Power and toughness

You can use pow: or power: and tou: or toughness: to find cards with specific mana costs. Arithmetic comparison operators are supported. You can also compare power and toughness to each other (but not to other attributes).

Examples:

• cmc<3 pow>3 (cards that have power greater than 3 but cost less than 3 mana)
• color:black toughness>power (black cards that have toughness greater than power)

Multi-faced cards

Generally, at least one of a multifaced card's faces must match the search criteria to show up in search results.

You can query card's "shape" using the is: keyword:

• is:normal (normal single faced cards)
• is:dfc or is:transform (double faced cards)
• is:split (split cards including fuse cards)
• is:flip (flip cards)

Rarity

You can use r: or rarity: to find cards with specific rarity. Use either full name ("common", "uncommon", "rare", "mythic" or "special") or a single letter shorthand:

Examples:

• r:m c:r t:dragon (mythic red dragons)
• r:c c:blue is:spell text:"draw a card" (common blue cantrips)

Sets, set statuses and authors

You can use s: or set: or e: or edition: to find cards from specific sets. To specify a set, you can use either a part of its name, part of its URL name or a part of its code.

You can also chain multiple sets using | or , (cards that appeared in at least one of the chained sets).

Examples:

• s:aenyr c:g cmc:2 (green two drops from Aenyr)
• s:aenyr|dreamscape (card that appeared either in Aenyr or in Dreamscape)

You can use st: or status: to find cards from sets that are in specified status. Valid values are "unplayable"/"un", "design", "development"/"dev", "finishing" and "finished"/"done". You can use arithmetic comparison operators with these values.

Discontinued sets are not matched unless you specifically ask for them with st:discontinued or st:dis.

Additionally, you can use st:play or st:playable to find cards from sets that are not in statuses "unplayable and "discontinued".

• st:finished r:m (all mythics from finished sets)

You can use au: or author: to find cards from sets made by specific author. The author can be specified using either their user name or their URL name:

• r:c au:matej-zabsky (all commons made by me)

Artist and rules text

You can use a: or art: or artist: to find cards with art by specific artists (as specified in the card's footer):

• art:"Noah Bradley" t:land (all lands illustrated by Noah Bradley)

You can also use f: or ft: or flavor: to find cards with specific string in their flavor text:

• flavor:"Keiaraq" (all cards with "Keiaraq" in their flavor text)
• flavor! (all cards without a flavor text)

Unrolling searches, upload dates

By default, only cards from the newest version of each set are searched. However, unlike in Scryfall, a card can be matched multiple times if it appears in multiple sets (even if it is exactly the same).

You can unroll the search by prefixing it with ++, which will cause all versions of all cards to be searched.

• ++!"Deepmind Mori" (all versions of a card named "Deepmind Mori")

You can also restrict the cards matched by date when they were uploaded to the site using date: keyword. You should use arithmetic comparison operators with date (exact matches make little sense). Note that if you use this keyword without unrolling the search using ++, only cards from sets that were last updated during matching time interval will be matched.

Date can be specified either in "YYYY-MM-DD" format or intuitively such as "yesterday", "-3weeks" (for details see strtotime PHP function). Note that if you specify a date this way, the exact moment specified is 00:00 of that day.

• ++date>-1week (all cards uploaded in last 7 days)

For technical reasons, only versions of cards uploaded after 29th September of 2016 are searched (images from set versions older than that are stored off-site and are mostly broken).

How to import sets into PlaneSculptors