<![CDATA[Halo Space Station Evolved - Development ]]> https://projectunsc.org/forum/ Tue, 19 May 2026 12:46:32 +0000 MyBB <![CDATA[Firefight gamemode]]> https://projectunsc.org/forum/showthread.php?tid=1733 Mon, 18 May 2020 11:20:58 +0000 Cael_Aislinn]]> https://projectunsc.org/forum/showthread.php?tid=1733
Firefight: As UNSC, defend a box fort in the middle of the desert against varied waves of Covenant troops
Stranded: As UNSC, defend the same box fort against hordes of Flood zombies
Crusade: As Covenant, defend the gravlift against waves of UNSC as you invade the forest colony on Sigma Octanus IV

A number of changes will be flowing across to other gamemodes as well, such as the new buildable defences and various bugfixes and qol stuff. 

Full changelog here: https://github.com/HaloSpaceStation/Halo...pull/2424/

Testing the defences
[Image: CSjSctl.png]

Here they come!
[Image: pCuKVTa.png]

I found a supply drop
[Image: yXnRCtF.png]

Reinforcements have arrived
[Image: i8X66Ip.png]

This guy looks like business
[Image: A4amIyk.png]

The human vermin defend their world
[Image: 236cb19015ba4d5e638f8f16faf026b5.png]]]>
Firefight: As UNSC, defend a box fort in the middle of the desert against varied waves of Covenant troops
Stranded: As UNSC, defend the same box fort against hordes of Flood zombies
Crusade: As Covenant, defend the gravlift against waves of UNSC as you invade the forest colony on Sigma Octanus IV

A number of changes will be flowing across to other gamemodes as well, such as the new buildable defences and various bugfixes and qol stuff. 

Full changelog here: https://github.com/HaloSpaceStation/Halo...pull/2424/

Testing the defences
[Image: CSjSctl.png]

Here they come!
[Image: pCuKVTa.png]

I found a supply drop
[Image: yXnRCtF.png]

Reinforcements have arrived
[Image: i8X66Ip.png]

This guy looks like business
[Image: A4amIyk.png]

The human vermin defend their world
[Image: 236cb19015ba4d5e638f8f16faf026b5.png]]]> <![CDATA[Gamemode: UNSC Achlys]]> https://projectunsc.org/forum/showthread.php?tid=1058 Wed, 22 Jan 2020 03:09:11 +0000 Desolane900]]> https://projectunsc.org/forum/showthread.php?tid=1058
--UNSC Data Archives--
!!Update!!
----------------------
Accessing ONI Section I File# 22-468206-051

!!Error!!

Authenticating Identification...

Please Standby...

Identification Accepted

Current User: Commanding Officer of commandeered Mariner-class Dante
------------------------------
If this is a mistake or unexpected login of identified user, please contact a system administrator
------------------------------
Accessing ONI Section I File# 22-468206-051

From: [REDACTED]
BCC: CINCONI, XEG
Subject: Short Notice Briefing

This transmission will have been beamed to you on location through the slipspace communications array mounted on the Dante before it left [REDACTED].  Do not reply. The ship you are searching for is operating under the callsign Achlys and is believed to have gone missing in the coordinates provided. Your mission is to ascertain the current status of the ship and react accordingly to data uncovered in your investigation, as well as destroy any navigational data on board the ship through Cole Protocol. It comes from an amalgamation of multiple ONI departments and is considered top priority for you and the men under your command. The following information has been provided to you specifically under a strict need-to-know basis.

  1. The Achlys is confirmed to have been boarded by Covenant forces in their final transmission. Any nonhuman entity is considered to be eliminated with extreme prejudice. The location of Earth must be safeguarded by any means necessary. The Dante has been outfitted with a micro MAC cannon for disposal of the ship, to be used in extreme circumstances only. This information is provided under assumption that the marines you have been allotted cannot, under hypothetical circumstances with utmost regard to collected onsite information used to degrees of computational accuracy, complete their mission with an unexpected mortality rate of 99.9%. Addendum-01: If recon, or a loss of recon, indicate the Achlys has been compromised beyond retrieval, the Dante has full authorization to utilize the on board micro MAC cannon to destroy the Achlys, regardless of passengers or unforeseen external threat.
  2. Any surviving humans that may have been spared by Covenant forces or survived until your arrival through other means are suspected to be Insurrectionists and other terrorists of the state. Their survival can only mean that they are working with the Covenant and/or failed to follow through with United Nations Space Command Emergency Priority Order 098831A-1 themselves and are considered traitors to the UNSC, under articles JAG 845-P and JAG 7556-L, committing treason which is justifiable grounds for execution.
  3. One or more ONI Operatives from Section III may or may not have been implanted into your troops with strict orders to secure top secret data on the ship and ensure that all survivors of this operation are permanently silenced when the operatives believe the time has come to eliminate them. No living being will be authorized to leave the Achlys under any circumstances unless those operatives fail their mission. If aforementioned operatives fail to dispatch any being considered living, aforementioned living creature, human or covenant, is to be held in strict isolated containment until such time that the Dante has returned to the designated rendezvous site.
If any of the above conditions are exposed to any living person you will face prompt and immediate execution from sleeper agents placed within your own crew, including aforementioned operatives operating under your command whose names and ranks will remain undisclosed. All operatives are under strict orders to eliminate yourself as well as identified double agents that are under assumption that they, or yourself, can expose ONI directives to anyone not involved. Consider this footnote your final and only warning, Commander.

OOC Notes and Elaborations:

  1. This gamemode is based on the novel/animated film Mona Lisa. It has focus on survival horror and fighting against stacked odds. The intent is for players to write their own story in an atmospheric environment but the gamemode does not follow the novel/film to the letter. Making subtle references to them will give you brownie points with me, whining about the fact that it doesn't follow the narrative to a T will get you on my shitlist. It's a game. Treat it as one and enjoy it for what it's worth.
  2. There will still be a roleplay expectation in this gamemode. Marines are expected to stay in uniform and listen to their chain of command to the best of their abilities. Acting in an LRP behavior will still get you banned. A prisoner's mind could be broken by what they've witnessed, but at least do it tastefully without screaming and turning on the capslock cruise control.
  3. Using this flavor text letter to metagame IC is against the rules. Unless you're the CO and can make a cool briefing out of it without giving away too much to make an Operative shoot you, which they will, and you might get job banned.
  4. ONI Operatives will shoot other marines. It's supposed to happen. Admins will not get involved in FF incidents. that being said, Operatives shooting people on the Dante will get them job banned and possibly ban banned.
  5. Marines don't need to shoot prisoners or covenant. It's not even encouraged. That said, prisoners and covies don't need to be friendly. Henry still beat up Lopez to get on that last escape pod, and Covenant have been committing a mass genocide for decades. If a prisoner wants to self antag, they have every right to. If a marine wants to shoot a covie, they have every right to.
  6. The Commander doesn't need to stay on the Dante as I can understand now ahead of time the job will get boring. That said, if the CO dies, the marines will lose the round.
  7. Prisoners will have seemingly meta knowledge about flood they can choose to divulge to marines. This has a limit. No prisoner is going to know about super cool John Halo working with the Gravemind on Installation 00 in Halo 3 and there was friendly floods and a giant talking hentai food from hell. When in doubt, play dumb and ease down on knowledge.
  8. Covenant Prisoners: You might get shot. Not a single admin wants an ahelp because you wanted to be Henry and got BTFO by a marine. Covies have been glassing human colonies for decades by now. Take one for the team.
  9. Do not spoil the game for other players. Booting it up by yourself and trying to bomb through it with meta-knowledge is not the intent of the gamemode. It is designed for player enjoyment via atmosphere and tension. Taking away from these elements defeats the purpose and ruins the experience.
]]>
--UNSC Data Archives--
!!Update!!
----------------------
Accessing ONI Section I File# 22-468206-051

!!Error!!

Authenticating Identification...

Please Standby...

Identification Accepted

Current User: Commanding Officer of commandeered Mariner-class Dante
------------------------------
If this is a mistake or unexpected login of identified user, please contact a system administrator
------------------------------
Accessing ONI Section I File# 22-468206-051

From: [REDACTED]
BCC: CINCONI, XEG
Subject: Short Notice Briefing

