Grimrock

Noticed something funny today. If you have a function with an underscore in the title, you can't connect a button to it in the dungeon editor interface. Nothing with an underscore will show up in the 'action' drop-down list.

Yup, seen that. LOTS of confusion ensued.

I hadn't actually seen the consequences of using underscores for functions, but I am strict adherer to the conventions of underscores_for_variables and camelCase() for functions.

I use camelCase for everything, just makes a lot of sense to me, but having a different format for variables might be helpful, I'll consider it

I've been using it as a feature!

My script is large and in charge with plenty of functions, but only a few of them are intended to be linked to buttons. So any function that I don't want to use with a button, I put an underscore in the name. Then when I am linking up any buttons, there aren't a billion options to choose from.

It's a feature I guess the idea was that if the function name starts or ends with an underscore it's private to the script and therefore not exposed in the dropdown. The check seems to be a little too trigger happy and rejects all functions with underscores in their name.

Ha! Good to know. So Balthasar was the only one adept enough to figure that out on his own