It's better to move to the new built-in Functions feature. It helps you make your project events modular and the functions can be easily looked up.

Although, I do not recommend Function Maps, use the Scripting Feature for string based Function calls.

> 	runtime.callFunction("functionName", param1, param2, param3, ...);

I hope that helps.

Hmm, I'll give that a try, thanks. That could really trim some of my code.

The restrictions of the new functions are intended to both enforce better organisation on your project, and improve performance. For example if you are allowed a function with the same name in two places, you can no longer look at a function and know what it does - you have to be aware of the entire rest of the project and see if there are any other functions with the same name. Besides, there's no reason to do it: you could just use one function with a series of sub-events to do everything in one function. And if for some reason that is difficult or awkward, you probably actually just want two separate functions. Now with the new functions you can look at one function and be confident that is the full logic of the function right there since other functions with the same name are not allowed. This improves your ability to reason about your events. It's also faster since the engine doesn't have to handle iterating over multiple functions with the same name, it just goes to the one function directly and runs that.

There are also major usability improvements, like being able to properly name and describe parameters, and renaming functions and parameters automatically updates the entire project for you.

I would strongly discourage you from using the old functions since they have poorer usability and much slower performance. Also in general deprecated features should not be used in new projects, since one day eventually they will probably be removed.

There's more info in the blog post Construct 3's new redesigned functions and More about Construct's new functions.

This got more attention than I imagined it would. Is there any chance you could make it so we can set default maps and strings for a function directly when we create it, in some update in the future? I have already switched to new functions and am getting used to them.

Actually you can use the old function on C3 runtime, but since its unprecated you can't add it as a new object, although you can use it if its already added in your project.

But I still doesn't understand your reasons to not use the new functions, since it can do all things the old function do and more.

I used to call functions directly by string variables and make a whole tree of them. I can still do that now but it's a bit more tricky.

Wow, I didn't know that. Thanks for the info. I guess for better or worse I have to integrate C3 functions into my builds.

I'm going to guess it's not possible

I have a silly question I haven't found any answers for. How do you change the width of the event and action columns on the mobile editor? Is it even possible?

I finally managed to implement my solution in the app I was talking about. Just to confirm, the whole point was to edit metadata that consists exclusively of text without corrupting the binary parts of the files. The app loads each file inside a specified folder as binary data, then copies the data into a text string and uses the string to determine where the text is and where the actual binary data is in order to separate them. Then it edits the text, converts it back to binary and sticks the real binary data to it to re-assemble the file.

I now was able to mass edit 400+ files in a matter of minutes and save loads of time and effort so thank you all for your help.

I also mentioned I have no idea what to do other than load and save the files using the Binary Data Object. When I load them as text I put the data into a string and use find, replace and such to make the edits I need. How do I do that with the data inside the Binary object? I tried converting it to text but it brought me back to the same problem.