This transmission will have been beamed to you on location through the slipspace communications array mounted on the Dante before it left [REDACTED].  Do not reply. The ship you are searching for is operating under the callsign Achlys and is believed to have gone missing in the coordinates provided. Your mission is to ascertain the current status of the ship and react accordingly to data uncovered in your investigation, as well as destroy any navigational data on board the ship through Cole Protocol. It comes from an amalgamation of multiple ONI departments and is considered top priority for you and the men under your command. The following information has been provided to you specifically under a strict need-to-know basis.

  1. The Achlys is confirmed to have been boarded by Covenant forces in their final transmission. Any nonhuman entity is considered to be eliminated with extreme prejudice. The location of Earth must be safeguarded by any means necessary. The Dante has been outfitted with a micro MAC cannon for disposal of the ship, to be used in extreme circumstances only. This information is provided under assumption that the marines you have been allotted cannot, under hypothetical circumstances with utmost regard to collected onsite information used to degrees of computational accuracy, complete their mission with an unexpected mortality rate of 99.9%. Addendum-01: If recon, or a loss of recon, indicate the Achlys has been compromised beyond retrieval, the Dante has full authorization to utilize the on board micro MAC cannon to destroy the Achlys, regardless of passengers or unforeseen external threat.
  2. Any surviving humans that may have been spared by Covenant forces or survived until your arrival through other means are suspected to be Insurrectionists and other terrorists of the state. Their survival can only mean that they are working with the Covenant and/or failed to follow through with United Nations Space Command Emergency Priority Order 098831A-1 themselves and are considered traitors to the UNSC, under articles JAG 845-P and JAG 7556-L, committing treason which is justifiable grounds for execution.
  3. One or more ONI Operatives from Section III may or may not have been implanted into your troops with strict orders to secure top secret data on the ship and ensure that all survivors of this operation are permanently silenced when the operatives believe the time has come to eliminate them. No living being will be authorized to leave the Achlys under any circumstances unless those operatives fail their mission. If aforementioned operatives fail to dispatch any being considered living, aforementioned living creature, human or covenant, is to be held in strict isolated containment until such time that the Dante has returned to the designated rendezvous site.
If any of the above conditions are exposed to any living person you will face prompt and immediate execution from sleeper agents placed within your own crew, including aforementioned operatives operating under your command whose names and ranks will remain undisclosed. All operatives are under strict orders to eliminate yourself as well as identified double agents that are under assumption that they, or yourself, can expose ONI directives to anyone not involved. Consider this footnote your final and only warning, Commander.

OOC Notes and Elaborations:

  1. This gamemode is based on the novel/animated film Mona Lisa. It has focus on survival horror and fighting against stacked odds. The intent is for players to write their own story in an atmospheric environment but the gamemode does not follow the novel/film to the letter. Making subtle references to them will give you brownie points with me, whining about the fact that it doesn't follow the narrative to a T will get you on my shitlist. It's a game. Treat it as one and enjoy it for what it's worth.
  2. There will still be a roleplay expectation in this gamemode. Marines are expected to stay in uniform and listen to their chain of command to the best of their abilities. Acting in an LRP behavior will still get you banned. A prisoner's mind could be broken by what they've witnessed, but at least do it tastefully without screaming and turning on the capslock cruise control.
  3. Using this flavor text letter to metagame IC is against the rules. Unless you're the CO and can make a cool briefing out of it without giving away too much to make an Operative shoot you, which they will, and you might get job banned.
  4. ONI Operatives will shoot other marines. It's supposed to happen. Admins will not get involved in FF incidents. that being said, Operatives shooting people on the Dante will get them job banned and possibly ban banned.
  5. Marines don't need to shoot prisoners or covenant. It's not even encouraged. That said, prisoners and covies don't need to be friendly. Henry still beat up Lopez to get on that last escape pod, and Covenant have been committing a mass genocide for decades. If a prisoner wants to self antag, they have every right to. If a marine wants to shoot a covie, they have every right to.
  6. The Commander doesn't need to stay on the Dante as I can understand now ahead of time the job will get boring. That said, if the CO dies, the marines will lose the round.
  7. Prisoners will have seemingly meta knowledge about flood they can choose to divulge to marines. This has a limit. No prisoner is going to know about super cool John Halo working with the Gravemind on Installation 00 in Halo 3 and there was friendly floods and a giant talking hentai food from hell. When in doubt, play dumb and ease down on knowledge.
  8. Covenant Prisoners: You might get shot. Not a single admin wants an ahelp because you wanted to be Henry and got BTFO by a marine. Covies have been glassing human colonies for decades by now. Take one for the team.
  9. Do not spoil the game for other players. Booting it up by yourself and trying to bomb through it with meta-knowledge is not the intent of the gamemode. It is designed for player enjoyment via atmosphere and tension. Taking away from these elements defeats the purpose and ruins the experience.
]]> <![CDATA[First Contact: the 3 way balance]]> https://projectunsc.org/forum/showthread.php?tid=1037 Mon, 25 Mar 2019 12:58:51 +0000 Cael_Aislinn]]> https://projectunsc.org/forum/showthread.php?tid=1037 https://www.youtube.com/watch?v=kuk39DhOkTc

The Insurrection gamemode was added around 2017 to provide some basic gameplay for the server. Basic overmap and Covenant gameplay quickly followed. Although not intended as a major faction the Insurrection faction is now a key part of our community. 

With our server concept we are aiming for asymmetrical gameplay between 2-5 factions featuring a mixture of gameplay styles and roleplay, with gameplay styles including PvP combat, space capital ship combat, dogfighting, civilian/innie economic gameplay etc. 

Different factions will have a focus on different gameplay styles as well as aesthetics and objectives. This means a competitive balance will be very hard. The Covenant are meant to be OP in space combat, and slightly OP in ground combat. Innies are meant to be initially UP in all areas but with more flexibility and strength gain. UNSC are meant to be reactive and probably have the hardest objectives. 

Balancing will need to account the following factors: 
- Faction base (Covenant: none, UNSC: fortified base, Innies: one or more hidden bases)
- Starting ship (Covenant: strong, UNSC: average, Innies: none but can get one late round)
- Equipment and racial bonuses (Covenant: strong, UNSC: average to strong, Innies: weak but can grow strong late round)
- Stealth options (Covenant: some, UNSC: a few, Innies: lots)
- Defensive objectives (Covenant: very few, UNSC: lots, Innies: some)
- Aggressive objectives (Covenant: lots, UNSC: some, Innies: very few)

Lots of tweaking will need to be done to balance this.]]> https://www.youtube.com/watch?v=kuk39DhOkTc

The Insurrection gamemode was added around 2017 to provide some basic gameplay for the server. Basic overmap and Covenant gameplay quickly followed. Although not intended as a major faction the Insurrection faction is now a key part of our community. 

With our server concept we are aiming for asymmetrical gameplay between 2-5 factions featuring a mixture of gameplay styles and roleplay, with gameplay styles including PvP combat, space capital ship combat, dogfighting, civilian/innie economic gameplay etc. 

Different factions will have a focus on different gameplay styles as well as aesthetics and objectives. This means a competitive balance will be very hard. The Covenant are meant to be OP in space combat, and slightly OP in ground combat. Innies are meant to be initially UP in all areas but with more flexibility and strength gain. UNSC are meant to be reactive and probably have the hardest objectives. 

Balancing will need to account the following factors: 
- Faction base (Covenant: none, UNSC: fortified base, Innies: one or more hidden bases)
- Starting ship (Covenant: strong, UNSC: average, Innies: none but can get one late round)
- Equipment and racial bonuses (Covenant: strong, UNSC: average to strong, Innies: weak but can grow strong late round)
- Stealth options (Covenant: some, UNSC: a few, Innies: lots)
- Defensive objectives (Covenant: very few, UNSC: lots, Innies: some)
- Aggressive objectives (Covenant: lots, UNSC: some, Innies: very few)

Lots of tweaking will need to be done to balance this.]]> <![CDATA[Covenant Alpha wind down]]> https://projectunsc.org/forum/showthread.php?tid=904 Sat, 29 Dec 2018 09:01:23 +0000 Cael_Aislinn]]> https://projectunsc.org/forum/showthread.php?tid=904
In the meantime (and over the next few months) please keep feedback coming in about the Covenant features so we can keep tweaking and bugfixing them as necessary. For any general suggestions or bug reports, go to https://github.com/HaloSpaceStation/Halo...issues/new

For any feedback about balancing or improving the gamemodes Operation: Red Flag or Packwar, please post it in this thread.]]>
In the meantime (and over the next few months) please keep feedback coming in about the Covenant features so we can keep tweaking and bugfixing them as necessary. For any general suggestions or bug reports, go to https://github.com/HaloSpaceStation/Halo...issues/new

For any feedback about balancing or improving the gamemodes Operation: Red Flag or Packwar, please post it in this thread.]]> <![CDATA[Voice actors wanted]]> https://projectunsc.org/forum/showthread.php?tid=899 Tue, 25 Dec 2018 10:45:43 +0000 Cael_Aislinn]]> https://projectunsc.org/forum/showthread.php?tid=899
UNSC
  • "All hands bring the ship up to combat alert alpha"
  • "Drop pods prepare to launch"
  • "Launch fighters"
  • "Evacuate"
  • "Welcome to Halostation13"
Covenant
  • "Warriors, prepare for combat"
  • "When we joined the Covenant we took an oath. All according to station. All without exception. On the blood of our fathers, on the blood of our sons, we swore to uphold the Covenant. Even to our dying breath. Those who would break this oath are heretics, worthy of neither pity nor mercy. We shall grind them into dust. And continue our march to glorious salvation."
Also some good stuff here https://www.halopedia.org/Sangheili/Quotes]]>
UNSC
  • "All hands bring the ship up to combat alert alpha"
  • "Drop pods prepare to launch"
  • "Launch fighters"
  • "Evacuate"
  • "Welcome to Halostation13"
