[Feature Request] Examine Command - Add inspection of script and channel objects.
See original GitHub issueIs your feature request related to a problem? Please describe.
Scripts are currently undergoing an overhaul to be more focused on the fact that they are “global” objects and are great for storing of information on attributes and via tags. Unfortunately, there is no way to examine them in-game as you would other objects.
Describe the solution you’d like
The account object is examined via the *
modifier. I propose that examine also gain new options to modify the command when attempting to view both script and channel objects.
Examine Command
get detailed information about an object
Usage:
examine [<object>[/attrname]]
examine [*<account>[/attrname]]
Switch:
account - examine an Account (same as adding *)
object - examine an Object (useful when OOC)
The examine command shows detailed game info about an
object and optionally a specific attribute on it.
If object is not specified, the current location is examined.
Append a * before the search string to examine an account.
Issue Analytics
- State:
- Created 2 years ago
- Reactions:1
- Comments:6 (6 by maintainers)
Top Results From Across the Web
Inspect network activity - Chrome Developers
This is a hands-on tutorial of some of the most commonly-used DevTools features related to inspecting a page's network activity.
Read more >How to Use Your Browser's Inspect Element Tool to Edit ...
Learn how to use your browser's inspect element tool to check a webpage's HTML code. Also, edit and troubleshoot webpages locally with it....
Read more >How to Inspect Element: Simple Methods for Editing a Web ...
Inspect Element lets visitors access and temporarily edit a website's front-end source code, including its HTML, CSS, JavaScript, and image ...
Read more >Improve your code with lint checks
The lint tool checks your Android project source files for potential bugs and optimization improvements for correctness, security, performance, usability, ...
Read more >Debugging in Visual Studio Code
One of the great things in Visual Studio Code is debugging support. Set breakpoints, step-in, inspect variables and more.
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
One thing that would help with most of these alternating-table commands is switching the base class from MuxCommand to UnixCommand.
UnixCommand would let one specify the table using an optional, but mutually-exclusive argument group (defaulting to Objects). It’s much more flexible for commands like this which require context-- and if keyed to ContentTypes, could allow examination of literally any object (not just typeclasses!).
Custom models would be a hell of a lot easier to work with if they could be
examine
like any other object.Default commands are based on MuxCommand, so we won’t be starting to use a contrib style for those.
examine/scripts
works just as well and could be equally exclusive depending on implementation. And--economy.sales
is not a ‘unix’ style syntax anyway (at least not any I’ve ever seen), so if one wanted something arbitrary one could just as well do it asexamine/economy sales
or similar.