Sounds great, thanks! I very much welcome any feedback on the Script Editor as I definitely want it to be as user-friendly as possible. One scenario I could see having a template or pre-defined logic block for would be "toggling" of states, for example a door opening and closing, since that is a common scenario. We can work together to determine what makes the most sense. :)
The "pending" path is something I am experimenting with and probably doesn't have much use at the moment. Basically, it makes a connection between two tiles, but doesn't allow any interaction or navigation initially - kind of like a "placeholder" connection. The intent is for it to become convenient for automating certain navigation based on the state of an object.
This path type will become much more useful once I add the functionality that will allow you to attach a script to a particular animation for an object. For example, you could create generic scripts for a door and attach them to the "open" animation and "close" animations. When "open" is triggered, the script could say update the path type between the tile that this door is on and the tile to the west of it to be "Walk and Interact", and when "close" is triggered, the script could say update the path type between the tile that this door is on and the tile to the west of it to now be "Pending". This would eliminate some of the need for giving unique IDs to tiles since you would have those pending paths and will be able to reference relative tiles (e.g. tile to the north, south, etc. instead of unique tile IDs to keep track of for each door). Hopefully I explained that well enough! Here is what it would look like visually:
It's still a work in progress at this point, so it may evolve or change to make it less confusing. :)