Covenant
  • "Warriors, prepare for combat"
  • "When we joined the Covenant we took an oath. All according to station. All without exception. On the blood of our fathers, on the blood of our sons, we swore to uphold the Covenant. Even to our dying breath. Those who would break this oath are heretics, worthy of neither pity nor mercy. We shall grind them into dust. And continue our march to glorious salvation."
Also some good stuff here https://www.halopedia.org/Sangheili/Quotes]]> <![CDATA[The Overmap Arc]]> https://projectunsc.org/forum/showthread.php?tid=840 Sun, 25 Nov 2018 02:03:39 +0000 Cael_Aislinn]]> https://projectunsc.org/forum/showthread.php?tid=840 https://projectunsc.org/forum/showthread...8&pid=1956

Post ideas and more details about arc plans here. 

More civilian colony jobs, NPCs and economy
  • Bartender minigame (with drunk NPCs)
  • Scrap salvager
  • More civilian/insurrection research with illegal options and gadgets
  • Chemist minigame
  • Organlegging (with NPC trader)
  • Data broker (buying and selling research blueprints, hidden locations, mercenary info, gamemode info, other secrets etc)
  • Kig-Yar smuggler
  • Gas mining and processing
  • Expanded manufacturing and crafting
Player trading ships between colonies
  • Trade destinations mapped in (3-4 locations)
  • Able to buy quantities in bulk
  • Smuggling/tariffs/customs duties
  • More commodities for players  
  • Pseudo-dynamic commodity pricing with NPCs also adjusting to changing market

More NPC ship interactions
  • NPC ships have NPC traders on board that travel between locations and into or out of the system
  • Board NPC ships to arrest NPC smugglers
  • NPC pirates who demand cash transfers 
Balances, bugfixes, QOL and more content for First Contact and Insurrection mode
  • Ongoing
Innie Commandos and gadgets
  • Seeking ideas

Expanded black market and grey market 
  • NPC ships come and go with traders
  • More research options including gadgets
  • More commodities for purchase or production which can be traded or manufactured into items and sold or used

Space weather
  • Asteroid fields
  • Ice fields
  • Ion storms
  • Solar radiation pulses
  • Comets

Random events fixes and additions
  • See space weather
  • Fixes empty or bugged random events

Improved space combat (dogfighting, capital ship weapons) and boarding
  • Port from old code
  • Port ship combat from space battles, star trek station, ftlstation

Dogfighting and flyable shuttles
  • Port from old code
  • Rewrite shuttles
  • Player spawns all moved to static bases (space stations, planets etc) and NPC shuttles allow automated movement for those players without ship access

Civilian focussed gamemodes
  • Price of Power gamemode

Covenant artifact hunt gamemodes
  • Raid gamemode
]]> https://projectunsc.org/forum/showthread...8&pid=1956

Post ideas and more details about arc plans here. 

More civilian colony jobs, NPCs and economy
  • Bartender minigame (with drunk NPCs)
  • Scrap salvager
  • More civilian/insurrection research with illegal options and gadgets
  • Chemist minigame
  • Organlegging (with NPC trader)
  • Data broker (buying and selling research blueprints, hidden locations, mercenary info, gamemode info, other secrets etc)
  • Kig-Yar smuggler
  • Gas mining and processing
  • Expanded manufacturing and crafting
Player trading ships between colonies
  • Trade destinations mapped in (3-4 locations)
  • Able to buy quantities in bulk
  • Smuggling/tariffs/customs duties
  • More commodities for players  
  • Pseudo-dynamic commodity pricing with NPCs also adjusting to changing market

More NPC ship interactions
  • NPC ships have NPC traders on board that travel between locations and into or out of the system
  • Board NPC ships to arrest NPC smugglers
  • NPC pirates who demand cash transfers 
Balances, bugfixes, QOL and more content for First Contact and Insurrection mode
  • Ongoing
Innie Commandos and gadgets
  • Seeking ideas

Expanded black market and grey market 
  • NPC ships come and go with traders
  • More research options including gadgets
  • More commodities for purchase or production which can be traded or manufactured into items and sold or used

Space weather
  • Asteroid fields
  • Ice fields
  • Ion storms
  • Solar radiation pulses
  • Comets

Random events fixes and additions
  • See space weather
  • Fixes empty or bugged random events

Improved space combat (dogfighting, capital ship weapons) and boarding
  • Port from old code
  • Port ship combat from space battles, star trek station, ftlstation

Dogfighting and flyable shuttles
  • Port from old code
  • Rewrite shuttles
  • Player spawns all moved to static bases (space stations, planets etc) and NPC shuttles allow automated movement for those players without ship access

Civilian focussed gamemodes
  • Price of Power gamemode

Covenant artifact hunt gamemodes
  • Raid gamemode
]]> <![CDATA[2018/2019 Roadmap]]> https://projectunsc.org/forum/showthread.php?tid=838 Sun, 25 Nov 2018 01:20:38 +0000 Cael_Aislinn]]> https://projectunsc.org/forum/showthread.php?tid=838

2019
Quote:Overmap Arc
  • More civilian colony jobs, NPCs and economy
  • Player trading ships between colonies
  • More NPC ship interactions
  • Balances, bugfixes, QOL and more content for First Contact and Insurrection mode
  • Innie gadgets
  • Expanded black market and grey market 
  • Space weather (asteroid fields, ice fields, ion storms, solar radiation pulses, comets etc)
  • Random events fixes and additions (see also space weather)
  • Improved space combat (dogfighting, capital ship weapons) and boarding
  • Dogfighting and flyable shuttles
  • Civilian focussed gamemodes
  • Covenant artifact hunt gamemodes
  • Improved objectives system

2019-2020
Quote:Forerunner Arc
  • Playable monitors and sentinels
  • Prometheans
  • Forerunner installation
  • Flood content
  • More Flood themed gamemodes (also expanding Stranded)
  • Forerunner installation gamemodes

2019-2020

Quote:Invasion Arc

???

Completed Arcs

1/6/18 - finishing by new year

Quote:Covenant Arc 
  • Make all Covenant species playable
  • Add race specific gear for Covenant
  • Add working Covenant languages and comms
  • Map in Covenant ships
  • Add Covenant themed gamemodes
]]>

2019
Quote:Overmap Arc
  • More civilian colony jobs, NPCs and economy
  • Player trading ships between colonies
  • More NPC ship interactions
  • Balances, bugfixes, QOL and more content for First Contact and Insurrection mode
  • Innie gadgets
  • Expanded black market and grey market 
  • Space weather (asteroid fields, ice fields, ion storms, solar radiation pulses, comets etc)
  • Random events fixes and additions (see also space weather)
  • Improved space combat (dogfighting, capital ship weapons) and boarding
  • Dogfighting and flyable shuttles
  • Civilian focussed gamemodes
  • Covenant artifact hunt gamemodes
  • Improved objectives system

2019-2020
Quote:Forerunner Arc
  • Playable monitors and sentinels
  • Prometheans
  • Forerunner installation
  • Flood content
  • More Flood themed gamemodes (also expanding Stranded)
  • Forerunner installation gamemodes

2019-2020

Quote:Invasion Arc

???

Completed Arcs

1/6/18 - finishing by new year

Quote:Covenant Arc 
  • Make all Covenant species playable
  • Add race specific gear for Covenant
  • Add working Covenant languages and comms
  • Map in Covenant ships
  • Add Covenant themed gamemodes
]]> <![CDATA[Gamemode: City Hunt]]> https://projectunsc.org/forum/showthread.php?tid=507 Thu, 05 Apr 2018 03:14:09 +0000 Desolane900]]> https://projectunsc.org/forum/showthread.php?tid=507
Details: The city will have 3-4 z levels including a basement level with sewers and basements, the street level, and each building will possibly be either a single story structure, two story, or sky scraper style tower. The entire map will have a run down, recently attacked, gritty and dark feel to it. I will be taking heavy inspiration from H3ODST with styling the city and adding the possibility of supply caches. This gamemode would not require Covenant being more fleshed out though that would be helpful.

Roles: The Covenant would have grunt minors, elite minors, and possibly a limit of 1-2 cloaked elites. The human roles would be surviving police, insurrectionists, marines, and a slim number of ODST that dropped late into the fight. Civilians were either killed or evacuated earlier before the round began.

This Gamemode would be based around humans either killing the remaining covenant or hiding out/running until they get what they want and leave. There would be no clear cut victory or loss, only a story of survivors in their last hours as aliens rip their city apart in search of what they believe to be Forerunner artifacts.]]>
Details: The city will have 3-4 z levels including a basement level with sewers and basements, the street level, and each building will possibly be either a single story structure, two story, or sky scraper style tower. The entire map will have a run down, recently attacked, gritty and dark feel to it. I will be taking heavy inspiration from H3ODST with styling the city and adding the possibility of supply caches. This gamemode would not require Covenant being more fleshed out though that would be helpful.

