In Praise of Our Volunteers
The adventure game (wargame+roleplaying game) industry is a small one, and there isn't the kind of money inside of it that other industries have. The industry consists of creative game designers willing to work 60 hours a week for half the pay they could command outside the game industry, all because they get to BE game designers.
Even at that, the only way the game industry survives is by the hard labor of unpaid volunteers who (for honor, glory, and rarely some free games) provide no end of valuable services to game publishers.
Mike West answers rules questions on FEDERATION COMMANDER. Nick Blank does the same thing for Federation & Empire, Andy Palmer for Prime Directive d20, Gary Plana for GURPS Prime Directive, Richard Sherman for Star Fleet Battle Force, and Mike Filsinger for STAR FLEET BATTLES.
Frank Brooks runs the Play-by-Email system as a volunteer. Paul Franz charges barely enough for the On-Line game system (for SFB and FC) to pay the server costs.
Federation & Empire would not exist without Jeff Laikind in charge of the overall game system and the Ship Information Tables, or without Chuck Strong (a real-world colonel from Space Command) keeping the scenarios updated and coherent.
Very little would get done on any of our games except for the Playtest Battle Labs run by Scott Moellmer in Colorado and by Mike Curtis and Tony Thomas in Tennessee. And all of the other playtesters are invaluable to us.
We have other staffers who do specific things (and sometimes a wide variety of things) for us including Scott Tenhoff, and Chris Fant (the F&E staff); Jean Sexton (Director of Proofreading and Product Professionalization); John Berg (Galactic Conquest Campaign); and John Sickels, Matthew Francois, Jonathan Thompson, and Loren Knight (Prime Directive). Some vital part of the product line would grind to a halt without each one of them.
Added to this list are hundreds of others who, during any given month, by Email or BBS or Forum, contribute in some way to the company and its product line. They may report a glitch in an existing product, playtest a product in development, suggest a new product, point out something another company is doing what we may want to take a look at emulating, look up a rules reference for another player, report on somebody who using our property improperly, comment on a posted draft of a new rule, or simply ask a question nobody else ever dared to ask.
Even at that, the only way the game industry survives is by the hard labor of unpaid volunteers who (for honor, glory, and rarely some free games) provide no end of valuable services to game publishers.
Mike West answers rules questions on FEDERATION COMMANDER. Nick Blank does the same thing for Federation & Empire, Andy Palmer for Prime Directive d20, Gary Plana for GURPS Prime Directive, Richard Sherman for Star Fleet Battle Force, and Mike Filsinger for STAR FLEET BATTLES.
Frank Brooks runs the Play-by-Email system as a volunteer. Paul Franz charges barely enough for the On-Line game system (for SFB and FC) to pay the server costs.
Federation & Empire would not exist without Jeff Laikind in charge of the overall game system and the Ship Information Tables, or without Chuck Strong (a real-world colonel from Space Command) keeping the scenarios updated and coherent.
Very little would get done on any of our games except for the Playtest Battle Labs run by Scott Moellmer in Colorado and by Mike Curtis and Tony Thomas in Tennessee. And all of the other playtesters are invaluable to us.
We have other staffers who do specific things (and sometimes a wide variety of things) for us including Scott Tenhoff, and Chris Fant (the F&E staff); Jean Sexton (Director of Proofreading and Product Professionalization); John Berg (Galactic Conquest Campaign); and John Sickels, Matthew Francois, Jonathan Thompson, and Loren Knight (Prime Directive). Some vital part of the product line would grind to a halt without each one of them.
Added to this list are hundreds of others who, during any given month, by Email or BBS or Forum, contribute in some way to the company and its product line. They may report a glitch in an existing product, playtest a product in development, suggest a new product, point out something another company is doing what we may want to take a look at emulating, look up a rules reference for another player, report on somebody who using our property improperly, comment on a posted draft of a new rule, or simply ask a question nobody else ever dared to ask.
<< Home