The current functionality of assigning a region as active is fine but a bit too complex for noobie players and they don't bother to read tutorials or watch a video. Also the current format can be cumbersome at times when flipping between multiple regions.

I don't propose scrapping the current system as it's pretty solid and works well for seasoned vets. The default functionality should not require the use of setting active regions though. The active region would be dictated by the location of the player and getting the regions that he is in. On a command if no active region is set it would check the player's location for plots/territories and use them as the active accordingly. Any overlap in regions would give a warning to the player about overlapping regions and having to set an active instead.

Town wise if players can join more than 1 town check the territory the player is in if he's a member of that town and use that as the active. If players can't join multiple towns then have the active town always be that town (unless set to of course).

This functionality could also be turned off for players using a command (/mct setting auto (on/off) ?) to regain the old active only system as before for more veteran players. This default functionality could also be turned off in the config.

This would help extremely with the learning curve of new players and provide new functionality extending the current system providing more choice too.

That's a good idea, and I agree, this could use revisiting. I like your plan and will look into implementing it for the next version.

Incidentally, does the quick-select tool not do what you're describing?

Because right now the plan is to just take the quick-select tool's functionality and run it automatically when you run a command.

Quick select tool is nice but not as easy as an auto select system like I outlined for new players. I asked various players and they thought that this auto-select way would be easier for newbies.

But different from the quick-select tool that it doesn't set permanent active but a temp one that is only used on that command and discarded afterwards.

Alright, I understand what you want now. I'll keep you posted on progress.

Okay thank you I really appreciate it.