Roles: The Covenant would have grunt minors, elite minors, and possibly a limit of 1-2 cloaked elites. The human roles would be surviving police, insurrectionists, marines, and a slim number of ODST that dropped late into the fight. Civilians were either killed or evacuated earlier before the round began.

This Gamemode would be based around humans either killing the remaining covenant or hiding out/running until they get what they want and leave. There would be no clear cut victory or loss, only a story of survivors in their last hours as aliens rip their city apart in search of what they believe to be Forerunner artifacts.]]> <![CDATA[Introducing strategy elements to our 2D spaceman simulator: Logistics and teamwork]]> https://projectunsc.org/forum/showthread.php?tid=252 Fri, 09 Dec 2016 06:28:45 +0000 Cael_Aislinn]]> https://projectunsc.org/forum/showthread.php?tid=252
Faction politics
- "Civilian" players are loosely affiliated and can sabotage, negotiate/aid or switch sides at will.
- Sometimes a greater threat can arise which will force bitter enemies to set aside their differences just to survive...

Added Support Player roles
- Fighters and bombers require refuelling, repairing and rearming after each engagement while pilots will require rest (or stimulants).
- Fighters and bombers need coordination and target setting from players in command to be effective.
- Marines are initially cloistered away in their barracks, their deployment needs to be coordinated via dropship with a pilot and a drop target (same with their extraction).
- Vehicles, weapons and gear are customisable so analyse your enemy's gear to determine their weaknesses.

New types of combat
- Dogfighting requires a different skillset in customisable vehicles.
- Capital ship combat requires careful positioning to maximise weapons fire while minimising damage. Players can crew turrets to help protect their ship.
- Electronic warfare, mines, targetting capital ship weakpoints and infiltration by boarding are all alternative options for defeating your enemy.

Electronic warfare
- Minimise your emissions to stay hidden, or simply lurk near something "loud" enough to disguise you.
- Encrypt your comms to prevent eavesdropping, but the more you talk the easier it is to decrypt.
- EMP weaponry can temporarily disable vehicles, weapons and components.
- Lock on missiles can be fooled or spoofed.
- Infiltrators can hack in to disable or overload systems. Particularly advanced tech can do it remotely...]]>
Faction politics
- "Civilian" players are loosely affiliated and can sabotage, negotiate/aid or switch sides at will.
- Sometimes a greater threat can arise which will force bitter enemies to set aside their differences just to survive...

Added Support Player roles
- Fighters and bombers require refuelling, repairing and rearming after each engagement while pilots will require rest (or stimulants).
- Fighters and bombers need coordination and target setting from players in command to be effective.
- Marines are initially cloistered away in their barracks, their deployment needs to be coordinated via dropship with a pilot and a drop target (same with their extraction).
- Vehicles, weapons and gear are customisable so analyse your enemy's gear to determine their weaknesses.

New types of combat
- Dogfighting requires a different skillset in customisable vehicles.
- Capital ship combat requires careful positioning to maximise weapons fire while minimising damage. Players can crew turrets to help protect their ship.
- Electronic warfare, mines, targetting capital ship weakpoints and infiltration by boarding are all alternative options for defeating your enemy.

Electronic warfare
- Minimise your emissions to stay hidden, or simply lurk near something "loud" enough to disguise you.
- Encrypt your comms to prevent eavesdropping, but the more you talk the easier it is to decrypt.
- EMP weaponry can temporarily disable vehicles, weapons and components.
- Lock on missiles can be fooled or spoofed.
- Infiltrators can hack in to disable or overload systems. Particularly advanced tech can do it remotely...]]> <![CDATA[Datanets: a streamlined replacement for SS13 radio signalling]]> https://projectunsc.org/forum/showthread.php?tid=251 Sun, 04 Dec 2016 03:39:24 +0000 Cael_Aislinn]]> https://projectunsc.org/forum/showthread.php?tid=251
While this system is fairly robust and feature complete, it is also overly complex and time consuming to setup and produces some in-world conflicts with overmap (the global controller means there are no restrictions for distance, and there is no handling for interference or jamming). On the whole it's quite powerful but I never liked using it due to those over-complexities and the transmission lag.

I've experimented with replacement systems in the past for other projects, but now I've decided to develop a replacement system integrated directly into overmap called datanets. They are prototyped right now with airlocks and will attempt to emulate a P2P network topology (any device can communicate with any other device and there is no "master controller" except for a coordinator datum for handling meta aspects such as data transfer and machine linking/delinking). The idea is that the datanet simply determines whether and what is connected in a super light framework, then any data transfer or processing is handled fully by the participating atoms. It's not as robust as signalling networks under the hood but should be able to produce the same functionality with a significantly decreased workload for mappers and coders.

SS13 radio signalling networks have multiple steps to do, requiring a frequency to be set for all participating atoms then unique tags for each assigned and linked manually via the map editor. Datanet airlocks only need a single tag set for all participating atoms in that net to be set (along with a small amount of metadata) to be set via the map editor.

For the moment radio signalling will exist alongside datanets and they can both be used as normal (I manually integrated radio telecommunications into the overmap several months ago so that it behaves as expected) although they won't need or be required to communicate. Eventually I'd like to completely replace everything using radio signalling with datanets, then remove radio signalling entirely. The change should be invisible to players, but make maintenance + development + extension of the features much easier in the long run.]]>
While this system is fairly robust and feature complete, it is also overly complex and time consuming to setup and produces some in-world conflicts with overmap (the global controller means there are no restrictions for distance, and there is no handling for interference or jamming). On the whole it's quite powerful but I never liked using it due to those over-complexities and the transmission lag.

I've experimented with replacement systems in the past for other projects, but now I've decided to develop a replacement system integrated directly into overmap called datanets. They are prototyped right now with airlocks and will attempt to emulate a P2P network topology (any device can communicate with any other device and there is no "master controller" except for a coordinator datum for handling meta aspects such as data transfer and machine linking/delinking). The idea is that the datanet simply determines whether and what is connected in a super light framework, then any data transfer or processing is handled fully by the participating atoms. It's not as robust as signalling networks under the hood but should be able to produce the same functionality with a significantly decreased workload for mappers and coders.

SS13 radio signalling networks have multiple steps to do, requiring a frequency to be set for all participating atoms then unique tags for each assigned and linked manually via the map editor. Datanet airlocks only need a single tag set for all participating atoms in that net to be set (along with a small amount of metadata) to be set via the map editor.

For the moment radio signalling will exist alongside datanets and they can both be used as normal (I manually integrated radio telecommunications into the overmap several months ago so that it behaves as expected) although they won't need or be required to communicate. Eventually I'd like to completely replace everything using radio signalling with datanets, then remove radio signalling entirely. The change should be invisible to players, but make maintenance + development + extension of the features much easier in the long run.]]> <![CDATA[Some WIP fighter HUD shots]]> https://projectunsc.org/forum/showthread.php?tid=246 Sat, 29 Oct 2016 23:18:00 +0000 Cael_Aislinn]]> https://projectunsc.org/forum/showthread.php?tid=246 https://gyazo.com/514a39d3bb76fcfc008ade2154e1c17f
https://gyazo.com/75268c0ca4e1b2069950eadaff5ac682

Adding and removing vehicle components
https://gyazo.com/0535bf301ad416b54600296957ec4da6]]> https://gyazo.com/514a39d3bb76fcfc008ade2154e1c17f
https://gyazo.com/75268c0ca4e1b2069950eadaff5ac682

Adding and removing vehicle components
https://gyazo.com/0535bf301ad416b54600296957ec4da6]]> <![CDATA[Procedural Asteroids Tech Demo]]> https://projectunsc.org/forum/showthread.php?tid=234 Wed, 17 Aug 2016 00:38:09 +0000 Cael_Aislinn]]> https://projectunsc.org/forum/showthread.php?tid=234

https://www.youtube.com/watch?v=8QBZ_-JNdTU]]>

https://www.youtube.com/watch?v=8QBZ_-JNdTU]]> <![CDATA[Recommended reading for new developers]]> https://projectunsc.org/forum/showthread.php?tid=225 Mon, 18 Jul 2016 11:28:34 +0000 bloxgate]]> https://projectunsc.org/forum/showthread.php?tid=225
  • First off I'd recommend reading chapter 2 (and preferably chapter 3) of the Git Documentation Book.
  • Then take a look at the Forking Workflow guide.
  • If in doubt, google is your friend.
  • If you still need help, just ask in the development Skype chat and we'll do our best to help you.
]]>
  • First off I'd recommend reading chapter 2 (and preferably chapter 3) of the Git Documentation Book.
  • Then take a look at the Forking Workflow guide.
  • If in doubt, google is your friend.
  • If you still need help, just ask in the development Skype chat and we'll do our best to help you.
]]> <![CDATA[Workflow tutorial for developing ships, shuttles, space stations, asteroid bases]]> https://projectunsc.org/forum/showthread.php?tid=218 Tue, 17 May 2016 13:26:42 +0000 Cael_Aislinn]]> https://projectunsc.org/forum/showthread.php?tid=218
1. Decide the kind of ship or station you want to make, its size and its purpose. For performance reasons we want to minimise the number of things using 2 or more zlevels (separate decks) by themselves but don't be afraid to make something bigger if you want to. Engines are props and there's no other ship mounted machinery like weapons, comms antennae, sensors etc at the moment but leave space for them as they'll get added eventually. Covenant turfs aren't in the code yet so stick to human ships. Space stations and asteroid bases are basically the same as capital ships but a little bit simpler. In the code stations and asteroid bases are treated identically. Anything larger than 20x20 must be either a capital ship or station (not a shuttle) and can use one or more zlevels.

