That’s completely different from custom menu items. That’s actual gcode macros. (M810-M819)
Custom menu items are gcode scripts defined in the firmware, and inserted into the queue when selected. Granted, those scripts could include M81X macros, but that’s completely irrelevant to this issue.
I think a good option is to wait for Ryan to merge the current bugfix changes into the V1 fork, and pick up the extended custom menu items (up to 25, rather than just 5).
Just out of curiosity, how hard would it be to disable some of the menus?
I am thinking I want to turn off " Configuration, Temperature, load media, Run media"
since I do everything from OctoPrint. they seem pointless and take up UI space?
Sz
Dunno. Probably commenting out the appropriate code in the various Marlin/src/lcd/menu/*.cpp files… Can’t imagine that it would be hard, but it could be tedious and/or finicky.
thnks
I think I found it.
Please share what you found. Others might benefit from it. 
Just be aware that, at this point, you are mucking about with the firmware sources. If you stay in /src/lcd/menu/ it’s doubtful you’ll break anything truly meaningful, but you could lose your LCD functionality. And if there are updates, you’ll have to re-apply any changes you’ve made. This is a bit deeper than tweaking the configs (although the code is pretty well structured to handle this sort of thing).
Thanks, I understand what your saying, But I am not a C++ Coder, though I know enough to be dangerous.
I am not going to change the menu’s persay, just turn them off to clean things up.
I was successful at turning off the Temperature and the Configuration menu. I can turn them back on if I need em 
// SUBMENU(MSG_TEMPERATURE, menu_temperature);
// SUBMENU(MSG_CONFIGURATION, menu_configuration);
