Reason: TICKLAG var is set too high.

In ./config/config.txt
Set:
TICKLAG 0.5
TICKCOMP 1

However, I am unsure of its effects on the game tickrate, might make things process faster.

However, if movement is too fast/slow,
Tweak in ./config/game_options.txt

These values get directly added to values and totals in-game. To speed things up make the number negative, to slow things down, make the number positive.
RUN_SPEED
WALK_SPEED

Some multitile airlocks are meant to be transparent, but the opaque ones can actually be seen through. I think this is a Byond issue as the main atom turf correctly blocks visibility, but all others don't. Needs testing.

data_net tag needs to be set for the components, and a datanet console added to control it

When you are in a fighter and your overmap coordinates match your sector coordinates, a big fighter image will appear on the overmap flying along as though the overmap were a sector. This image is visible only to the pilot (maybe passengers as well?).

I've tried to debug this one but I'm stumped. It's probably got to do with the way byond handles client views, and suggests I need to rethink then retool look-out-to-space verb.

This is technically covered in #148 but it's major enough to warrant it's own issue.

We have an existing reactor, but the mechanics don't fit with the sprites so we may as well tweak the functionality to make a slightly different one. It will be interesting to have a couple of different methods of power generation. The one for this issue will probably be independant of a much larger multitile central reactor I'm planning to add later.

Docking via an extendable airbridge between capital ships, or capital ships and stations.

Doesn't need to be anything fancy, just a bunch of empty rooms and some lights or passages. In theory players could use it as well, but we'll need to setup a few other things before playable civilian roles are a thing.

The quality of some of the lobby music is being affected by its high volume. In loud parts of the music, there is audible clipping.

Fix: Get better music samples.

Issue discovered on overmap-controller just after merging #13

The ship covered 4 zlevels and was entirely sealed (the top floor is just plating and formed the "roof") except for a 2x2 doorway on the highest indoors level which led to a shuttle. The shuttle didn't have a roof, and was consequently vented (correct behaviour for both, individually). This meant there was 10 tiles inside the shuttle, all adjacent to space (above).

What happened: When the airlock to the shuttle was opened, the main ship drained very slowly (about 0.05 moles per second, or 0.5 kPa).

Expected behaviour: the main ship should have drained much faster, perhaps at a rate of 5-25 kPa per second.

Note that this may not be a bug, just the ZAS settings not being set appropriately.

As title.

• Miscellaneous HUD buttons need to have generalised layouting so they aren't all individually positioned.
• All overmap_vehicles use the same HUD... vehicles without weapons (like shuttles) need to have the various weapons and weapons fire HUD elements removed.
• Setup starting loadouts for Sabres and Pelicans
• Ensure the HUD works ok with the loadouts for Sabres and Pelicans.

Roundstart code that picks a random squadron name and logo then applies it to all UNSC pilot players, longswords, pelicans and miscellaneous other stuff like noticeboards, uniforms and propaganda.

eg "209th Hellcats" with the logo of an angry bobcat
"45th Flying Tigers" with the logo of a tiger prowling in the jungle
"174th Red Aces" with the logo of an ace of hearts.

Basic shuttles with a couple of basic NPCs to randomly fly around the system and look busy. They don't need to do anything more.

I probably set the ammo type to the wrong thing or something. If someone could take a look at it that would be great!

Simple 1-2 deck ships with basic NPCs that randomly fly around "pretending" to ship materials between colonies, space stations and other star systems.

Eek. Thankfully this won't affect many players. It's likely the issue is caused by or related to how I implemented vehicle HUDs so that would be a good place to look first.

This one should be a smallish one. Weapons currently consume ammo, but there's no way to resupply them apart from actually replacing the weapon so there needs to be an external loading machine which can do that.

Fuel consumption also needs to be added whenever the vehicle thrusts, and possibly also a way of tracking power usage/storage/consumption. An idea I had for fusion fuel cores was that they would function as a sort of "battery" for fighters, giving a big dose of power for as long as they last. A machine needs to be added to refuel fighters, and possibly a way to charge up batteries as well.

Extension of the issue: #137

Movement isn't choppy anymore, but diminishing the TICKLAG makes movement slower.

Tweak:
RUN_SPEED
WALK_SPEED

Change those values until there is an appropriate speed.

As title. This should be fairly quick, the UI is quite simple.

These can be filled with placeholdery type rooms and content. All they need are a few rooms with magic lighting, infinite power and basic NPCs so that other NPCs can fly up and dock to 'pretend' to trade, or hang around in the bar "chatting."

Missing gear/errors with medic class spawn.

As title.

Thanks to Discord for the tips:

Just north of auxiliary reactor 2
http://prnt.sc/dlp178
https://gyazo.com/173c36be41a74ba0b770679874300d18

In the main corridor south west of tcomms
http://prnt.sc/dlp39z

SMES feeder array adjacent to auxiliary reactor 1
http://prnt.sc/dlp9sp
This last one is odd. In dreammaker it appears to be mapped correctly, but apparently power wasn't flowing and it got fixed after the corrections were made in that screenshot. Needs testing

