Do you have another discussion open about this somewhere? I am just curious if it is related to something I recently came across in the editor trying to run code in the onpaletteadd function and realizing that RED.nodes.eachConfig can never find my config node because it is too soon to check. I am still trying to determine if that is a bug or just the expected behavior. Regardless, I have a pretty clean workaround for it by adding RED.events.on('runtime-state', handleRuntimeState) in the onpalleteadd function. After the first time it detects obj.state === 'start', I remove the event listener.
Good idea. I will use that technique to not include my help button.
