Is your feature request related to a problem? Please describe.
I am frequently finding when using this to reverse engineer Grime 2 that I know how to find a monobehavior for an item, but actually need to know where the item is given. The best I can find to do this is to first search for the item, then copy the path ID, then use the search bytes/search by content tool to look for that path ID. However there are 2 practical issues with this which make this approach cumbersome:
- There is not a way to open the results of this search into the inspector view. For example, if I find there is a reference from GamePlay_ObjectAbsorbHandler, I have to go and search for that, which will yield many results and then I have to skim manually to find the right path ID returned from the search result
- To my understanding, path IDs can be reused between asset files/bundles; in other words, a search by the path ID can return results other than PPtrs directly referencing the object.
Describe the solution you'd like
My ideal solution would be if I can right-click an entry in the main tab area and see a "find references" button, which will open a new tab performing a search for any PPtrs that directly reference the selected object. I believe this would involve the implementation of "search by PPtr" (I am not aware of whether there are technical limitations that can prevent this from working as desired but am open to discuss alternatives) and a new tab style to support such a search, since the normal search bar will not work here.
The second best solution would be to offer a way to open the results of search by content into the inspector, though I think this is less convenient because of the extra steps needed to copy the path ID and open the tool window, along with reason (2) above.
I would be open to work on a PR this, or something functionally similar to the extent that is technically possible to accomplish.
Additional context
Here's screenshots of the specific example of the problem I gave above:
Is your feature request related to a problem? Please describe.
I am frequently finding when using this to reverse engineer Grime 2 that I know how to find a monobehavior for an item, but actually need to know where the item is given. The best I can find to do this is to first search for the item, then copy the path ID, then use the search bytes/search by content tool to look for that path ID. However there are 2 practical issues with this which make this approach cumbersome:
Describe the solution you'd like
My ideal solution would be if I can right-click an entry in the main tab area and see a "find references" button, which will open a new tab performing a search for any PPtrs that directly reference the selected object. I believe this would involve the implementation of "search by PPtr" (I am not aware of whether there are technical limitations that can prevent this from working as desired but am open to discuss alternatives) and a new tab style to support such a search, since the normal search bar will not work here.
The second best solution would be to offer a way to open the results of search by content into the inspector, though I think this is less convenient because of the extra steps needed to copy the path ID and open the tool window, along with reason (2) above.
I would be open to work on a PR this, or something functionally similar to the extent that is technically possible to accomplish.
Additional context
Here's screenshots of the specific example of the problem I gave above: