It’s just about to get a small overhaul because, yes, its follows some strange rules and is buggy.
In the current released version doing:
opcp /GLOBAL/UI/LIB/BUTTON dcjnk
will create /GLOBAL/UI/LIB/BUTTON/dcjnk, regardless of what your current component path is. This is obviously nonsense so it’s going to change.
In the upcoming versions (Im going to do this change today)
opcp /GLOBAL/UI/BUTTON dcjnk - Will create dcjnk in whatever the current component path is
opcp /GLOBAL/UI/BUTTON . - will create a node named BUTTON in whatever the current component path is (as it does now)
opcp /GLOBAL/UI/BUTTON /dcjnk - will create a new node /dcjnk
opcp /GLOBAL/UI/BUTTON /dcjnk/ - will create a new node /dcjnk/BUTTON (assuming dcjnk already exists, otherwise it’ll error)
opcp /GLOBAL/UI/BUTTON /dcjnk/newname - will create a new node /dcjnk/newname (assuming dcjnk already exists, otherwise it’ll error)