jacob1:

@Videogamer555 (View Post)
There is no way, you'll have to look at the source code every time. You can probably just guess what the properties of most elements are, I think most are just their state, and the rest are obvious like hotglow or conductive with life decrease

Which file do I want to look at if I want to see the properties of an element?

me4502:

@jacob1 (View Post)

i originally did make a command to show it in my 'awesome lua pull request' that added about a quarter of the commands there are now... but simon removed it... basically, it allowed tpt.active_menu to set secret one

Why? Why do they not want access to the secret menu? They don't want beta elements being accessed, because if it's not "polished" enough people will think its a bad element and it will reflect badly on their reputation of only making "good" elements? I'm confused.

Active menu won't work with ANY of the menus, not even the "non-secret" menus. But it doesn't generate an error, suggesting it DOES RECOGNIZE the command. Just that it doesn't do anything.

Active menu won't work with ANY of the menus, not even the "non-secret" menus. But it doesn't generate an error, suggesting it DOES RECOGNIZE the command. Just that it doesn't do anything.

However it seems the Lua section on the wiki still shows active_menu as a valid command (it shouldn't list it in the wiki, cause even if recognized by the software, it has been disabled so does NOT DO ANYTHING, not even with the NORMAL menus).

jacksonmj:

@Videogamer555 (View Post)
tpt.active_menu DOES work with normal menus. Or at least, it works fine for me. What is the exact command that isn't working?

Example usage (will open the liquids menu):
tpt.active_menu(5)

Now it works. Wonder what happened?