It seems that Edopro is missing custom formats aside from 2005-Goat and the current ones.
While the necessary banlists for things like 2010-Edison or 2011-Tengu have been put together (for example here: https://www.reddit.com/r/CompetitiveYugioh/comments/lc2ogq/23_legacy_formats_for_edopro/), they still can't be hosted. To currently circumvent this, hosting people have to write a note in the description and hope, that the joining player knows what "EDISON" means for example.
Wouldn't it be better if the server forces the banlist upon the clients? Regardless of if the client has it installed? In that case, the banlist of a server has to be browseable in the lobby to know, what you've signed up for. Also with a "Save as..." option, so that the client can grab the banlist and host it himself next time.
That way, some brilliant custom made banlists could be distributed easily as well.
Some troubles I'd see...
Considering badguys manipulating standard banlists to sneak some offically "banned" cards in a game, there would have to be a check, if server's "2005.4 GOAT" is exactly what you have on your computer. Mark it with making the font red instead of white, indicating something has been altered. And having the server-side banlist browseable might show the evidence, which manipulations have been made.
It seems that Edopro is missing custom formats aside from 2005-Goat and the current ones.
While the necessary banlists for things like 2010-Edison or 2011-Tengu have been put together (for example here: https://www.reddit.com/r/CompetitiveYugioh/comments/lc2ogq/23_legacy_formats_for_edopro/), they still can't be hosted. To currently circumvent this, hosting people have to write a note in the description and hope, that the joining player knows what "EDISON" means for example.
Wouldn't it be better if the server forces the banlist upon the clients? Regardless of if the client has it installed? In that case, the banlist of a server has to be browseable in the lobby to know, what you've signed up for. Also with a "Save as..." option, so that the client can grab the banlist and host it himself next time.
That way, some brilliant custom made banlists could be distributed easily as well.
Some troubles I'd see...
Considering badguys manipulating standard banlists to sneak some offically "banned" cards in a game, there would have to be a check, if server's "2005.4 GOAT" is exactly what you have on your computer. Mark it with making the font red instead of white, indicating something has been altered. And having the server-side banlist browseable might show the evidence, which manipulations have been made.