We will be testing the ft20 format at first and adjust to your preferences if we get complaints about too long matches after the first matchweeks. Considering the team changes, we will most likely make a poll about this.
Spoiler
With such a numerical decline in the community it now makes sense for regiments to submit a team roster with player GUIDs. The league should be divided up into 4-5 stages (a stage consisting of 2-3 matches). At the end of each stage there should be a 2-3 day period where all players that wish to join new teams can (this includes external players wishing to join teams that are in the tournament). These changes should be listed on a post at the end of each stage. Whitelist the servers so that anyone who has not complied with the policy will simply be banned. In the past people have criticised this approach stating that it is too much effort but frankly every single RGL since season 2 has been plagued by the problem of double reggers so putting a little more time an effort in to construct watertight format is in the best interests of the organisers and the regiments.
The second point regarding people being in two regiments, one casual and one competitive, is virtually impossible to prevent. One can only manage the members that are in the RGL but there is no way of finding out what other regiments they are in if they really want that to remain hidden. A policy like that which the EIC introduced where no double regging of any form was allowed could be a start but it was hard to enforce then and it will be hard to enforce now.
Also, for once, can the organisers set up a criteria for accepting regiments rather than just going with whoever signs up. It is better to have a smaller roster of participating regiments who you know will stay till the end than have a larger roster which is half empty by the end of the season due to unstable regiments dropping.
I tried to implement a roster rule in season 2 but got huge backclash against it so I'm curious what the opinions about this are like now. We're thinking about this so if you want it or dont want it, it would be great to give us your feedback.
I posted a similar solution then. The reason why it received so much backlash is because there were simply so many established regiments with large teams that the general consensus was that it would take too long to set up properly. Nowadays with only a few stable regiments left (regiments which are actually going to stay for the duration of the tournament) and a considerably reduced player pool I do not think it should be that complex to sort out. One must remember that if done in the way which I suggested, the labour of the task doesn't solely rest on the shoulders of the organisers. Each regiment leader is responsible for providing the list of GUIDs for their team, then simply submit the list to the organisers. After that it is fairly easy to input the said GUIDs into a whitelist on each of the servers. When all the GUIDs are in the system, the 'transfer window' element is fairly self explanatory. Let's say there are 12 weeks (just an example, you would divide the weeks up 4 stages (so three weeks per stage for the special people out there). During an allotted duration at the end of each stage members of the participating regiments are able to transfer to another regiments roster. In addition to this if a player is part of a regiment that is not playing in the RGL and wishes to join a participating regiment then they can also do so in this period, it goes without saying that once the 'transfer window' is closed all rosters are locked in until the next one.
The only thing the organisers would have to do is post a small list after each window to ensure that all regiments are aware, an example of the format could go something like this:
Stage 1 Window
63e NewPlayer -
0203950 to 36e
N.B. There is no point discussing the topic of 'people being in a casual reg and a comp reg'. Rules have to be able to be enforced in all circumstances, no rule (short of having an RGL inquisition that would go around casual regiments trying to find double reggers) can be implemented that will be able to enforce this, therefore it is a null point. I've never supported double regging as it undeniably takes away from the competitive value of a tournament but it's simply something one has to accept will occur at this point. What the organisers can enforce however, like this GUID roster system should be implemented, at least then if you're playing X regiment you know that they are only using their players.