Vigilance Starfighter Group/archive

From Rebel Squadrons Wiki
Jump to navigationJump to search

The following is the archived proposal for the IBG-RgF merger.

Organization and Structure

Officers

The success of the new fleet will heavily depend on the hard work and dedication of its officers.


The Command Staff of the new fleet will be composed of the following:

  • Commanding Officer
  • Executive Officer
  • Second Officer (It can be disputed that SO is an unnecessary position and thus will not initially be filled.)


In addition to the Command Staff, the following positions will need filled:

  • Seven (7) Squadron Commanders
  • Two (2) Flight Instructors (Alternatively referred to as TCO and TXO)


In order to improve the efficiency of the command structure and to keep officers from spreading themselves too thinly, the new fleet will impose a rule that will limit officers to one position per person.


In addition, the following expectations and guidelines will be set for the following positions:

  • Commanding Officer
  • Executive Officer
  • Squadron Commanders
  • Flight Instructors


Units

The new fleet will utilize a streamlined command structure that removes the redundancy of a Wing Command Staff. Thus, Squadron Commanders will report directly to the Fleet Command; likewise with the Training and Auxiliary staff.


Wings

Due to the extent to which Wings are no longer a main source of activity, the mergered fleet will contain no wings, with the exception of support wings if at all. The additional strain on filling Wing command positions, in combination with no wing-level activity or otherwise competitions, make it an extraneous step in the fleet's hierarchy and thus the new fleet will be without wings.


Squadrons

Initially, there will be two XWA squadrons carried over from the IBG and four XvT squadrons carried over from the RgF. These squadrons will remain intact expect where conflicts occur. Pilots in more than one squadron will have to choose which squadron they preferred to remain with.

NOTE: Anyone that hasn't flown a mission for 3+ consecutive months has been removed from the roster.

This is what the squadrons will look like post merger:


Dagger Squadron 
CO: MGN Chris Horn "Kicks"
2: 2LT Elena (606)
3: 2LT Olith Hesto
4: GEN Himm El-Syna
5: BGN Ton Matty
6: VA Spokes
7: 1LT Jaja Darksight (606)
8: 2LT Py Modus
9: 
10: 
11: 
12: 
Dragon Squadron
CO: LCL David Vaughan
2: 2LT Kalurrachit
3: CPT Galactic Angel
4: CPT Kane Redron
5: MAJ Carlos
6: 
7: 
8: 2LT Jotheb Tahn
9: BGN David "Tenacious 'D'"
10: CPT Calista "Scarlet" Fairbright
11: 
12: 2LT Janis Deiverion


Phalcun Squadron
CO: BGN Anton "Ups" Nels
2: CPT Lukus Harman (606)
3: MGN Jon Anchorage
4: LJG Kier Santage
5: 
6: 
7: LCL shaolin
8: 2LT B'illiam (606) 
9: COL Reabel
10: 
11: 
12: 
Ragnarok Squadron
CO: 
2: 1LT Patryn Selant (412)
3: CPT AkinaMaru
4: LCL Triani Sovak (412)
5: 
6: 
7: MGN Chris Earthkeeper
8: 
9: GEN Wes Belden (412)
10: MGN Joshua Hawkins
11: 2LT Gavin Starseeker
12: BGN Jairo Pantoja
Red Dragon Squadron
CO: LCL Rahvin
XO: CPT Carth (email)
3: RA Gavin Cantorph Kravis
4: 2LT Han Sarganar (412)
5: COL Jack "Blazer" Barnes (412)
6: BGN Max Cal (412)
7: MAJ Hermann
8: CPT John Rayovac (email)
9: COL Tech Krill
10: CPT Guybrush Threepwood 
11: 2LT Shroomius (412)
12: GEN Corran Horn Jr. (412)
Resurrection Squadron
CO: MGN Phil DarkFire
2: MAJ Hec Losame (412)
3: MAJ Asen
4: 1LT KingBird (412)
XO: MAJ Luren "DaLe" Ketan
6: GEN Leonard Cable (412)
7: CPT Keldar "Whisper" Wenn
8: 1LT Kelem Syn (email)
9: 2LT Phelan Kell (412)
10: MAJ Bonaparte
11: CMDR Dyl'jo'ban (412)
12: 1LT Hyde


At first, we should anticipate having the RgF squadrons competing in XvT and the IBG squads competing in XWA, with handful of pilots flying both missions. Inevitably, the goal is to have pilots from all the squadrons competing in both missions. This can be accomplished with plenty of encouragement from the Fleet Command and well placed ISOs of the games.

Training Units

As one possibility, the fleet’s training academy will consist of two squadrons: on for XvT (Marshall) and one for XWA (Incubator). The Training Officer and Executive Training Officer will double as the XWA and XvT Instructors. Additional training squadrons, such as Top Gun program may be created later as the need arises.


Alternatively, an entire training wing may not be necessary. Two Flight Instructors, each assigned to a flight designated by platform may be sufficient to initiate pilots into the fleet.


Other alternatives might be considered pending a revision of the RS Training Office operations.


Auxiliary Units

The purpose of these auxiliary units will be to provide various types of services and support to the fleet; e.g. ITOD design. Additional support units will be created as needed, but this is not anticipated.


