2. What is RGA?
Rensselaer Gaming Association
LAN Parties
Mini-LAN every other Friday
Uber LAN every semester
Many tournaments
Team Fortress 2 (20-30 minutes)
Starcraft (1-2 hours)
Guitar Hero (3-5 minutes)
Halo Reach (10 minutes)
Spleef (5-10 minutes)
3. The RGA Dilemma
Competitors in multiple tournaments causing bottlenecks
Old Solution: Waiting it out
Building brackets for tournaments
Old solution: Excel / Google Docs spreadsheets
Notifying competitors when rounds start
Old solution: Shouting / Overhead / Loud Speaker
Discovering competitors are busy in other tournaments
Old solution: Facepalming
Answering competitors' questions
Old solution: Repeating ourselves
Workload distribution
Old solution: Club officers do everything manually
4. The RGA Solution
Competitors in multiple tournaments causing bottlenecks
New solution: Automatic scheduling, online chat
Building brackets for tournaments
New solution: Automatic bracket creation
Notifying competitors when rounds start
New solution: Via website & text alerts
Discovering competitors are busy in other tournaments
New solution: System tracks competitor status
Answering competitors' questions
New solution: Publicly viewable tournament rules &
status
Workload distribution
New solution: Many tasks handled by competitors
5. A pLANer Is Born
Flexible interface
Website
Mobile-compatible
Text messaging
Bracket management
Build bracket from registered competitors
Public bracket display
Records wins & losses
Automatic alerts to competitors
Allow competitors more control
Reporting wins & losses
Tournament signup
Notify players of what, where, when, and who to play
6. pLANer Tech
Webapp framework
Ruby on Rails
Authentication
Devise
Permissions
Cancan
Text messaging
Twilio (costs $)
Google Voice API (unofficial)
Compatible with MyRPI hosting
7. Thanks for listening
Special thanks to Sean O Sullivan & Professor Moorthy
Mike Pinkowish for hosting the Hackathon and showing us
Twilio
Git
https://github.com/cspotcode/pLANer
Email
cspotcode@gmail.edu
ashbyb@rpi.edu
Blog
rga.union.rpi.edu/blog