Skip to content

Latest commit

 

History

History
52 lines (45 loc) · 2.14 KB

old_CONTRIBUTING.md

File metadata and controls

52 lines (45 loc) · 2.14 KB

English variants

  • Use only American English spelling, consistent with vanilla.

Internal code conventions

  • Use camelCase.

This style of variable naming for Endless Sky shall be named "Lemurian Dot Variables", or LDV.

Fleet, mission names

Fleet

faction.purpose.name.size.num
  • faction: fleet's faction. use short names for long full names (free worlds becomes fw, sayari plushie authority becomes spa)
  • purpose: purpose of fleet such as mining, fighting wars, or trading
  • name: any kind of name
  • size: size of fleet, solely based on ship count, lrg, med, sml; definition of size can be subjective
  • num: for specifying different variants if more precise control instead of variant #num desired

If two variants of a fleet exist, you may have them under 1 fleet as a variant or define them separately for more precise control.

Mission names

  • st Story missions
  • fl Flavor text (e.g Free Worlds secession dialogue)
  • ft Fighting missions
  • pi Pirate missions (e.g smuggling)
  • tr Transport missions
  • ex Exploration missions
  • ms Miscellaneous missions
tr.cargo.size.pirateRisk.num.#Faction

Attributes

  • cargo: Type of cargo, camelCase. bunks, cargo, or commodity name. Use bunks for passenger.
  • size: huge, xxlrg, xlrg, lrg, med, sml.
tons ship count size attr
0-200 0-4 sml
201-600 5-7 med
601-1200 8-12 lrg
1201-2000 13-20 xlrg
2001-3000 21-28 xxlrg
3001+ 29+ huge
  • pirateRisk: lrg, med, sml, involvement of capital ships is considered lrg, medium warships med, interceptors and small warships sml. pirateRisk will be the risk of attack from Merchants, Syndicate, and Republic ships if the mission is offered by pirates (e.g smuggling.)
  • num: increments up, used for offering missions more than one at a time.
  • #Faction: if the mission is faction specific. use short names. ideally, you should define faction-specific missions in a separate file.
  • if the mission falls under two categories, the two shall be separated by hyphens ("-"). the st flag will always go first.

NO: pi-st.bunks.lrg.med.1 YES: st-pi.bunks.lrg.med.69