As title.

I'm not 100% about reproducing this, but I believe it happens when you get inside the spacetravel zone around the edge of a map.

Due to the speeds involved in cruise engines and the way atoms cross over zlevels, I think the ideal way to fix this is splitting off fast travel from sector travel by removing cruise engines and preventing sector view when in fast travel mode.

I noticed some major issues with capship flight a few months and forgot about them. Gotta test them and make sure control is working and the mechanics aren't bugged. Also todo: mock up UI designs for helm control, fighter control, gunnery control.

This is probably related to the old bug of firing weapons in the armoury locking up the server. Todo: grab the proper bay12 fix for proc/visible_message instead of the tempfix I put in a while back.

When I integrated tcomms with overmap, I didn't add in the ability for players to cart around radio relays so they can use their comms in places outside their some base sector. This is a fairly big thing.

For marines they have the signalmen, who will get a backpack tcomms relay. To sabotage it just kill him or get him to drop it, then disable it.

For insurrectionists, they will have portable relays on their shuttles.

I haven't done a full testing pass to work out all the issues here, and the actual traversal code is a yucky spaghetti else-if chain. Notes:

• Stairs work fine in normal use cases (mapped properly, nothing blocking either end with mobs just moving as normal).
• Ladders work fine when manually clicked on (from either end).
• Travel upwards/downwards verb works as expected for stairs and ladders.
• Ghosts using travel upwards/downwards appear to be incorrectly blocked by floors.
• The traversal code is messy
• Overmap vehicles appear to be working correctly in the standard use cases (might need more testing).
• Stuff placed at the top of stairs isn't bumped when someone tries to move up it (ie, open an airlock at the top of stairs). After trying and failing to do this, the travel upwards verb no longer works.
• Players can move up and down zlevels if there is open space.

As title. Not technically a bug just something I forgot.

Falling down the shaft can potentially put players in crit. Especially important for playtests, and given there's no actual elevators.

As the jobs are all pretty new, and most of the jobs are partially unimplemented or actually don't have anything to do, we should setup a small blurb for round start and player memory which explains to them their basic duties (if they have any).

There might be some tweaks made to iron out fighter movement, and we also need to do loads of testing on dogfighting. I'd like to build up a bit of a fun meta around which loadouts are effective, so different weapon types need to be bugtested and ensure they all work.

Looks like there are some signfiicant unhandled edge cases for the look-out-to-space verb so that sometimes, the client view will actually get locked to the overmap object and not return to the mob properly. Cancel-camera-view verb also has a slight delay when being used sometimes, as opposed to when it's being used in other SS13 instances.

The verb probably needs to be rewritten to be more robust and more safely handle resetting to the mob.

Just a small NPC crewed ship which patrols around the sector checking for smugglers or pirates. Only needs 1 zlevel as well as some placeholder rooms.

What's supposed to be happening is a shaded underlay of the turf on the level below is applied, but instead the open turf just has a pitch black overlay. This appears to be an issue with lighting (note possible fix in #16).

The Marine armor sprites are still using the outdated ones, we have newer ones made by firestorm.

As title. There's a reaaaaally long stretch of corridor.

Several things placed on the map use standard SS13 access perms which are not granted to UNSC players so those (either perms added or restrictions stripped, most likely through code):

• Welding and electrical supplies secure closets in main engineering.
• APCs
• Security lockers in the NavSec compound
• Gun lockers in the armoury
• ID computer (not placed on map yet...)

Seems that your view doesn't update at all if you're using the latest 510. I got stuck on a white screen that was called "flash" twice, and one other time I got an actual view of the game but it didn't update when I moved.

Just do eeet, it's long overdue. Events are far too tied into the old Bay12 map setup and would all need to be individually rewritten.

I've done the base of the map, what it needs

Atmos

Power that isnt just a godcell, and that reaches all Z levels

Maybe some tweaking needed, but meh

Boop

Overmap turrets are purely cosmetic, the bullets don't actually do anything. Code needs to be written for overmap traversal so that the projectiles can actually be seen fired from the ship, travel to other ships/overmap objects, then collide and do damage.

Subclasses of the turret also need to be setup for other capship weapon types like archer/ares missiles and the MAC Cannon etc.

Just a simple map 1 zlevel map with a few placeholder rooms and small hangars. The idea is that this one acts as a sort of mobile base by flying out to asteroid fields with shuttles and EVA pods so that miners can harvest minerals and drop them off back here. Then when it's full or a shift ends, the hauler flies back to a trade station to sell or drop off the minerals.

Attempting to walk up one of the stairwells near the arrivals shuttle greets you with an invisible wall and a message saying your way up is blocked by stairs. This might be a map issue.

These could be based off /overmap_vehicle /mech or even the B12 vehicles (the latter is probably best).

Drivable ground vehicles won't be needed until the Colony feature arc but the sprites are there and it will probably be easy to code in.

... into a sad little pile of metal and glass.

We don't want copycats to be confused with us for the official HS13 server, and also we want to make sure we're distinctive from the default Bay12 blurb.