Presently, one needs to use chunky world <world> to change to the current world (unless the current world is world). This is rather non-intuitive. Please consider making the active world for all commands the current world, unless it has been explicitly set with chunky world <world>.

I looked into adding this feature, and while it is possible, it introduced some complexity that I don't think make sense for the moment with the plugin's current design.

This mostly has to do with the fact that now we would need to support both defaulting to the sender and selecting explicitly, but that leaves a lot of ambiguity with what will (or should) happen if someone were to, for example, select a world explicitly and then run a command in-game intending to select their current world. Switching worlds while in-game also poses an issue, since a command selecting something in one world could then affect another if the user isn't aware of how the defaults work.

That being said, I did like the idea, so I was a bit disappointed to find out this didn't function as well as I thought it would. If I find a better way to handle this in the future I will consider it again.

Note: I did end up adding chunky start [world] instead, which may be more intuitive for people coming from other plugins where the builder style we use isn't as common.

Thanks for looking into it. I don't find the complexity confusing, but I appreciate that others might. (I implement the complexity in my own plugins.)