Understanding Function Maps

As a C2 user I've been trying to learn more about C3's new features. Maybe someone could help me see the value in Function Maps?

I checked out the Function Map tutorial included in C3, but that only made things more puzzling. It seemed like it took 3x more work to do something you can make with one function and some if statements.

For example: here's a picture of the C3 Function Map tutorial done without function maps. It's much less work and much simpler — but I'm sure I'm missing something valuable about these maps.

In C2 it was possible to call functions by name. You could do things like Call Function choose("SpawnZombie","SpawnVampire"), or even Call Function "Spawn"&choose("Zombie","Vampire")

In C3 it's not possible, you can only pick function name from the list. That's why function maps were added.

Of course, in your example it's easier to just use a function parameter. But imagine you have several large functions with very different code and you need to call one of them dynamically by a string name.

Having said that, I haven't used function maps myself, I find this concept too complex and cumbersome.. I still prefer to use a bunch of If-Then-Else blocks.

A use I've found for Function Maps is being able to call functions from within my JSON-based dialogue system. Basically you store a string in the JSON, then by mapping a function to that string, you can call the function later on.

This explains the use case hopefully a little better.

Laura_D Good point! I just remembered that in my game Planet-O-Tron all button sprites have an instance variable, that contains function names. When any button is pressed, I call its function from that variable. So that's another way to use function maps.

Well, I see function maps as a form of polymorphism concept. But that's because I come from an object-oriented programming language background. So, for me it is a very interesting way to make your code more extendable, like, making your functions more reusable. I think it could also be useful to implement delegates/callbacks (or at least a resemblance of that).

Having said that, I agree that for a starting user or for someone who doesn't know about coding may think function maps are too confusing and even overkill, demanding a lot more typing than using a bunch of if-elses. And for a small project it is true indeed.

But, for a huge game with lots of levels, upgrades, skills, and so on, mapping functions to execute similar actions with different parameters will be a huge boost in your coding process and also with readability and maintenance (just like the JSON dialogue system Laura_D has pointed).

So, what I really wanted to say is that function maps (along with the scripting feature) is a powerful tool that allows us to make bigger projects, and elevates Construct 3 level against other competitor game engines.