Editing Line Developer

Warning: You are not logged in. Your IP address will be publicly visible if you make any edits. If you log in or create an account, your edits will be attributed to your username, along with other benefits.

The edit can be undone. Please check the comparison below to verify that this is what you want to do, and then save the changes below to finish undoing the edit.

Latest revision Your text
Line 2: Line 2:
  
 
==Overview==
 
==Overview==
The '''[[BattleTech]] Line Developer''' ("LD") is the lead developer and director of the BattleTech tabletop universe. Overseeing things from start to finish, the Line Developer solicits and manages the efforts of the writers and artists, freelance or otherwise, who create official BattleTech products and events. While generally operating in concert and collaboration with a variety of elements on the creative team, the Line Developer is also effectively the final word in the BattleTech universe and its [[canon]], ultimately determining the overall direction and tone of the books and storyline.
+
The '''[[BattleTech]] Line Developer''' ("LD") is the lead developer and director of the BattleTech tabletop universe.
  
BattleTech fans summarily refer to people who are in a position to define [[Canon]] because they own or have righfully licensed the appropriate [[w:Intellectual Property|intellectual properties]] or are trusted with the IP by the owner or licensee, particularly the Line Developer himself but also the staff of authors and artists answering to the LD, as ('''The''') '''Powers That Be''', TPTB for short.
+
Overseeing things from start to finish, the Line Developer solicits and manages the efforts of the writers and artists, freelance or otherwise, who produce the physical online publications of BattleTech. While generally operating in concert and collaboration with a variety of elements on the creative team, the Line Developer is also effectively the final word in the BattleTech universe and its [[canon]], ultimately determining the overall direction and tone of the books and storyline.  
  
 
In the current Internet era the Line Developer is also an increasingly accessible means of seeking canon clarifications via either the [http://bg.battletech.com/forums/index.php/board,34.0.html Ask the Lead Developers] or [http://bg.battletech.com/forums/index.php/board,41.0.html Ask the Writers] sections on the [[BattleTech Forum]]s.
 
In the current Internet era the Line Developer is also an increasingly accessible means of seeking canon clarifications via either the [http://bg.battletech.com/forums/index.php/board,34.0.html Ask the Lead Developers] or [http://bg.battletech.com/forums/index.php/board,41.0.html Ask the Writers] sections on the [[BattleTech Forum]]s.
  
 
An Assistant Line Developer position exists since 1996 (at the latest). Many Assistant Line Developers would go on to become full Line Developer.
 
An Assistant Line Developer position exists since 1996 (at the latest). Many Assistant Line Developers would go on to become full Line Developer.
 +
 +
BattleTech fans summarily refer to people who are in a position to define [[Canon]] because they own or have righfully licensed the appropriate [[w:Intellectual Property|intellectual properties]] or are trusted with the IP by the owner or licensee, particularly the Line Developer, as ('''The''') '''Powers That Be''', TPTB for short.
  
 
==History==
 
==History==
Line 22: Line 24:
  
 
===List of Line Developers===
 
===List of Line Developers===
*[[Sam Lewis]] (arguably; game developer across all game lines from when he signed up with FASA in 1987 until ca. 1989)
+
*[[Sam Lewis]] (arguably; until ca. 1989.)
*[[Michael Nystul]] (preceded Scott Jenkins, but exact dates unknown; apparently, from ca. 1989 through the end of 1991)
+
*[[Michael Nystul]] (preceded Scott Jenkins, but exact dates unknown; apparently, from ca. 1989 to the end of 1990)
 
*[[Scott Jenkins]] (preceded Bryan Nystul, but exact dates unknown; apparently, from 1st quarter 1992 through 1993)
 
*[[Scott Jenkins]] (preceded Bryan Nystul, but exact dates unknown; apparently, from 1st quarter 1992 through 1993)
 
*[[Bryan Nystul]] (January 1994 - August 2000)
 
*[[Bryan Nystul]] (January 1994 - August 2000)
Line 31: Line 33:
 
*[[Brent Evans]] (15 May 2017 - 13 September 2019)
 
*[[Brent Evans]] (15 May 2017 - 13 September 2019)
 
*[[Ray Arrastia]] (since 13 September 2019)
 
*[[Ray Arrastia]] (since 13 September 2019)
 
 
===List of Assistant Line Developers===
 
===List of Assistant Line Developers===
 
*Randall N. Bills (1996 - August 2000)
 
*Randall N. Bills (1996 - August 2000)
Line 37: Line 38:
 
*[[Ben H. Rome]] (12 December 2008 - 07 October 2016)
 
*[[Ben H. Rome]] (12 December 2008 - 07 October 2016)
 
*Ray Arrastia (01 June 2017 - 13 September 2019)
 
*Ray Arrastia (01 June 2017 - 13 September 2019)
*[[Aaron Cahall]] (since 28 October 2020)
 
  
 
==External Links==
 
==External Links==
Line 44: Line 44:
 
* [http://bg.battletech.com/?p=5196 A Changing Of The BattleTech Development Guard - Herb Beas steps down as Line Developer, 25 Aug 2013]
 
* [http://bg.battletech.com/?p=5196 A Changing Of The BattleTech Development Guard - Herb Beas steps down as Line Developer, 25 Aug 2013]
 
* [http://www.catalystgamelabs.com/about/ Catalyst Game Labs Staff Page]
 
* [http://www.catalystgamelabs.com/about/ Catalyst Game Labs Staff Page]
 
[[Category:Battletech Media Franchise]]
 

Please note that all contributions to BattleTechWiki are considered to be released under the GNU FDL 1.2 (see BattleTechWiki:Copyrights for details). If you do not want your writing to be edited mercilessly and redistributed at will, then do not submit it here.
You are also promising us that you wrote this yourself, or copied it from a public domain or similar free resource. Do not submit copyrighted work without permission!

To edit this page, please answer the question that appears below (more info):

Cancel Editing help (opens in new window)

Advanced templates:

Editing: {{Merge}}   {{Moratorium}}   {{Otheruses| | | }}

Notices: {{NoEdit}}   {{Sign}}   {{Unsigned|name}}   {{Welcome}}

Administration: {{Essay}}   {{Policy}}   {{Procedure}}