2. Map the internal layout. Size guidelines for some possible ship/shuttle types are:

- Small shuttle, dropship, personnel lighter, escape pod: up to 6x6 tiles (shuttle class)
- Large shuttle, tug, gunboat, heavy dropship, small yacht: up to 20x20 tiles (shuttle class)
- Stealth vessel, light freighter, transport ship, patrol boat, sub-prowler/sub-corvette, luxury yacht: 1 zlevel (capital class)
- Corvette, light frigate, medium freighter, personnel transport: 2 zlevels (capital class)
- Frigate, light destroyer, heavy freighter, refinery ship: 3 zlevels (capital class)
- Destroyer, heavy frigate, light cruiser, light carrier, colony ship: 4 zlevels (capital class)
- Heavy cruiser, carrier: 5 zlevels (capital class)

Space stations and asteroid bases can be anywhere from 1-5+ zlevels depending on their purpose. Shuttle class ships are able to physically move around inside and dock with capital class ships. We can theoretically make shuttles up to around 50x50 or larger, but any larger than 20x20 and gameplay/performance issues crop up. There are also specific turfs you need to use for shuttles. Capital class ships and space stations occupy entire zlevels and have static layouts. On the overmap both type of ships work near identically but should be given different sized sprites to represent their size difference. Place a minimum 50 tile margin of empty space around the edge of anything occupying one or more zlevels.

Map your shuttles facing north (up) and map your capital ships facing east (right). Don't ask me why because I was probably drunk at the time. I might get drunk and make them the same someday but forget to tell anyone so all the ships suddenly start flying sideways. Spacestations and asteroids can do whatever they want. Make sure that the map z dimension is always 1 and split separate decks off into separate mapfiles labelling then myship-1.dmm myship-2.dmm etc.

2(a). Shuttle specific stuff

The shuttle code requires that the only turf type used internally are of type /turf/simulated/shuttle/hull (for the shuttle) and /turf/unsimulated/blocker (for any empty space around it). To achieve a desired visual effect, you will need to modify the icon and icon_state of the turf in the map editor to match what you want. To do this right click on the turf, go to the dropdown for it and select "Edit..." then scroll down to where it says icon in the left column. In the right column enter the path of the icon you want to use inside single brackets (eg 'icons/turf/space.dmi') then press "OK". Go to the edit menu again, and this time scroll down to where it says icon_state in the left column and put the name of the icon state you want in the right column in double brackets (eg "plating"). To find a list of possible turf sprites to use, navigate to icons/turf inside Dreammaker.

For floor turfs (ie are non-dense and non-opaque) use /turf/simulated/shuttle/hull/floor and for windows (dense and non-opaque) /turf/simulated/shuttle/hull/window the parent hull type /turf/simulated/shuttle/hull function as walls (dense and opaque). Don't worry about maglocks, they don't use specific turfs for now.

Do not map out any areas, but make sure you place exactly 1 APC somewhere (SMES and cabling are optional but there if you want them) and at least 1 /obj/machinery/computer/shuttle_helm to fly the shuttle. Lighting is also required, and you can use ordinary airlocks as normal to divide internal cabins and rooms. Place some /obj/machinery/door/airlock/external/shuttle to allow players to enter and exit the shuttle while it is in flight (not maglocked). Putting the machinery for a cycling airlock is not necessary as most shuttles will be flying to and from hangars or planets with atmosphere, but you can do it if you want (eg for a salvage or SAR shuttle).

The map file containing this layout should use the exact same dimensions. Eg if your shuttle is 12x15 then the map should be 12x and 15y.

Nothing other than shuttles should use these turf types.

3. Get an overmap sprite for your ship or station

Shuttles: the sprite should be around 16x16 from one end to the other (use a standard 32x32 dmi size) with a little bit of leeway either size (eg you could do a 10x10 or 20x20 sprite). Create it as an state in code\modules\overmap\overmap_vehicles\icons\overmap_vehicles.dmi and call it whatever you want but remember it for the next step (4). Make sure the sprite is facing north and don't bother creating directional states.

Capital ships or space stations: The overmap sprite should be 32x32 for things that are 1 full zlevels, 64x64 for things that are 2 full zlevels, 96x96 for things that are 3 zlevels, 128x128 for things that are 4 or more zlevels. Also include icon states for thrusting and braking (reverse thrust). For the dimensions larger than 32 you will need to use an external editor then import it into Dreammaker, I recommend Paint.NET as it's free, small and fast but with loads of features. Place it as a new icon inside the folder code\modules\overmap\ships and name the icon states "base" "thrust" and "brake" for ships. Make sure all 3 icon states exist (if ship), but just reuse the base sprite if you don't have the extra ones. Make sure the sprites are facing north and don't bother creating directional states. 32x32 station sprites can go into code\modules\overmap\ships\sector_icons.dmi or just as new icons into code\modules\overmap\overmapobj (sorry it's a little bit disorganised). Remember the icon name and icon_state for the next step (4a and 4b and 4c).

3(a). Shuttle top-down sprites

The top-down sprite is used for the shuttle when it is in flight (eg docking with or leaving a hangar) and the dimensions need to match the full pixel dimensions of the internal layout so an external editor is required. To calculate the size required, count the x width and y-height of the shuttle excluding any empty space then multiply by the standard Byond turf size of 32x32. For example, a shuttle that is 5 turfs wide and 10 turfs high will need a top-down sprite with dimensions 160 (5 x 32) by 320 (10 x 32).

Once you figure out the required dimensions either obtain the services of an artist or map out the "roof" in Dreammaker using whatever turfs you like then take a screenshot and scale/crop it to the required proportions. Place the image into its own DMI (ensuring it is facing north) and call the icon state "shuttle". Call the icon itself whatever you want, but remember it for the next step (4a).

3(b). Sensor HUD images

Everything the size of a fighter or larger needs a unique sprite to quickly identify it when it pops up on a player's sensor HUD. The sprite should be 32x32 and grayscale (because it is coloured in according to its faction or light blue for environmental stuff like asteroids and stars). Place the sprite in code\modules\overmap\overmap_vehicles\icons\overmap_vehicle_hud.dmi and name it whatever you want but remember it for the next step (4).

4(a). Implementing shuttles in code

Open up code\modules\overmap\overmap_vehicles\instances\shuttles.dm then scroll down to the bottom of the file and copy paste the following code at the end:

Code:
/obj/machinery/overmap_vehicle/shuttle/my_shuttle_path
   name = "My Awesome Shuttlecraft"
   desc = "For transporting Super Cool Dudes while making spacey noises with your mouth."
   icon = 'code/modules/overmap/overmap_vehicles/shuttles/my_shuttle_icon.dmi'
   overmap_icon_state = "unsc_shuttle"
   maglock_strength = 8
   bound_width = 192
   bound_height = 384
   layout_file = 'maps/ships/my_shuttle_layout.dmm'
   layout_x = 6
   layout_y = 12
   iff_faction_broadcast = "UNSC"
   hull_remaining = 250
   hull_max = 250
   armour = 75
   maglocked_at_spawn = 0

We will now edit some lines to customise this code. Some lines are optional and if they aren't changed then they can be deleted to make the code a little cleaner. We'll go through the lines one by one.

Code:
/obj/machinery/overmap_vehicle/shuttle/my_shuttle_path

Change my_shuttle_path to whatever you want but keep it reasonably simple and only use lower case letters and underscores (eg colonial_salvage_shuttle).

Code:
   name = "My Awesome Shuttlecraft"
   desc = "For transporting Super Cool Dudes while making spacey noises with your mouth."

Change these to whatever you want. This is what the players see when they mouse over or examine the shuttle.

Code:
   icon = 'code/modules/overmap/overmap_vehicles/shuttles/my_shuttle_icon.dmi'

Change this to the icon containing your top down sprite you made in step 3(a).

Code:
   overmap_icon_state = "unsc_shuttle"

This should match the icon_state of the overmap icon you made in step 3.

Code:
   maglock_strength = 8

This is the number of adjacent or overlapping walls and floors required to "maglock" or dock with a capital ship. Pick the side you want to use to dock (usually the one with airlocks in it) and this number should be slightly less than that. Eg if the sides of your shuttle are 8 tiles high then the maglock strength should be 6.

Code:
   bound_width = 192
   bound_height = 384

This should be changed to the exact dimensions of the top down sprite.

Code:
   layout_file = 'maps/ships/my_shuttle_layout.dmm'
   layout_x = 6
   layout_y = 12

