Revision as of 23:01, 13 January 2015

This user's time zone is Central Time. This user has a Pro-level subscription.
Achievements:
Achievement get! Citizen Achievement get! K Club Achievement get! See Me Rollin' Achievement get! Getting to Know You Achievement get! I Know You're Out There Achievement get! Patron of the Arts Achievement get! Better to Give Achievement get! Sheet Auteur

I have been using Roll20 since August, 2013. I started when I was trying to find an online battle grid for a D&D 4e campaign when we had multiple people joining via a conference call, and simply describing the layout of the battlefield was far too inefficient. One of the players, Eric V., recalled the Kickstarter for Roll20, and recommended that I look it up. My group has greatly enjoyed the features it grants, and I've gone as far as purchasing a Mentor-level subscription.

Background

I have approximately 10 years of experience with computer science, attending Rice University for computer science for four years. Since purchasing my Mentor-level membership, I've been putting that knowledge to use when I can with the Roll20 API.

My first tabletop roleplaying game was Vampire: the Masquerade in 2004, and I have since played:

• Advanced Dungeons & Dragons
• Black Crusade
• Changeling: the Dreaming
• Dark Ages: Mage
• Dark Ages: Vampire
• Dark Heresy
• Deathwatch
• Demon: the Fallen
• The Dreaming
• Dungeons & Dragons 3.5
• Dungeons & Dragons 4e
• Exalted
• Exalted 2e
• Fiasco
• Iron Kingdoms
• Legacy Crossing
• Mage: the Ascension
• Mage: the Awakening
• Mage: the Socerer's Crusade
• Mutants and Masterminds
• Outbreak Undead
• Paranoia
• Unknown Armies
• Unknown Ponies: Failure is Awesome
• Vampire: the Masquerade
• Werewolf: the Apocalypse
• Wraith: the Oblivion

I have also participated in three LARPs: Vampire: the Masquerade, an oWoD crossover (Vampire, Werewolf, and Changeling), and Exalted 2e.

Campaigns

I am currently running a game of Unknown Ponies: Failure is Awesome. I am participating in a game of Dungeons & Dragons 4E.

Projects

API Scripts

Working on the following API Script pages:

• Random Dungeon Generator
• Store Commands
• Raise Count

Wiki Beautification

As of June 16, 2014, there are:

• 248 wanted pages, the vast majority of which are from links in default wikimedia content
• 106 long pages
• 106 short pages
• 46 dead-end pages
• 22 orphaned pages
• 16 unused files
• 14 wanted categories
• 10 wanted files (plus 39 pages using a redirected file name)
• 10 uncategorized files, all of which are not used on any page
• 5 uncategorized pages, three of which I do not have permissions to edit and therefore cannot categorize, and two of which are pages on modules, and I'm uncertain whether they're supposed to be visible at all; I have decided not to touch them, just in case the visible page actually affects the module
• 2 unused templates
• 1 uncategorized category (Category:Docs), which I do not have permissions to edit and therefore cannot categorize
• 0 uncategorized templates
• 0 unused categories
• 0 wanted templates
• 0 broken redirects
• 0 double redirects

I have done a fair bit of work getting many of these numbers down. In the coming weeks, I intend to look into the wanted lists, and then start sifting through the actual page content, and trying to improve them -- especially the Docs, Tips, Guides, and API.

Automatic Fiasco

This will, ideally, be a Fiasco table which can be run without anyone with GM privileges being present.

Status:

• List and select playsets
• Start and stop game
• Join game/set character name
• Select relationships, needs, locations, and objects
• Establish/resolve scenes and grant white/black dice to self or others (depending on act)
• Select tilt

Needed:

• Set text for relationships/etc.
• Full tables for each playset (tied in with the above)

Exalted 2e Character Sheet

Runner-up for the character sheet contest!

Created in partnership with Benjamin Bandelow.

Status:

• Base Solar sheet complete
• Tabs organize information
• Expandable table for storing premade attack and damage rolls

Needed:

• Multiple sheet configurations in order to allow for alternative Exalt types; this is not yet implemented in the character sheet system

The most up-to-date (beta) version of the sheet's code can be found on my GitHub account. The code used by Roll20 (stable) can be found on Roll20's GitHub account; the former is a fork of the latter, and pull requests are often made to synchronize the two. However, if there is a difference between the two, the former repository will have the newer version.

You should not need either codebase unless you have to modify the sheet for your campaign: simply selecting Exalted 2e from the dropdown list in your campaign info should be sufficient.

If you want to report bugs or request new features for the character sheet, please submit issues on my repository. If you want to make changes to the sheet yourself, please fork my repository and submit pull requests to me, rather than forking the Roll20 repository directly and submitting pull requests to Riley.

Betrayal at House on the Hill

This project is currently on hold, largely due to desire for more interaction between cards/decks and the API.

Status:

• All images uploaded
• Script for choosing characters is complete
• Script for taking damage/healing characters is complete
• Script for starting the haunt is laid out
• Script for stunning monsters/recovering monsters is complete

Needed:

• Complete script to start the haunt (~2%)
• Input the text of all haunts (~7%)
• Create script to manage the room tiles
• A means to search decks (incl. room stack) and peek at the top of decks; this may require implementing the omens/items/events in some way other than Roll20's deck mechanic.

Git Notes

Delete a Commit

Back up to Head - N or a specific commit:

git reset --hard HEAD~1
git reset --hard sha1

Force the push

git push origin HEAD --force

Sync a Fork

git fetch upstream
git merge upstream/master
git push origin

Force Overwrite of Fork

Overwrites everything in the local copy with the original (upstream, the official repo), then uses that to overwrite the fork (origin).

git fetch upstream
git reset --hard upstream/master
git push origin HEAD --force

Requests

I'll gladly write scripts on request, to the best of my ability and during my free time. Leave a comment on my talk page, and I'll see what I can do. Not all ideas are possible, as the API isn't perfect.