can I post random editor shit in here?
You can post whatever you want, rules do not really get enforced much here about channels

If you want to post info about your editor, I can make a specific channel for that!
I'm sure many people here (including me) would be interested in keeping tabs on it
I mean... I guess both? I just wanted to ask about the crates again
Oh, I thought you were referring to your editor
Feel free to ask questions here or in #xxl, I don't think it matters
It's just nice to keep order for the autists

I believe I found another issue: when you duplicate a hook, it always sets the activeSector (saved in the Addendum) to -1 (which means the level file). If, for example, the original hook was a CKHkWater with activeSector=0, it won't carry over and get saved incorrectly in the addendum, bricking the level! Of course I'm just assuming here, but did you mean to write -2? Because if it is -2, it will try to figure out the activeSector in the onLevelLoaded function for the newly duplicated hook
Also, if you duplicate a CKHkWater and change the ground it references which is in another sector, the same issue happens
Currently, when you duplicate a hook, it will place it in the common sector.
This is intented, because it is simplier and less risky to put everything in LVL, than putting in the STR which can be tricky.
But there may be problems in the duplication: not sure but one example is that when you duplicate a hook with a model in a sector, it might not duplicate the texture to the LVL's dictionary. But by exporting the hook to a file and importing I think it should.
Setting to -2 is a bad idea as that will make it use some guessing to find the correct sector.
For water (or something else can't remember) I think it uses the sector's bounding boxes to check if the sector matches or not.
It works luckily on the original files, but if you start to mod, these "guessing algorithms" will probably collapse and fail.
I think the problem is that the ground has to be in the same sector as the hook's active sector, which is important during loading as it's expected to be the same. But since the duplicator place the hook in the LVL, then a "quick&dirty" fix is to put the ground in the LVL as well.
Or change the active sector of the hook, but not sure if that is possible.