Change the layout file to be the map file containing your layout, and make sure the layout_x and layout_y match the map dimensions.

Code:
   iff_faction_broadcast = "UNSC"

Optional: Determines the faction alignment for sensors. Available options are "UNSC" "Insurrection" "Covenant". Probably just leave this as UNSC for now because the Insurrection aren't in a habit of broadcasting their presence.

Code:
   hull_remaining = 250
   hull_max = 250
   armour = 75

Optional: hull_remaining and hull_max should be set the same and represent the overall health of the shuttle. armour functions as damage mitigation and anything that deals less damage than this value is ignored. If something deals more damage than the armour value then hull is removed according to the function hull_remaining -= damage / armour means something that deals the same amount of damage as the shuttle has armour will only remove 1 point of hull. Be sensible and look at existing values to balance this. If you're in doubt then don't change it.

Code:
   maglocked_at_spawn = 0

Optional: determines if the shuttle spawns in as maglocked (docked) at the start of the game.

4(b). Implementing capships in code

Open up code\modules\overmap\ships\unique_ships.dm then scroll down to the bottom of the file and copy paste the following code at the end:

Code:
/obj/effect/zlevelinfo/ship/my_ship
    name = "UNSC Derpaderp"
    desc = "For a brick it flies pretty good."
    icon = 'code/modules/overmap/ships/my_ship_icon.dmi'
    faction = "UNSC"
    init_bounds_dims = 96
    use_me_to_initialise = 0
    sensor_icon_state = "7th_column"

We'll break it down line by line. Sensors are definitely working but leave speed and acceleration etc alone again for now.

Code:
/obj/effect/zlevelinfo/ship/my_ship

Change my_ship to something simple and clear and only using lowercase letters and underscores.

Code:
    name = "UNSC Derpaderp"
    desc = "For a brick it flies pretty good."

What the players see. Remember that UNSC specifically refers to navy ships (including ONI). For civilian ships use CAA (Colonial Administration Authority), UEGS (United Earth Government Ship), your own made up acronym or nothing at all. The desc should be describe it's origins and purpose while being informative and short.

Code:
    icon = 'code/modules/overmap/ships/my_ship_icon.dmi'

Change this to the icon you made in step 3.

Code:
    faction = "UNSC"

For sensor faction purposes. Available values are "UNSC" "Insurrection" "Covenant" but again best left as "UNSC" for now.

Code:
    init_bounds_dims = 96

Set this to the dimensions of your overmap sprite (which should be square).

Code:
    sensor_icon_state = "7th_column"

Set this to the icon_state you created in step 3(b).

Code:
    use_me_to_initialise = 0

This is a magic number and should be kept as 0. We'll look at it in step 5a.

4©. Implementing stations and asteroid bases in code

These are the simplest to do. Open up code\modules\overmapobj\unique.dm (it might not exist and need to be created). Scroll to the end and copy paste the following code:

Code:
/obj/effect/overmapobj/my_station_thingy
    name = "a station or something"
    desc = "a thingy"
    icon = 'code/modules/overmap/ships/sector_icons.dmi'
    icon_state = "mysprite"
    faction = "UNSC"
    init_sensors = 1
    sensor_icon_state = "mysensorsprite"

Then we gonna edit some lines.

Code:
/obj/effect/overmapobj/my_station_thingy

Change to something short with only lowercase and underscores.

Code:
    name = "a station or something"
    desc = "a thingy"

What the players see. Do something descriptive.

Code:
    icon = 'code/modules/overmap/ships/sector_icons.dmi'
    icon_state = "mysprite"

Change this to the icon and icon_state you created in step 3.

Code:
    init_sensors = 1

Keep this line and make sure it is set to 1. ~~magic~~

Code:
    faction = "UNSC"

This is for sensor alignment colour. Available options are "UNSC" "Insurrection" "Covenant" but you can also set it to any random value and it will stay in grayscale.

Code:
    sensor_icon_state = "mysensorsprite"

This should match the icon_state you created in step 3(b). Sensors might not setup correctly at the moment but remind me to fix it because it's probably just a quick tweak.

5. Final steps - testing (read this for shuttles, ships, stations, asteroids)

Press control+k or choose Build -> Compile (from the top menu list). Shuttles can skip the rest and go directly to 5c

