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
  • #12779
Closed
Open
Created Dec 14, 2016 by Rob Nelson@N3X15Maintainer5 of 5 tasks completed5/5 tasks

Having high ping makes precise movement impossible

Created by: BobdaBiscuit

Just a note this is most likely bad latency handling on byond's part and not /vg/station, but I'll make this incase there's some autism that can be done.

Description of issue

With high (130+) ping it becomes impossible to move a single tile at a time, instead a single keypress moves you 2+ tiles.

Difference between expected and actual behavior

Expected:

  • tap key
  • move 1 tile

Actual:

  • tap key
  • move 2 tiles, get launched into space during spacewalks etc etc

Steps to reproduce

  • Have shit internet, play videogame.

Specific information for locating

N/A

Length of time in which bug has been known to occur

N/A

Server revision

2b12a40f

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