Skip to content
GitLab
  • Menu
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • vgstation13 vgstation13
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 1,627
    • Issues 1,627
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 44
    • Merge requests 44
  • Deployments
    • Deployments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • Repository
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • vgstation
  • vgstation13vgstation13
  • Issues
  • #12922
Closed
Open
Created Dec 19, 2016 by Rob Nelson@N3X15Maintainer1 of 1 task completed1/1 task

Firelocks no longer require access or crowbars to open

Created by: Blithering

Description of issue

Not sure if this was an intentional change, but firelocks blocking off breaches or fires (noted by the flashing lights) used to require crowbarring or engineering access to open, but recently just give the message 'you force the firelock open' when clicked on.

Difference between expected and actual behavior

Previously the safety feature at least slowed down peoples' attempts to open the zas nightmare Now we can all enjoy slamming into paper sheets and dying.

Steps to reproduce

make a breach so the station's firelocks close and theoretically lock. open one with the flashing alarm lights, Marvel as evolution has rendered the average greyshirt's hands equivalent to a crowbar.

Specific information for locating

Length of time in which bug has been known to occur

Please check whatever applies. More checkboxes checked increase your chances of not being yelled at by every contributor.

  • [x ] Issue could be reproduced at least once
  • [yes] Issue could be reproduced by different players
  • [checkbox] Issue could be reproduced in multiple rounds
  • [:^)] Issue happened in a recent (less than 7 days ago) round
  • Couldn't find an existing issue about this
Assignee
Assign to
Time tracking