What we need to do now is to make sure the map files are loaded correctly by the code. When they are loaded should be handled by the code (ie the gamemode or whatever code spawns your thing in midround) but we need to do some final stuff to determine how they are loaded. Compile the code and open up each of the map files for your ship or station. If there are any errors double check you have copy pasted the code correctly. In step 4 we defined a metaobject which contains the information on how to properly load, create and initialise our ship or station. Ships and stations/asteroids are done slightly differently (eventually I'm going to make them the same which will simplify this a bit). In order to initialise both and spawn them on the map for testing we need to place a specific meta info object on each of the map files for our thing then place a different kind of meta info object into the overmap at the coordinates we want it to spawn in for testing.

Note 1: If you can't find it in the object list then remember to click the + for each / in the type path and explore until you find it (make sure you have compiled at the start of this step).

Note 2: If you are having trouble placing one of the meta info objects make sure your placement cursor type is set to "Add" (an icon of a filled in box with a plus side in the top right corner) which is the leftmost of 3 buttons near the bottom of the middle pane directly left of the map window. If you are in "Fill" mode you might need to click and drag to place the object, and if you are in "Select" mode you won't be able to place it at all.

Note 3: The object list displays the PATH but not the NAME. Once placed on the map you will see something's name when you right click on it. If done correctly both kinds of meta objects (for ships) or the meta object we place on the overmap (for stations and asteroid bases) should be the same dimensions and sprite as our ship when it appears on the overmap. The meta object we place in the map files for stations and asteroids should just appear as a blue cross.

5a. Final steps for ships

(i) In the bottom left corner of EACH MAP FILE, place exactly one of that meta object we defined in the code in step 4b (/obj/effect/zlevelinfo/ship/my_ship which you should have renamed).

(ii) In the top map file (the highest on the list) right click on the meta object we just placed, open up the dropdown list and select "Edit..." then scroll down to where it says use_me_to_initialise in the left hand column. Change the value on the right to 1. This doesn't strictly need to be done on the top map file but it should only be done on exactly one of them.

(iii) Finally open up the map __overmap.dmm and place a /obj/effect/overmapobj/ship then rename it to exactly the same name as the meta info object we created in step 4(b) and placed down in 5(a)(i). To change the name, right click on it and select "Edit..." then scroll down to where it says "name" in the left column. Put the name into the corresponding box in the right column. Remember the coordinates on the overmap where you placed it, then tick the map files to include them in the DME (note: this should only be done for testing). Delete the object from the overmap after you have finished testing it.

5b. Final steps for stations/asteroids

(i) In the bottom left corner of EACH MAP FILE, place exactly one of /obj/effect/zlevelinfo and name it the same as the meta info object we created in step 4© (note: the NAME not the TYPE). To change the name, right click on it and select "Edit..." then scroll down to where it says "name" in the left column. Put the name into the corresponding box in the right column.

(ii) In the top map file (the highest on the list) right click on the meta object we just placed, open up the dropdown list and select "Edit..." then scroll down to where it says use_me_to_initialise in the left hand column. Change the value on the right to 1. This doesn't strictly need to be done on the top map file but it should only be done on exactly one of them.

(iii) Finally open up the map __overmap.dmm and place a /obj/effect/overmapobj then rename it to exactly the same name as the meta info object we created in step 4©. To change the name, right click on it and select "Edit..." then scroll down to where it says "name" in the left column. Put the name into the corresponding box in the right column. Remember the coordinates on the overmap where you placed it, then tick the map files to include them in the DME (note: this should only be done for testing). Delete the object from the overmap after you have finished testing it.

5c. Final steps for shuttles

Shuttles should simply be placed into a pre-existing ship or station (ie one of the hangars in the cruiser map) and they're good to go (make sure your map cursor is set to "Add" mode).

6. Running the code and testing your thingy

Recompile and run your code after editing the map. If you are testing a shuttle, just go to where you put it in the cruiser map. Otherwise steer the cruiser to the coordinates you placed your ship on the overmap, jetpack over and start exploring or flying it around. A little creative adminghosting, adminporting and/or var-editing will get you there much faster, or you can place player spawn markers onto your ship and spawn there at round start (a little bit more complex).

Revisit any of the previous steps to modify or tweak things as needed. This is a long and complex guide so if you have any issues come to me for help. And if you find any bugs or think something is broken, go ahead and create an issue on github to get it addressed! There are also a few tweaks which I need to do which will simplify some stuff like step 5.

In total this guide is 3.5 hours, 3447 words, 265 lines and 7 standard drinks worth of Sailor Jerry's Caribbean Spiced Rum.]]>
1. Decide the kind of ship or station you want to make, its size and its purpose. For performance reasons we want to minimise the number of things using 2 or more zlevels (separate decks) by themselves but don't be afraid to make something bigger if you want to. Engines are props and there's no other ship mounted machinery like weapons, comms antennae, sensors etc at the moment but leave space for them as they'll get added eventually. Covenant turfs aren't in the code yet so stick to human ships. Space stations and asteroid bases are basically the same as capital ships but a little bit simpler. In the code stations and asteroid bases are treated identically. Anything larger than 20x20 must be either a capital ship or station (not a shuttle) and can use one or more zlevels.

2. Map the internal layout. Size guidelines for some possible ship/shuttle types are:

- Small shuttle, dropship, personnel lighter, escape pod: up to 6x6 tiles (shuttle class)
- Large shuttle, tug, gunboat, heavy dropship, small yacht: up to 20x20 tiles (shuttle class)
- Stealth vessel, light freighter, transport ship, patrol boat, sub-prowler/sub-corvette, luxury yacht: 1 zlevel (capital class)
- Corvette, light frigate, medium freighter, personnel transport: 2 zlevels (capital class)
- Frigate, light destroyer, heavy freighter, refinery ship: 3 zlevels (capital class)
- Destroyer, heavy frigate, light cruiser, light carrier, colony ship: 4 zlevels (capital class)
- Heavy cruiser, carrier: 5 zlevels (capital class)

Space stations and asteroid bases can be anywhere from 1-5+ zlevels depending on their purpose. Shuttle class ships are able to physically move around inside and dock with capital class ships. We can theoretically make shuttles up to around 50x50 or larger, but any larger than 20x20 and gameplay/performance issues crop up. There are also specific turfs you need to use for shuttles. Capital class ships and space stations occupy entire zlevels and have static layouts. On the overmap both type of ships work near identically but should be given different sized sprites to represent their size difference. Place a minimum 50 tile margin of empty space around the edge of anything occupying one or more zlevels.

Map your shuttles facing north (up) and map your capital ships facing east (right). Don't ask me why because I was probably drunk at the time. I might get drunk and make them the same someday but forget to tell anyone so all the ships suddenly start flying sideways. Spacestations and asteroids can do whatever they want. Make sure that the map z dimension is always 1 and split separate decks off into separate mapfiles labelling then myship-1.dmm myship-2.dmm etc.

2(a). Shuttle specific stuff

The shuttle code requires that the only turf type used internally are of type /turf/simulated/shuttle/hull (for the shuttle) and /turf/unsimulated/blocker (for any empty space around it). To achieve a desired visual effect, you will need to modify the icon and icon_state of the turf in the map editor to match what you want. To do this right click on the turf, go to the dropdown for it and select "Edit..." then scroll down to where it says icon in the left column. In the right column enter the path of the icon you want to use inside single brackets (eg 'icons/turf/space.dmi') then press "OK". Go to the edit menu again, and this time scroll down to where it says icon_state in the left column and put the name of the icon state you want in the right column in double brackets (eg "plating"). To find a list of possible turf sprites to use, navigate to icons/turf inside Dreammaker.

For floor turfs (ie are non-dense and non-opaque) use /turf/simulated/shuttle/hull/floor and for windows (dense and non-opaque) /turf/simulated/shuttle/hull/window the parent hull type /turf/simulated/shuttle/hull function as walls (dense and opaque). Don't worry about maglocks, they don't use specific turfs for now.

Do not map out any areas, but make sure you place exactly 1 APC somewhere (SMES and cabling are optional but there if you want them) and at least 1 /obj/machinery/computer/shuttle_helm to fly the shuttle. Lighting is also required, and you can use ordinary airlocks as normal to divide internal cabins and rooms. Place some /obj/machinery/door/airlock/external/shuttle to allow players to enter and exit the shuttle while it is in flight (not maglocked). Putting the machinery for a cycling airlock is not necessary as most shuttles will be flying to and from hangars or planets with atmosphere, but you can do it if you want (eg for a salvage or SAR shuttle).

The map file containing this layout should use the exact same dimensions. Eg if your shuttle is 12x15 then the map should be 12x and 15y.

Nothing other than shuttles should use these turf types.

3. Get an overmap sprite for your ship or station

Shuttles: the sprite should be around 16x16 from one end to the other (use a standard 32x32 dmi size) with a little bit of leeway either size (eg you could do a 10x10 or 20x20 sprite). Create it as an state in code\modules\overmap\overmap_vehicles\icons\overmap_vehicles.dmi and call it whatever you want but remember it for the next step (4). Make sure the sprite is facing north and don't bother creating directional states.

Capital ships or space stations: The overmap sprite should be 32x32 for things that are 1 full zlevels, 64x64 for things that are 2 full zlevels, 96x96 for things that are 3 zlevels, 128x128 for things that are 4 or more zlevels. Also include icon states for thrusting and braking (reverse thrust). For the dimensions larger than 32 you will need to use an external editor then import it into Dreammaker, I recommend Paint.NET as it's free, small and fast but with loads of features. Place it as a new icon inside the folder code\modules\overmap\ships and name the icon states "base" "thrust" and "brake" for ships. Make sure all 3 icon states exist (if ship), but just reuse the base sprite if you don't have the extra ones. Make sure the sprites are facing north and don't bother creating directional states. 32x32 station sprites can go into code\modules\overmap\ships\sector_icons.dmi or just as new icons into code\modules\overmap\overmapobj (sorry it's a little bit disorganised). Remember the icon name and icon_state for the next step (4a and 4b and 4c).

3(a). Shuttle top-down sprites

The top-down sprite is used for the shuttle when it is in flight (eg docking with or leaving a hangar) and the dimensions need to match the full pixel dimensions of the internal layout so an external editor is required. To calculate the size required, count the x width and y-height of the shuttle excluding any empty space then multiply by the standard Byond turf size of 32x32. For example, a shuttle that is 5 turfs wide and 10 turfs high will need a top-down sprite with dimensions 160 (5 x 32) by 320 (10 x 32).

Once you figure out the required dimensions either obtain the services of an artist or map out the "roof" in Dreammaker using whatever turfs you like then take a screenshot and scale/crop it to the required proportions. Place the image into its own DMI (ensuring it is facing north) and call the icon state "shuttle". Call the icon itself whatever you want, but remember it for the next step (4a).

3(b). Sensor HUD images

Everything the size of a fighter or larger needs a unique sprite to quickly identify it when it pops up on a player's sensor HUD. The sprite should be 32x32 and grayscale (because it is coloured in according to its faction or light blue for environmental stuff like asteroids and stars). Place the sprite in code\modules\overmap\overmap_vehicles\icons\overmap_vehicle_hud.dmi and name it whatever you want but remember it for the next step (4).

4(a). Implementing shuttles in code

Open up code\modules\overmap\overmap_vehicles\instances\shuttles.dm then scroll down to the bottom of the file and copy paste the following code at the end:

Code:
/obj/machinery/overmap_vehicle/shuttle/my_shuttle_path
   name = "My Awesome Shuttlecraft"
   desc = "For transporting Super Cool Dudes while making spacey noises with your mouth."
   icon = 'code/modules/overmap/overmap_vehicles/shuttles/my_shuttle_icon.dmi'
   overmap_icon_state = "unsc_shuttle"
   maglock_strength = 8
   bound_width = 192
   bound_height = 384
   layout_file = 'maps/ships/my_shuttle_layout.dmm'
   layout_x = 6
   layout_y = 12
   iff_faction_broadcast = "UNSC"
   hull_remaining = 250
   hull_max = 250
   armour = 75
   maglocked_at_spawn = 0

We will now edit some lines to customise this code. Some lines are optional and if they aren't changed then they can be deleted to make the code a little cleaner. We'll go through the lines one by one.

Code:
/obj/machinery/overmap_vehicle/shuttle/my_shuttle_path

Change my_shuttle_path to whatever you want but keep it reasonably simple and only use lower case letters and underscores (eg colonial_salvage_shuttle).

Code:
   name = "My Awesome Shuttlecraft"
   desc = "For transporting Super Cool Dudes while making spacey noises with your mouth."

Change these to whatever you want. This is what the players see when they mouse over or examine the shuttle.

Code:
   icon = 'code/modules/overmap/overmap_vehicles/shuttles/my_shuttle_icon.dmi'

Change this to the icon containing your top down sprite you made in step 3(a).

Code:
   overmap_icon_state = "unsc_shuttle"

This should match the icon_state of the overmap icon you made in step 3.

Code:
   maglock_strength = 8

This is the number of adjacent or overlapping walls and floors required to "maglock" or dock with a capital ship. Pick the side you want to use to dock (usually the one with airlocks in it) and this number should be slightly less than that. Eg if the sides of your shuttle are 8 tiles high then the maglock strength should be 6.

Code:
   bound_width = 192
   bound_height = 384

This should be changed to the exact dimensions of the top down sprite.

Code:
   layout_file = 'maps/ships/my_shuttle_layout.dmm'
   layout_x = 6
   layout_y = 12

Change the layout file to be the map file containing your layout, and make sure the layout_x and layout_y match the map dimensions.

Code:
   iff_faction_broadcast = "UNSC"

