This token is designed to help dungeon masters copy PDF text from MM1 and MM3 sources, text from the old Monster Builder program, and XML text from the new DDI Adventure tools, and turn it into a functioning monster token.
[spoiler=Preview]Paste the stats card from Monster Builder (PC program text export or online XML export) or a PDF
...and get a functional monster token with stats and powers automatically created!
First and foremost, you must download and get the framework going. Visit the framework's thread at http://forums.rptools.net/viewtopic.php?f=8&t=15969&start=0.
This will be the one-stop area to download the current version of the token.
Upload date: November 9, 2011
Upload date: October 8, 2011
If you need help using the token, I have copied the text from the token's help button and reformatted it here. I incorporate steps that helpful folks in this thread have contributed, so if you find a helpful step on your own, please post it!
[spoiler=Current Help File]RegExParser for the DN Framework
Setting up Maptool for the Token:
- You must use Maptool version b76 or later; b87 is suggested.
- Configure Maptool to run a stack size of 4MB or larger. The parser runs several iterations and launches several functions as it checks the monster stat card text for its various sections, so if you don't set Maptool for a large enough stack size, it will fail and probably not even give you an error message.
- You must be running DN's framework version 5. You can download the framework from http://forums.rptools.net/viewtopic.php?f=8&t=15969&start=0.
- Once you have launched Maptool with the correct stack size and have loaded DN's framework, drop the parser token onto your library map and configure it for hot keys.
Setting up the Parser Token for Hot Keys:
- Select the Lib:RegExParser.
- Drag the macros from the Selection window (in the section called CopyToGlobal) to the Global Window.
- Right-click "Launch StatCard Entry" from the Global Window. Select "Edit".
- In the upper right, select "F3" from the "Hot Key" drop down menu.
- Check "Apply to Selected Tokens" in the bottom left corner. Click "OK"
F4: Trap Stat Card Entry window. Use this to bring up the entry window that you will use to write your trap's information to the token.
your monster and rolling damage dice.
Stat Card Entry window. Use this to bring up the entry window that you will use to write your monster's information to the token.
Procedure for Creating a Monster Token That Will Work in the DeviantNull 4th Edition Framework
- Drag and drop a token to the MapTool map space.
- Click on the monster token.
- Hit F3 to pop up the entry window. If it does not pop up,
you may need to click on the RegExParser token once and then back up to step 2. Also, make sure that you followed the steps in the first section, which details how to setup the hot keys.
- Fill out the entry windows according to the steps and
guidelines given below.
- Choose the source material for your monster (MM1 PDF, MM3--also works for old Monster Builder program, or XML--exported from the new online Monster Builder.
- Click the Save button on the entry window.
- Edit token to reflect any changes that you want to see with powers, etc..
Monster Stat Card Entry
- The top of the Stat Card Entry window will indicate whether you are using the Monster Manual 1 ("MM1 Monster Stat Card Entry"), Monster Manual 3 ("MM1 Monster Stat Card Entry"), or XML ("XML Monster Stat Card Entry") format. Beneath that line are clickable lines of text that allow you to switch to the format you are using. Click the link until you see the title for the format which you will be pasting into the entry window.
- Copy the entire stat card from a PDF source or from Monster Builder
- If you are using a PDF source, start selecting text with the monster name and finish after the ability scores and copy to the clipboard (CTRL-C from the PDF).
- If you are copying from Monster Builder, right-click the monster's name, choose "Copy as," and then "Copy as text." The parser will automatically clean out the copyright and origin text that comes from this source, so you don't have to worry about editing it out once you paste..
- If you are copying from the online Monster Builder, you will have to export the monster online, save the file to your computer, open the XML file in a text editor like Notepad, copy all of the text, and then paste it into the monster parser.
- If you are using a PDF source, start selecting text with the monster name and finish after the ability scores and copy to the clipboard (CTRL-C from the PDF).
- Paste the block of text into the first text entry box (CTRL-V to the "save to token" box), directly und the "Save to token" check box.
For MM1 sources: If you find that some powers appear in the same section of a previous power on the F2 stat sheet, you may need to insert a line break just before the power in this window. You may also want to replace characters that MapTool does not handle very well, like quotation marks and apostrophes (after saving the stats to the token and reloading the Monster Stat Card Entry frame, it is easier to see the characters that need to be replaced).
- If the body text of a power contains parenthetical information, you should replace the parentheses with double minus signs to simulate dashes. For example, "(see additional information in sidebar)" should be typed in as "--see additional information in sidebar--" because parentheses will make the parser think that the entire body entry is a power name.
- The Save to token check box is checked by default. Enabling this option causes the RegExParser to write the stat card information to a token. It also configures it to be an NPC token for the DN framework, which is necessary for the other areas of the entry sheet to function. The first time you edit a monster token, you should keep this enabled; however, since it resets the stat info on the monster token, you may want to disable it if you are just running the entry frame to update knowledge checks or add tactical information.
- You do not need to configure the token to use DNA properties, since the parser token will do that automatically for you.
- Copy the entire tactics block from your PDF, starting with
the line, "(monster name) Tactics"
- Paste this text into the entry box.
- Enable the check box in order to save to your monster token.
- If there is tactical information available in the XML text that you pasted, you can have the parser use that information by selecting the "Use tactics from XML" check box.
Information pasted into this window is added to the end of the DNA_CharacterNotes property, which is viewed in the Notes section of the character sheet. RegExParser makes the first line bold if it has the word "tactics" in it.
- Copy the entire lore block from your PDF, starting with the
line, "(monster name) Lore."
- Paste the block of text into this entry box.
- If you want to delete unnecessary line breaks so that
paragraphs do not look as choppy, do so now.
- Enable the check box in order to save the knowledge check
information to your monster token.
RegExParser should accurately create knowledge check entries on your
monster token if they exist in the following two formats:
- ...with a successful (skill name. i.e. "Arcana") check.
DC 25: Check results.
DC 30: Check results.
- ...with a
successful skill check.
(skill name) DC 25: Check results.
(skill name) DC 30: Check results.
If, however, your lore entry looks like :
...with a successful skill check.
(skill 1 name) or (skill 2 name) DC 25: Check results.
you can save this information and it will create checks for skill 2. To
create checks for skill 2, simply overwrite the skill 2 name with that
of skill one and save the information a second time.
Attempt to create powers.
Because powers exist in a seemingly endless variety, this function will not create powers on your token with 100% accuracy. Use this function as a time saver that will create most of your monster's power entries on your token, which you can then edit for details. RegExParser will create power entries with what it thinks the names of the powers are, as well as power types, action used, and recharge information. You will want to edit your powers so that they behave the way you want them to and so that they show the appropriate information.
Enable this check box if you would like to create powers on the token. Disable the box if you do not want to save ower information to the token (for example, if you are just updating the token with lore information).
Output complete power text entry to chat window.
If you check this option, the complete text entry for a given power will be copied to the "Special" field for the power and will appear in the chat window when you run it. If you leave this option unchecked, the text will still be copied to the "Special" text field for the power, but the check box to display the text will be unchecked.
Note: This option currently has no effect on XML monster tokens.
Output nonempty Effect, Attack, and Miss boxes
Checking this item will select to show the contents of the Effect, Hit, and Miss boxes for the power (as long as they contain text) in the chat window.
Note: For XML monster tokens, this will also display power requirements in the powers list.
Group all MM3 power entries in one power window.
If you leave this unchecked, the parser will created a separate power group window for each group of powers (i.e. traits, minor actions, etc.). If you want to conserve window space and see the text listed out in the same window, check this box. Your choice will be saved to the parser token as the default for the next time you run it.
Set the token's Private Rolls option to ON.
Check this to automatically set your token's option for making rolls private. Note: This only toggles the option for the framework to use, and doesn't affect how the framework actually employs its use. As of the time of the entry for this help file, the FF buttons in the framework still do not allow for private rolls.
Set the token's Hidden Rolls option to ON.
Check this to automatically set your token's option for making rolls hidden (prevents tooltips from a mousover that show the dice and base values). See note for previous entry.
Set the token's Private Health Rolls option to ON.
Check this to automatically set your token's option for making health rolls private. See note for previous entries. Currently, the option only comes up as the default in health/damage rolls that are linked from token powers.
Recharge Roll Type:
(From DN's help section) Sets how a token processes its recharge rolls when using rechargeable powers. Separate Rolls means it rolls a 1d6 for each power it can recharge. Singe Roll means it makes one 1d6 roll and checks that result against every power it can recharge.
Apply Damage States:
(From DN's help section) Sets if the character sheet should apply the bloodied, dying, and dead states to a token when it takes damage.
When Dying Change To:
(From DN's help section) This changes the layer of the token when it becomes dying, handy to change them to objects to get them out of the way.
When Dead Change To:
(From DN's help section) Same as dying except the trigger is Dead.
Click the save button to write all information in areas whose check boxes are enabled to the token. The frame window stays open so that you can change information.
When you no longer need the entry window, you can close it and recall it at a later time by selecting your monster token and hitting the F3 key.[/spoiler]
- The parser will now accept XML text exported from the online Monster Builder
- Updated help button.
- Removed references to F2 and quick stat card.
- MM3PowerSifter: Fixed issue finding ongoing damage in text with multiple conditions.
Fixed secondary Hit text grabbing "Hit:" as well as other text.
Hit text that doesn't contain damage roll info now does not contain "Hit:".
Fixed an issue with triggered action powers whose name contains "Attack" before the open parenthesis.
- KnowledgeParser: Fixed some bugs.
Knowledge checks now add onto current knowledge check list rather than replace it.
- MM3PowerSifter: Fixed Free Action setting for triggered effects.
Attack (without the initial damage roll), Miss, and Effect information now goes into those boxes (for secondary attacks as well).
Checks for prone condition.
Checks for ongoing conditions that a save can end--from this list:
removed from play
- PowersParser: Checks for prone condition.
- MM3EditMonsterFrame: Added option to output nonempty Effect, Hit, and Miss boxes.
- StatsParser: Shows first bloodied trigger text.
Checks for vulnerability on MM1 and MM3 cards.
- MM1 & MM3 MonsterFrame: Added options for hidden and private rolls.
Split power options and token options into two sections.
- StatsParser: Pulls in resistance, vulnerability, and immunity information for both MM1 and MM3.
- PowersParser: MM1 stat entry now creates a new batch of powers instead of tacking them on the end of the previous list.
Now lists triggers in the power sheet.
Now places the full power text in the special field.
- MM1EditMonsterFrame: Has option to output MM1 full power text to chat or to suppress it.
- MM3PowersParser finds Traits and Powers sections when they are completely capitalized.
MM3PowerSifter & PowerParser: now add damage type to power. They also add ongoing damage that a save can end.
- MM1 & MM3 EditMonsterFrame: Added token options for recharging roll type, applying damage states, and changing token type when dying or dead--and remembers choices. Frame now remembers choice to save stat card and to create powers.
- MM3PowerSifter & PowersParser: Corrected an issue where the parser was adding the die number as extra damage to a roll where there was originally no bonus damage.
Began color coding macro buttons to make it easier to edit and reference in the help file.
- StatsParser: Sets the DNA_HealingSurgeBase value along with the other surge values so that they are not lost when you edit the monster's stats.
Writes the selected values for private health, private rolls, and hidden rolls to the monster token.
- StatsParser: Sets private rolls option to of, and sets private health and hidden rolls to on. Code is documented, so you can see where to change it if needed. In the future, these will be an option on the parser token itself.
Added Zalarian's Streetwise fix.
Help: updated help button with posts from discussion thread.
- Added option to save MM3 powers in one power group instead of splitting them up.
Parses Other Powers.
- Parses move actions.
Looks for hit points, temp hp, and surge usage in healing powers, then adds them on as another attack entry so that you can use the link in the chat output.
Full power text appears in Special field.
There is now a check box on the MM3 input sheet that allows choosing whether the Special field is output in the chat window. This selection is remembered.
Parses for triggered actions.
- Fixed several pop-ups for MM1.
Close attacks now blank out area size and range if they don't exist.
Fixed keywords not showing.
Fixed AOP notes not showing.
Added frame for MM3 sheet and ability to switch between MM1 and MM3. Parser token remembers last setting for card style.
Fixed method for parsing perception abilities, languages, and alignment so that StatsParser should now parse MM1 and MM3 sheets.
Will parse Traits, Standard Actions, and Minor Actions for MM3.
Fixed aura names issue for MM3.
Some powers in Monster Builder list recharges with dice and some give lowest die roll possible. Fixed the recharge parser to cope.
- Fixed attack vs. not showing properly.
Now looks for secondary attacks.
Range and action type icons now show.
Fixed issue where attack showed when power wasn't an attack.
- Parses most powers, but only does icons for recharge and aura.
Fixed assignment of aura type if "aura" was present in an attack power.
- Creates Powers group and adds names of powers.
- Fixed passive insight and passive perception.
- Only designed to work with MM1 stat cards.
Power creation is disabled.
Haven't bothered with trap functionality.
Enters monster stats and will set knowledge checks and tactics.