Help:Myth-Weavers bbCodes

From Myth-Wiki
Revision as of 02:58, 30 March 2009 by Rodrigo (Talk | contribs)

(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search



Private Text

Private Text is a feature that allows you to type a hidden message inside a post and to specify one or more users that will be able to see this message. Note that GMs are able to see all private text in their games.

Here's how it works for a single recipient.

[private=username]Your private message, which may include anything from text to hyperlinks, images, dice rolls - anything you can place in a post regularly will only be seen by the specified users![/private]

Adding more recipients is easy!

[private=username;username2;username3]By placing a semicolon [;] with no space between each name, you can allow as many people as you wish to view your secret message.[/private]

Note that in this situation usernames are not case sensitive, but proper spelling is still essential.

In case you don't want to type the whole tags every time you use the Private Text, you can use the following icon (only located above advanced post area):

Even though Private Text is un-readable by people other than its recipients, you might tip off onlookers to the presence of Private Text by un-savvy formatting. Here are some tips on how to ensure that nobody knows you're placing Private Text in your posts:

  • Don't make a post with only secret text because everybody would see a blank post, leading to the obvious conclusion that you're hiding private text there.
  • Don't make a line break (by pressing enter to skip to the next line) before and after your private text tags. The formatting takes care of that for you, and the extra blank lines are give-aways.
  • Make sure you type the tags correctly and preview your post before submitting it. Incorrectly typing the tag syntax might cause you to accidentally reveal everything, so be careful and preview often!

OOC Tags

OOC Tags

OOC Tags (Out Of Character Tags) are available to help players and GMs to add pop-up OOC comments and other messages into their posts without disrupting the flow of the game. If you are one of those people like clean game posts, then this feature was created for you.

What does it do? OOC Tags work in a similar way as Roll Tags in that they enable you to attach a message to text in form of a pop-up box.

How can it be done? The structure of the OOC command is as follows:

[ooc=Text]OOC message[/ooc]

  • ooc – An OOC Tag consists of an opening tag placed in front of your OOC text and closing tags (which always include a slash) placed after it.
    • Note: There may not be any spaces between the tags and dice roll nor breakers in the word ooc
  • Text – This is where you enter the text that will be visible in the main body of your post. It will allow linking to the popup OOC message, as shown in the screenshot below.
  • OOC message – Here is where you type in your message that will be available as a popup for GMs and other players to see.
    • The OOC message can include more than just text -- images, dice rolls, and other sorts of formatting can be used.

Let’s take a look at an example:

John smiles at the peaceful troll named [ooc=Bob]Hey, you really like using this name in your games, right?[/ooc] and lowers his sword.

In post, the above will take this form:

To see the OOC message, all you need to do is hover your mouse over the underlined (linked) text.

Rules Data Tags

Rules data tags are a simple way of including information about a particular game rule directly into your posts. Right now, the data tags support information from the D&D 3.5 System Reference Document, particularly about monsters, spells, conditions, and psionic powers. This information can be added to your post directly, as a popup, or in a spoiler block.

How they Work - Summary

A data tag just needs the type of game info and the name of a particular thing to find what you want. If a name doesn't match anything, the tag will supply some suggestions to help find what you're looking for.

[srd=Type]Thing Name[/srd]

The types we currently support are: monster, monsterlong, spell, power, item, feat, skill, condition, ability, and attack. Monsterlong is like monster, except that it includes an explanation of a monster's special abilities in addition to the basic statistics. Attack is for the special attacks, such as Charge, Bull Rush, etc. For the purpose of simplifying the types, Delay and Ready actions are also included in attack. Ability is for special abilities, such as Rake, Improved Grab, Spell Immunity, etc.

Example: You Type[srd=feat]Cleave[/srd]

You Get

Cleave [General]

Prerequisites: Str 13, Power Attack.

Benefit: If you deal a creature enough damage to make it drop (typically by dropping it to below 0 hit points or killing it), you get an immediate, extra melee attack against another creature within reach. You cannot take a 5-foot step before making this extra attack. The extra attack is with the same weapon and at the same bonus as the attack that dropped the previous creature. You can use this ability once per round.

Special: A fighter may select Cleave as one of his fighter bonus feats.

Additional Display Options

You can also choose different ways of displaying the game rule data in your post. You can accomplish this by adding ;ooc or ;sp after the name part of your tag.

[srd=Type;Option]Thing Name[/srd]

OOC makes the data a popup that only appears when one puts the cursor over the name of the data.

Example: [srd=item;ooc]jumping[/srd] produces...

Jumping: This ring continually allows the wearer to leap about, providing a +5 competence bonus on all his Jump checks.

Faint transmutation; CL 2nd; Forge Ring, creator must have 5 ranks in the Jump skill; Price 2,500 gp. jumping

SP puts the data into a spoiler block that can be expanded or collapsed.

Example: [srd=item;sp]jumping[/srd] produces...

Jumping: This ring continually allows the wearer to leap about, providing a +5 competence bonus on all his Jump checks.

Faint transmutation; CL 2nd; Forge Ring, creator must have 5 ranks in the Jump skill; Price 2,500 gp.

Full List of Examples:

  • [srd=monster]mimic[/srd]
    Output Mimic; CR 4; Large aberration (shapechanger); HD 7d8+21; hp 52; Init +1; Spd 10 ft. (2 squares); AC 15 (-1 size, +1 dex, +5 natural), touch 10, flat-footed 15; Base Atk +5; Grp +13; Atk +9 melee (1d8+4, slam); Full Atk +9 melee (1d8+4, 2 slams); Space/Reach 10 ft./10 ft.; SA Adhesive, crush; SQ Darkvision 60 ft., immunity to acid, mimic shape; AL N; SV Fort +5, Ref +5, Will +6; Str 19, Dex 12, Con 17, Int 10, Wis 13, Cha 10 Skills and Feats: Climb +9, Disguise +13, Listen +8, Spot +8; Alertness, Lightning Reflexes, Weapon Focus (slam)[/
  • [srd=monsterlong]mimic[/srd]
  • [srd=spell]light[/srd]
  • [srd=power]conceal thoughts[/srd]
  • [srd=item]jumping[/srd]
  • [srd=feat]Cleave[/srd]
  • [srd=skill]Appraise[/srd]
  • [srd=condition]prone[/srd]
  • [srd=ability]Fast Healing[/srd]
  • [srd=attack]Aid Another[/srd]


Tables are useful for organizing information that looks funny as a list or is just too unwieldy to explain in pure text. They're also particularly handy for describing rules-mechanics like classes.

At Myth-Weavers, you can make tables by using two types of tags -- "Table" tags and "R" tags. Here's how to build a table outline.

[table=Number of Columns,Number of Rows;List-Numbering] Your "R" Tags [/table]

  • [table=] [/table] -- These main tags must be included at the start and end of every table.
  • Number of Columns -- This is where you decide how many columns your table will have by putting in that number here. Whole numbers (integers) only.
  • Number of Rows -- This is where you decide how many rows your table will have. Again, just insert that number here.
  •  ;List Numbering -- This part is optional. If you insert ";1" here, the first column of every row except the first will be numbered. If you select this option, you do not need to fill in those cells. This is like a numbered list, as it goes 1...2...3... etc.
  • Your "R" Tags -- This is where you will be using "R" tags to fill in the contents of the table. The "R" tags are described below.

Now, on to the "R" tags themselves. The "R" tags are used to describe each of the cells in the table. Each "R" tag fills in exactly one cell of the table. You pick what cell is being filled in by specifying which column and row the "r" tag is targeting.

[R=Column Number,Row Number] Content of the Cell

  • [R= ... ] -- This tag must be included at the start of each cell-description. No end-tags are needed.
  • Column Number -- The column number of the cell you want to fill in.
  • Row Number -- The row number of the cell you want to fill in.
  • Content of the Cell -- This is where you get to actually fill in what this cell in the table says. You can put any text, tags, and so forth into this part except another table. How much you put in here determines the size of the cell.

As mentioned above, no "end tag" (such as [/R]) is necessary. To fill more than one cell, just add another "R" tag using the same syntax, but a different column and row number. You can only have as many "R" tags as there are cells in your table (i.e. the number of columns times the number of rows). The "R" tags do not have to be in any particular order, but they must be in-between the [table] and the [/table] tags.

Special Note: Because this feature is still in development, you can only insert one table per post. When the tags are absolutely complete, this limitation will be removed. Furthermore, tables are not functional in user signatures.


Sample Table A This table is very small and simple, resembling a list.

The Code (What you type)

[table=1,2] [R=1,1] This is the content of the cell in the first column and the first row of the table. [R=1,2] This is the content of the cell in the first column and the second row of the table. [/table]

The Table (What you get)

Sample Table B This table is somewhat like a horizontal list.

The Code (What you type)

[table=3,1] [R=1,1] The stuff in column one, row one. [R=2,1] The stuff in column two, row one. [R=3,1] The stuff in column three, row one. [/table]

The Table (What you get)

Sample Table C This table is more complex, demonstrating the use of other formatting tags to make the first row act like a header for the rest of the table.

The Code (What you type)

[table=3,4] [R=1,1][b]Character[/b] [R=1,2]Asuka [R=1,3]Bryan [R=1,4]Carmen [R=2,1][b]Blood Type[/b] [R=2,2]A [R=2,3]B- [R=2,4]O+ [R=3,1][b]Zodiac Sign[/b] [R=3,2]Ox [R=3,3]Rat [R=3,4]Tarrasque [/table]

The Table (What you get)

Sample Table D This code produces the same table as in Sample C. Please note that the "R" tags are in a different order. For some people, this sort of organization might be more intuitive.

The Code (What you type)

[table=3,4] [R=1,1][b]Character[/b] [R=2,1][b]Blood Type[/b] [R=3,1][b]Zodiac Sign[/b] [R=1,2]Asuka [R=2,2]A [R=3,2]Ox [R=1,3]Bryan [R=2,3]B- [R=3,3]Rat [R=1,4]Carmen [R=2,4]O+ [R=3,4]Tarrasque [/table]

The Table (What you get)

Sample E: This example shows use of the list-numbering option.

The Code (What you type)

[table=2,6;1] [R=1,1][b]Orc Group[/b] [R=2,1][b]Status[/b] [R=2,2]Alive and fighting [R=2,3]Fleeing west [R=2,4]Begging for mercy [R=2,5]Weaving baskets [R=2,6]Discussing literature [/table]

The Table (What you get)

Sample F An advanced table used to describe a custom class.

The Code (What you type)

[table=4,11;1] [R=1,1][b]Level:[/b] [R=2,1][b]Base Attack Bonus:[/b] [R=3,1][b]Base Saves:[/b] [R=4,1][b]Special:[/b] [R=2,2]+11/+6/+1 [R=3,2]+2/+0/+0 [R=4,2]Cause, Oath [R=2,3]+12/+7/+2 [R=3,3]+3/+0/+0 [R=4,3]In your head [R=2,4]+13/+8/+3 [R=3,4]+3/+1/+1 [R=4,4]Calling of the cause [R=2,5]+14/+9/+4 [R=3,5]+4/+1/+1 [R=4,5]Oath, Fighter Bonus Feat [R=2,6]+15/+10/+5 [R=3,6]+4/+1/+1 [R=4,6]Further the cause [R=2,7]+16/+11/+6/+1 [R=3,7]+5/+2/+2 [R=4,7]Raise the Standard [R=2,8]+17/+12/+7/+2 [R=3,8]+5/+2/+2 [R=4,8]Oath [R=2,9]+18/+13/+8/+3 [R=3,9]+6/+2/+2 [R=4,9]Suffer for the cause [R=2,10]+19/+14/+9/+4 [R=3,10]+6/+3/+3 [R=4,10]Fighter Bonus Feat [R=2,11]+20/+15/+10/+5 [R=3,11]+7/+3/+3 [R=4,11]Champion of the cause, Further the cause, Oath [/table]

The Table (What you get)

Character Stat Block Tags

Stat blocks are another way of connecting character sheets to your posts. Simply put, the stat block is a section at the bottom of the character sheets which can be viewed and edited in your posts with the statblock tag.

If you need to find out to make and edit a character sheet in the first place, please read the Character Sheets Help Article. This feature works only for characters that have been applied to the given game.

The Syntax


  • STATBLOCK: This is the basic tag, and is always necessary. You can shorten this to SB if you want to abbreviate.
  • Text: Is used in different ways, depending on the option chosen. Typically, text items are entered in the format of "Number:StatName". These items are separated by semi-colons (;).
  • Option: There are three options: show, modify, and remove.
    • Show: Simply puts the current contents of the statblock into the post.
    • Modify: Changes the contents of the statblock to match whatever is in the text section, and then displays the statblock.
    • Remove: Removes the specified text item from the statblock.

But What is it Good For?

The statblock is useful for when you want to be able to keep track of something along the course of the game which is either important to know on command or may change. For combat-oriented games, this might mean the character's attack and defensive stats, their saving throws, and so forth. For games with expendable resources (like power points, wand charges, action points, etcetera), the statblock is a quick way of adding or removing these resources.

Also, you can always edit your statblock directly when in/at the character sheet itself. You'll find it in the D&D 3.5-template sheets, directly above the "Notes" section. This is handy when you need to reference statistics from other parts of the sheet.

Dealing with Multiple Characters (GMs and Players)

If you are a player with multiple characters, or a GM (who has the ability to view and modify stat blocks for all characters that have been applied to that game), there is a simple system for selecting which characters to view. Character sheets in a game are given a number based on the order of their Sheet ID values.

For example, if there are two character sheets in a game and their Sheet IDs are 4576 and 5033, then "1" would refer to 4576 and "2" to 5033. To view a specific character, specify that number in the statblock tag as follows:


Example: [STATBLOCK=1;show][/STATBLOCK] would show the statblock for the character with the lowest Sheet ID number.

If you are a GM, the default is to show all statblocks at once. If you want to show more than one character at once, you can put a list of these numbers, separated by commas, into the CharacterNumber field.

Example: [STATBLOCK=1,2,4,7;show][/STATBLOCK] would show the statblocks for the selected characters.

A Note of Caution

After you use a [statblock=modify] or [statblock=remove] tag to adjust a statblock and save the post, immediately edit the post and either delete the tags or replace them with [statblock=show] (if still want to display the statblock). The reason for this is that other editings, viewings, or replyings-to of the modify and remove posts may cause them to be re-parsed, causing their alterations (perhaps now out-of-date and irrelevant) to take place again.

To prevent these sorts of mix-ups, simply delete or replace all of your old statblock tags with [statblock=show] right after you use them.

Noparse Tags

Noparse Tags are designed to display vBcode in its raw format. In other words, any vBCodes wrapped inside the Noparse Tags will not be processed to function, but treated as plain text. This is best used to explain how vBCode works, and to create a code that others can simply copy and paste to use.

Syntax The command for Noparse Tags is as the following:


  • NOPARSE: This is the most important thing in the syntax. Note that, as with all vBCodes, it doesn't have to be in uppercase.
  • vBCode: any vBCode, such as OOC Tags, Private Text, or even Dice tags, and so on. Anything you want to be displayed without the server parsing the commands.

Examples Code:

[B]This is a bold text.[/B] [NOPARSE][B]This is a bold text.[/B][/NOPARSE]


This is a bold text. [B]This is a bold text.[/B]