Don't post in this node then if you are not making a comment on the meATpAk.

On the meATpAk, it is very well done. No gaps, no problems, can switch between original menu and the meATpAk with ease. Good job. I found some of the changes useful, but others annoying (gamma change..)

The new menus are well done as well, maps sorted alphabetically.

What would have been nice would have been some new editing menu changes, but other than that, this is very nice.

4/5

well so far it's mostly in keybinding,
checkout kbrdlay/kedit.cfg
problem is there's no better documentation of meATpAk features than that :-P

Have you found the numeric keypad for entity property control?
0,"," for property #0 +/-,
1,2 for #1
4,5 for property #2 and 7,8 for property #3
makes for easy to align doors, monsters and models.

Also I find that having special submenus bound directly to a key -
like the # key in edit mode for the "entity"-menu, COMMA and PERIOD as trigger & teleport quick-key -
makes good use of the feature of the sauer-menus where each remembers it's last active item - makes for quick re-usage of menu commands,
but I'm more of a console guy anyway.
So I tend to use loops of sub-commands to achieve stuff.
/loop i 2 [entproperty (+ $i 1) -192]

Have you used the "texlay" menu? ... try the "grid" entries there!

I'm working on an "actions" plugin, which already has the gimmick function of jumping into edit (if needed) and placing a teleport-destination at your current position.
It then also creates a teleport - one with a destination you selected via a menu with 128 teleport entries (index) in it.
It then jumps back out of edit mode - so you auto-jump to that teleports exit.
It then jumps back into edit and places a teleport back to where you came from.
it's kinda useless since it will litter your map with defunct teleports in the long term ...

Did I say something bad about you? No? Then don't reply to something I wrote to him.

This script-pack is really outdated ... code is more fresh in QCSP ... CubeScript keeps changing, so a lot of stuff I mangled here is not required anymore:
E.g. the empty_arg_list function :)
It was used to fix up the values of the argument list;
like when you used to call "func_1 val1 val2 val3" and then "func_2 val4"
then in func_2 you'd still see "$arg2 to be == val2" ... which gives problems with functions testing for $arg2 to be empty.

And for the second question the answer is a mixture of "it just grew that way (probably it started out a lot more complex)" and secondly it's often easier to map arguments to variables than adding twenty or so @'s ;-)