Optional: Determines the faction alignment for sensors. Available options are "UNSC" "Insurrection" "Covenant". Probably just leave this as UNSC for now because the Insurrection aren't in a habit of broadcasting their presence.

Code:
   hull_remaining = 250
   hull_max = 250
   armour = 75

Optional: hull_remaining and hull_max should be set the same and represent the overall health of the shuttle. armour functions as damage mitigation and anything that deals less damage than this value is ignored. If something deals more damage than the armour value then hull is removed according to the function hull_remaining -= damage / armour means something that deals the same amount of damage as the shuttle has armour will only remove 1 point of hull. Be sensible and look at existing values to balance this. If you're in doubt then don't change it.

Code:
   maglocked_at_spawn = 0

Optional: determines if the shuttle spawns in as maglocked (docked) at the start of the game.

4(b). Implementing capships in code

Open up code\modules\overmap\ships\unique_ships.dm then scroll down to the bottom of the file and copy paste the following code at the end:

Code:
/obj/effect/zlevelinfo/ship/my_ship
    name = "UNSC Derpaderp"
    desc = "For a brick it flies pretty good."
    icon = 'code/modules/overmap/ships/my_ship_icon.dmi'
    faction = "UNSC"
    init_bounds_dims = 96
    use_me_to_initialise = 0
    sensor_icon_state = "7th_column"

We'll break it down line by line. Sensors are definitely working but leave speed and acceleration etc alone again for now.

Code:
/obj/effect/zlevelinfo/ship/my_ship

Change my_ship to something simple and clear and only using lowercase letters and underscores.

Code:
    name = "UNSC Derpaderp"
    desc = "For a brick it flies pretty good."

What the players see. Remember that UNSC specifically refers to navy ships (including ONI). For civilian ships use CAA (Colonial Administration Authority), UEGS (United Earth Government Ship), your own made up acronym or nothing at all. The desc should be describe it's origins and purpose while being informative and short.

Code:
    icon = 'code/modules/overmap/ships/my_ship_icon.dmi'

Change this to the icon you made in step 3.

Code:
    faction = "UNSC"

For sensor faction purposes. Available values are "UNSC" "Insurrection" "Covenant" but again best left as "UNSC" for now.

Code:
    init_bounds_dims = 96

Set this to the dimensions of your overmap sprite (which should be square).

Code:
    sensor_icon_state = "7th_column"

Set this to the icon_state you created in step 3(b).

Code:
    use_me_to_initialise = 0

This is a magic number and should be kept as 0. We'll look at it in step 5a.

4©. Implementing stations and asteroid bases in code

These are the simplest to do. Open up code\modules\overmapobj\unique.dm (it might not exist and need to be created). Scroll to the end and copy paste the following code:

Code:
/obj/effect/overmapobj/my_station_thingy
    name = "a station or something"
    desc = "a thingy"
    icon = 'code/modules/overmap/ships/sector_icons.dmi'
    icon_state = "mysprite"
    faction = "UNSC"
    init_sensors = 1
    sensor_icon_state = "mysensorsprite"

Then we gonna edit some lines.

Code:
/obj/effect/overmapobj/my_station_thingy

Change to something short with only lowercase and underscores.

Code:
    name = "a station or something"
    desc = "a thingy"

What the players see. Do something descriptive.

Code:
    icon = 'code/modules/overmap/ships/sector_icons.dmi'
    icon_state = "mysprite"

Change this to the icon and icon_state you created in step 3.

Code:
    init_sensors = 1

Keep this line and make sure it is set to 1. ~~magic~~

Code:
    faction = "UNSC"

This is for sensor alignment colour. Available options are "UNSC" "Insurrection" "Covenant" but you can also set it to any random value and it will stay in grayscale.

Code:
    sensor_icon_state = "mysensorsprite"

This should match the icon_state you created in step 3(b). Sensors might not setup correctly at the moment but remind me to fix it because it's probably just a quick tweak.

5. Final steps - testing (read this for shuttles, ships, stations, asteroids)

Press control+k or choose Build -> Compile (from the top menu list). Shuttles can skip the rest and go directly to 5c

What we need to do now is to make sure the map files are loaded correctly by the code. When they are loaded should be handled by the code (ie the gamemode or whatever code spawns your thing in midround) but we need to do some final stuff to determine how they are loaded. Compile the code and open up each of the map files for your ship or station. If there are any errors double check you have copy pasted the code correctly. In step 4 we defined a metaobject which contains the information on how to properly load, create and initialise our ship or station. Ships and stations/asteroids are done slightly differently (eventually I'm going to make them the same which will simplify this a bit). In order to initialise both and spawn them on the map for testing we need to place a specific meta info object on each of the map files for our thing then place a different kind of meta info object into the overmap at the coordinates we want it to spawn in for testing.

Note 1: If you can't find it in the object list then remember to click the + for each / in the type path and explore until you find it (make sure you have compiled at the start of this step).

Note 2: If you are having trouble placing one of the meta info objects make sure your placement cursor type is set to "Add" (an icon of a filled in box with a plus side in the top right corner) which is the leftmost of 3 buttons near the bottom of the middle pane directly left of the map window. If you are in "Fill" mode you might need to click and drag to place the object, and if you are in "Select" mode you won't be able to place it at all.

Note 3: The object list displays the PATH but not the NAME. Once placed on the map you will see something's name when you right click on it. If done correctly both kinds of meta objects (for ships) or the meta object we place on the overmap (for stations and asteroid bases) should be the same dimensions and sprite as our ship when it appears on the overmap. The meta object we place in the map files for stations and asteroids should just appear as a blue cross.

5a. Final steps for ships

(i) In the bottom left corner of EACH MAP FILE, place exactly one of that meta object we defined in the code in step 4b (/obj/effect/zlevelinfo/ship/my_ship which you should have renamed).

(ii) In the top map file (the highest on the list) right click on the meta object we just placed, open up the dropdown list and select "Edit..." then scroll down to where it says use_me_to_initialise in the left hand column. Change the value on the right to 1. This doesn't strictly need to be done on the top map file but it should only be done on exactly one of them.

(iii) Finally open up the map __overmap.dmm and place a /obj/effect/overmapobj/ship then rename it to exactly the same name as the meta info object we created in step 4(b) and placed down in 5(a)(i). To change the name, right click on it and select "Edit..." then scroll down to where it says "name" in the left column. Put the name into the corresponding box in the right column. Remember the coordinates on the overmap where you placed it, then tick the map files to include them in the DME (note: this should only be done for testing). Delete the object from the overmap after you have finished testing it.

5b. Final steps for stations/asteroids

(i) In the bottom left corner of EACH MAP FILE, place exactly one of /obj/effect/zlevelinfo and name it the same as the meta info object we created in step 4© (note: the NAME not the TYPE). To change the name, right click on it and select "Edit..." then scroll down to where it says "name" in the left column. Put the name into the corresponding box in the right column.

(ii) In the top map file (the highest on the list) right click on the meta object we just placed, open up the dropdown list and select "Edit..." then scroll down to where it says use_me_to_initialise in the left hand column. Change the value on the right to 1. This doesn't strictly need to be done on the top map file but it should only be done on exactly one of them.

(iii) Finally open up the map __overmap.dmm and place a /obj/effect/overmapobj then rename it to exactly the same name as the meta info object we created in step 4©. To change the name, right click on it and select "Edit..." then scroll down to where it says "name" in the left column. Put the name into the corresponding box in the right column. Remember the coordinates on the overmap where you placed it, then tick the map files to include them in the DME (note: this should only be done for testing). Delete the object from the overmap after you have finished testing it.

5c. Final steps for shuttles

Shuttles should simply be placed into a pre-existing ship or station (ie one of the hangars in the cruiser map) and they're good to go (make sure your map cursor is set to "Add" mode).

6. Running the code and testing your thingy

Recompile and run your code after editing the map. If you are testing a shuttle, just go to where you put it in the cruiser map. Otherwise steer the cruiser to the coordinates you placed your ship on the overmap, jetpack over and start exploring or flying it around. A little creative adminghosting, adminporting and/or var-editing will get you there much faster, or you can place player spawn markers onto your ship and spawn there at round start (a little bit more complex).

Revisit any of the previous steps to modify or tweak things as needed. This is a long and complex guide so if you have any issues come to me for help. And if you find any bugs or think something is broken, go ahead and create an issue on github to get it addressed! There are also a few tweaks which I need to do which will simplify some stuff like step 5.

In total this guide is 3.5 hours, 3447 words, 265 lines and 7 standard drinks worth of Sailor Jerry's Caribbean Spiced Rum.]]> <![CDATA[Open Alpha: ETA Soon TM (the final crunch!)]]> https://projectunsc.org/forum/showthread.php?tid=204 Wed, 24 Feb 2016 13:35:35 +0000 Cael_Aislinn]]> https://projectunsc.org/forum/showthread.php?tid=204
I don't wanna put a date on it but we're looking at late next week for the earliest and probably a fortnight or so on the outside.]]>
I don't wanna put a date on it but we're looking at late next week for the earliest and probably a fortnight or so on the outside.]]>