The ITOD Team will consist of three parts:

  • Design Team
  • XWA Mission Team
  • XvT Mission Team


The head of the ITOD Team will be the lead designer and creator of the current tour. Lead Designers will be rotated every tour, to provide fresh ideas and stories. The Design team will include the Lead Designer, the Logistics Officer (for council) and two other functionaries with writing or other creative process experience. The Missions teams will consist of a builder and three testers. The testers and builders my be rotated as the Lead Designer sees fit. The smooth operation of the ITOD Team is of paramount importance


Management and Operations

Storyline

Currently serving as Lead Designer for Tour 1 is David Vaughan. His story will incorporate a number of new design elements and be tying up loose ends form previous tours.

Activities

The primary activities we should support are:

  • Single-player ITOD mission reports - BoP, XWA (We can provide copies of BoP when necessary)
  • Multi-player ITOD mission reports - Zodiac-type (XvT/BoP)
  • Personal narratives based on the ITODs
  • Inter-club competitions (e.g. WoW)
  • Intra-club competitions (e.g. LIC)
  • Historical/non-active mission reports
  • Missionmaking

Single-player reports

All pilots will be able to participate in both missions. The new fleet will have two separate scoreboards, one for XWA and one for BoP. There are two methods by which this can be done on the database.

  • Assuming a common storyline, the missions will be listed as VSF 101 (XWA) and VSF 101 (BoP).
  • Alternatively, if there are two separate storylines, the two storylines will have individual names e.g. Vermillion for BoP and Shadowbane for XWA.

The creation and development of the ITODs will remain the responsibility of the ITOD Team as described above.

As the popularity of the OITODs rises, new missions will come out, much as with the regular TODs. OITODs may or may not be under the supervision of the TOD Team or a separate team. This is considered secondary in importance to the TODs.

For pilots looking for more to do, there will be a wide selection of historical and non-active mission reports from the missions database.

Multi-player competitions

The DL portion of LIC will be the focus of in-club competitions, as well as possible tournaments. 2v2 should be incorporated into the multiplayer system as well.

We'll also heavily encougae participation in inter-club events such as the ICTE, pending ORWs, and WoW.

Awards

Merits

The primary focus of the VSG should be good participation, activity, and spirit. To encourage a variety of ways of participating, a pilot can earn a certain number of merits each mission, as follows:

Single-player ITOD reports (fleet)
   8 - mission complete, first game
   4 - mission complete, second game
   4 - mission failure, first game
   2 - mission failure, second game
  10 - first place in a game
   9 - second place, and so on down to tenth
2-10 - personal narrative on mission
   4 - report, wing or squadron mission
Multiplayer ITOD reports
   8 - mission complete
   4 - mission failure
Multiplayer competitions (20pt max/month, inter-; 10pt, intra-)
   1 - each win
   1 - each 2 losses
Historical reports (10pt max/month)
   1 - each mission complete
   1 - each 2 mission failures
Missionmaking (12pt max/month)
 1-4 - each mission
Squadron bonuses:
  30 - first place in a game
  20 - second place
  10 - third place
  20 - best overall narratives
  10 - second best
  30 - most active in MP
  20 - second
  10 - third
  20 - best character (demonstrating HIER)
  10 - second
  (# members x 5) - 100% activity
  (# members x 3) - 75% activity
  (# members x 2) - 50% activity

Examples of this system in action: VSG merit system examples

Each squadron's score is calculated by adding each individual pilot's score plus the squadron bonuses. The squadron with the highest score is the fleet's Top Squadron for that month, and each pilot who participated in that squadron receives an appropriate award.

Merit Ranks:

  1. Rookie
  2. Certified
  3. Pilot
  4. Marksman 4th
  5. Marksman 3rd
  6. Marksman 2nd
  7. Marksman 1st
  8. Veteran 4th
  9. Veteran 3rd
  10. Veteran 2nd
  11. Veteran 1st
  12. Expert 4th
  13. Expert 3rd
  14. Expert 2nd
  15. Expert 1st
  16. Ace 4th
  17. Ace 3rd
  18. Ace 2nd
  19. Ace 1st
  20. Top Ace 4th
  21. Top Ace 3rd
  22. Top Ace 2nd
  23. Top Ace 1st
  24. Legend
  25. Master

Medals

-This is just a generic outline of what medals will be needed.
  • Honorary-type Medal -

Because every fleet will want to have some super-high up award for their fleets.

  • Graduation Medal -

Each game will have one of these still, so one for XWA and one for BoP.

  • Best Narrative Medal -

For the best narrative every mission.

  • Top Gun Medal -

For the individual winners of every ITOD/OITOD mission.

  • Top Squadron Medal -

For the top squadron of every ITOD/OITOD mission.

  • Gold Medal -

For first in LIC.

  • Silver Medal -

For second in LIC.

  • Bronze Medal -

For third in LIC.

Additional Considerations

Bylaws

Noticeably one of the immediate objections to the purposed fleet merger is that the new structure is in clear violation of the bylaws which govern the entire club. In defense of this proposal, times have changed; unnecessary command structure is a waste on an already thin leadership resource and is otherwise detrimental to the successful operation of this fleet.

Recently, bylaw amendments passed that allow fleets to operate without wings.