Skip to content
GitLab
    • GitLab: the DevOps platform
    • Explore GitLab
    • Install GitLab
    • How GitLab compares
    • Get started
    • GitLab docs
    • GitLab Learn
  • Pricing
  • Talk to an expert
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
    • Switch to GitLab Next
    Projects Groups Topics Snippets
  • Register
  • Sign in
  • openmw openmw
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributor statistics
    • Graph
    • Compare revisions
    • Locked files
  • Issues 833
    • Issues 833
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
  • Merge requests 34
    • Merge requests 34
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
    • Test cases
  • Deployments
    • Deployments
    • Releases
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Code review
    • Insights
    • Issue
    • Repository
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • OpenMWOpenMW
  • openmwopenmw
  • Issues
  • #5427
Closed
Open
Issue created May 22, 2020 by Kindi@KuyondoContributor

GetDistance unknown ID error is misleading

if we do

GetDistance "dagoth velos"

an "unknown id" error is thrown which is misleading because the id is actually valid(vanilla id). Apart from that, any script running a similar syntax will fail and stop executing thereafter. The command will return such errors when the object is not placed in the world yet.

This may be actually 2 issues, but there are suggested approaches here:

  1. To change "unknown id" to "object not found", and ignore that line in scripts.

  2. Execute it normally and return distance the same way as it is implemented for objects of different cells.

  3. Throw "object not found" warning, but still execute it using 2nd approach.

  4. Change the error message, but script will still stop executing.

On a side note, some other commands can throw similar misleading errors as well, such as gethealth, getpos, getangle etc..

Edited May 22, 2020 by Kindi
Assignee
Assign to
Time tracking