A common speedrunning tactic in Doom is to straferun into an object just out of reach to pick it up. Like Doom, hitboxes in System Shock are interesting to say the least. For the split second that the player’s camera hitbox is through the plane, you can see through a plan and even see unrendered parts of the map (which the game calls Inky Blackness).

For instance if you’re going very fast horizontally then add in a vector from uncrouching as you hit a plane your physics start to get a little weird because the game code doesn’t account for an action like that, and you get thrown (partly) through the plane you ran into. Because of this, the game takes a few shortcuts when calculating things so that it would run faster on computers from 1994.

System Shock is 2.5D, as in not 2D, but not fully 3D (like Doom, but more advanced and with Tiles instead of Sectors). Well, if you run into a 2D plane with something on the other side while crouching at high speed, uncrouch as you are about to collide with the plane, then save, you bump through the other side.Īs for why this works, I need to dive into the game engine.

The purpose of my keybinds is to make my save creations as fast as possible (pressing Y, Down Arrow, then Enter). System Shock: Enhanced Edition adds a few new features to the base game such as native mouselook, custom resolutions, and custom keybinds.įor the sake of transparency, here are my (relevant) custom binds:Īdditionally, I have Y bound to Mouse 5, Down Arrow to Mouse 4, Enter to Mouse 3, Shift+Tab to Scroll Up, and Tab to Scroll Down through Razer’s proprietary software that comes with their DeathAdder 2013.Īs you can see, I mostly play with Default (Classic) controls, with a few key differences, mainly that a few keys are easily accessible at all times. Shoutouts to itsubitsu for finding save clips and Fearful Ferret for competing and pushing me to get sub 11:00.

System shock 1 codes