Open parseccentric opened 2 years ago
@Barasakar Here is some info on function callbacks that you might find helpful for understanding who is calling some teleportation functions. I wrote it like a task, but it's more of an FYI for now. I might take on this refactoring myself -- I am not sure yet.
Problem Inspector-assigned callbacks can make merging code difficult, because .unity and .prefab files are not human-readable. They can make navigating call stacks difficult, because Intellisense is not aware of things assigned in the Unity editor.
Proposed Solution
Workaround
Search the whole repository for the name of the function whose caller you are looking for. Note inspector-assigned callbacks in .unity and .prefab files.
More details
These are the inspector-assigned callbacks we currently have in the project: