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
  • #9370

Closed
Open
Created Apr 10, 2016 by Rob Nelson@N3X15Maintainer3 of 5 tasks completed3/5 tasks

Vaults don't always respect the bounds of vault areas when spawning

Created by: Probe1

Description of issue

I removed a 60x60 chunk of vault10 on metaclubs z6. While testing my new area inside the 60x60 bounds, a syndicate vault spawned directly below it. The center of the vault was inside vault10 area but the top of it was well outside it and deleted a fair bit of my structure.

Difference between expected and actual behavior

When spawning a vault check to see if the edges are within bounds and to retry if not. Didn't check, spawned the top of a vault out of the vault10 area.

Steps to reproduce

Man this is such a bitch to reproduce that if I hadn't seen it happen while testing it wouldn't have been seen at all. Try deleting all vault areas and mapping in an area that is too small to fit a vault. That will probably provide a reproducible environ.

Specific information for locating

Length of time in which bug has been known to occur

Server revision

Issue bingo

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

  • Issue could be reproduced at least once
  • Issue could be reproduced by different players
  • 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