That won’t help with any of those things though. It’s merely a clipboard format that is used by construct to copy events. It’s not meant to be human readable or writeable.
The ids are mostly arbitrary although they are typically close to the name of things but they aren’t really useful to know at all as a human. They are used internally by construct to lookup actual names of things in whatever language mostly.
The manual and the event editor lists all the actions, conditions and expressions if you need a reference of what’s available.
Events are their own thing that don’t convert to a lower level language. Generally it’s similar to a traditionally typed language, but it also has a picking system on top of that which is rather unique. The manual explains how events work for the most part, but some actions or conditions can do their own thing that deviate from common behaviors.
Theres also JavaScript and typescript you can use to do basically what events do but in a different way. There isn’t always feature parity though. For example you’d have to do your own object picking in events or do a hybrid approach with events.
Advanced collaborators likely won’t care about whether you use code or events. All they care about is how things are meant to work and they can implement it in any way they fancy.