Suggestion: A Remotespy Thing

[NOTGodlynoah]

Suggestion: Persistent Remote Logging Toggle

Add a toggle called "Keep Remotes" or "Persistent Logging" to the RemoteSpy window.

Currently, when a remote function/event or its parent gets destroyed or set to nil, the logged data becomes inaccessible. If you try to generate a script for a remote that was destroyed after being fired, you lose that information.

Solution:
When "Keep Remotes" is enabled, RemoteSpy should:

1. Cache remote data immediately when a remote is first detected/fired
2. Store the complete remote information (name, parent path, arguments, etc.) in memory
3. Keep this cached data accessible even after the original remote object is destroyed
4. Allow script generation from cached data, so you can still generate scripts for destroyed remotes

Example:

• Remote fires → gets logged in RemoteSpy
• Remote is instantly destroyed by the game after use
• With this feature: You can still click on the cached entry and generate a working script
• Without this feature: The remote entry becomes unusable/errors out

This would be especially useful for games that dynamically create/destroy remotes or have anti-debugging measures that clean up/recreate remotes after use, OR remotes that delete a object, but all the objects are named the same thing in a folder, its really annoying to have to figure that out myself.