1) "/selectarea" is definitely a different command than the other two, as event.getCommand().split(" ")[0].equals("/select") will not match it; the other two might end up behaving differently or not according to the way each treats further words after the first.
2) Are we sure that only one instance of the area selecting tool would be created or there will be several?
3) Even if they share the same area selecting tool, once the selection completed, each will carry on its own processing of that area; not necessarily what the user may want...
This is similar to the problem with Java package names (which should ideally be unique world-wide) or with GUID (which are by definition "Globally Unique"). In both cases, some heuristics has been found to manage the problem. It should be much easier in a much more limited domain, like RW chat commands. I am not sure that picking the first string coming to mind and not yet used by another plug-in is such a heuristics...
several instance's of the selection tool running at once oO i don't think it works like that, but ill ask red51 as thats a good point,
, saying picking the first string coming to mind is a little rude Miwarre its almost saying i was lazy lol but the tru fact is the frist thing i picked was /bp
but after all the problems with world edit and users typing the wrong thing like / weplace block /weplace block etc i decided adding /bp to the mix would case more problems than it solves.