Can someone please do a complete ID string dump of ALL Construct 3 blocks? conditions, actions, beha

would be a cherry on top if there were a complete list of the event blocks ID in string format in the Manual.

Please, this would speed up my workflow and it's just too much to copy if creating the code-less event and then copy-pasting.

{"is-c3-clipboard-data":true,"type":"conditions","items":[{"id":"compare-eventvar"...

For all conditions, behaviors, and actions of all objects.

Thank you!!

Unique workflow. That’s probably the kind of thing you’d need to do yourself as you’ve noticed it’s very time consuming to do. Even if it could be done in an automated way, the possibility of renaming the type/behavior or variables in general would make it infeasible to do.

What you can do is create a project to copy from that you build as you go since there would be some actions and conditions used more than others. Overall that would let you try that workflow more and firsthand find pros and cons with it.

HA, yeah! Considering we probably don't have the same tools as the staff that work on the insides of Construct, it would be a very tedious & time consuming task. Which is why i'm hoping that someone in the staff could automate it and pull those id's, with much more ease, for their beloved customers :]

Why do you need this? It sounds like the kind of question which is better answered by changing your workflow so you don't need the answer to this question.

Hi Ashley,

the reason i'm asking is because i'm genuinely interested in understanding the underlying logic and language that Construct 3’s visual blocks represent -- not just for the sake of building games, but as a way to improve actual programming structure.

A reference or syntax mapping, even something unofficial or community-built would help me:

•Learn to mentally translate event blocks into their equivalent written logic

•Practice code structure and improve debugging skillls by understanding flow more clearly

•Bridge my current no-code knowledge into low-code or full-code workflows in the future

•Better communicate with collaborators who are more code-oriented

I'm not asking for internal implementation code, just a consistent reference or example set to help learners like me transition and be versatile going between visual scripting and writing real code later n' vice versa.

I believe resources like this would also benefit others who, like me, are using Construct not just as a production tool, but also as a learning platform to grow their skills beyond the visual environment. That is why.

Thank you

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.

I know the clipboard format isn’t meant to be human-readable, and I’m not trying to read it like code directly. But I do find value in looking at the structure -- how event blocks, conditions, and parameters are stored — because it does help me think about how I might express the same logic in real code (like functions, expressions, or object references).

For example, seeing things like "value": "Self.vy + Self.gravity * dt" lets me mentally map the visual action to something like vy += gravity * dt; in JavaScript. That practice helps me with scripting and clean structuring.

So I get that it’s not meant for this -- but even in this raw form, it’s helping me develop that coder’s mindset, which is really my end goal here.

I think the real goal here is to feed this into an AI, so it can generate native Construct 3 code.

What you're asking about is basically an implementation detail of how event sheets are saved to disk. Knowing more about that won't help you achieve your stated goals. For example if you know the ID for some specific action in the event system, that has no correlation to the equivalent in JavaScript or TypeScript coding. It won't help you, and may actually hinder you, with progressing on to coding - instead I would recommend our Learn JavaScript in Construct tutorial series.

Further these IDs are just how Construct saves things to disk, and don't actually tell you anything about how the event system runs those event blocks. A better way to learn about that would be to inspect the documentation and make some exploration projects that test how Construct actually runs various combinations of event blocks.

So I'm afraid I don't think it would actually help you to answer your question!

Thank you for your reply.

Is it possible to get a list of the current block IDs for events, conditions, actions, behaviors?

If it’s a no, that’s fine -- I just want to close the loop.