Warrior General Games

Pretty sure this has been brought up before, and nothing's been done about it.

The whole "can't play on back to back days" issue is to keep a dot from playing in 17 games in a season. I get that and it makes perfect sense.

The problem is that the rule was put in in such a sloppy way, they failed to consider (or just didn't care enough) that it can work the other way depending on which days the dots' games are (odd/even). Right now if a dot gets cut or a team gets sold that played on even days, it is impossible for them to sign with a team that plays on odd days without them losing 1 game of xp's.

There is no reason for it to work in the reverse, and they need to implement a fix IMO. Maybe run it by games played to date when signed to the new team. If both the new team and the dot have only played in 4 games to that point, there is no advantage to them.

+1 Stupid rule

+1 again

+1, but I admit to liking some of the other suggested fixes more. (Namely, coordinate scheduling by age brackets instead of alternating by league number, use a game "week" to determine XP eligibility, detach XP from games played, etc.)

Originally posted by CDZYO
+1, but I admit to liking some of the other suggested fixes more. (Namely, coordinate scheduling by age brackets instead of alternating by league number, use a game "week" to determine XP eligibility, detach XP from games played, etc.)

I honestly don't care (or really know enough about programming to tell them) how to fix it, but it's just dumb that it is still this way.

+1 if it goes by game week instead of game day. -1 otherwise.

Originally posted by smokinbluegrass
+1 if it goes by game week instead of game day. -1 otherwise.

What?

i've brought this up before, and got a direct response that it was going to change.

+1

I think that the best ways to do it would be one of the following:

1 - coordinate all league games of a particular age to play on the same (even vs odd) day, this might not be possible in the higher levels because there are a lot of pro and uncapped leagues etc

2 - Whenever you play the first game of the season, you lock in your day for XP, and you get XP on that day / time provided you are on a team's roster

3 - Allow players to play in back to back games, but only allow 16 total games per season to count toward xp. Any users that were found to be abusing this to try and stack all their games at the beginning / end of the season would be dealt with on a case by case basis

Originally posted by Chysil
I think that the best ways to do it would be one of the following:

1 - coordinate all league games of a particular age to play on the same (even vs odd) day, this might not be possible in the higher levels because there are a lot of pro and uncapped leagues etc

2 - Whenever you play the first game of the season, you lock in your day for XP, and you get XP on that day / time provided you are on a team's roster

3 - Allow players to play in back to back games, but only allow 16 total games per season to count toward xp. Any users that were found to be abusing this to try and stack all their games at the beginning / end of the season would be dealt with on a case by case basis



This.

Good to see a suggestion instead of just a statement to fix stuff. In this case, there must be a control of some sort, our we will see farm teams swapping dots several times a season to get extra levels through game exp.

Originally posted by vinman

Originally posted by smokinbluegrass
+1 if it goes by game week instead of game day. -1 otherwise.
What?


What I mean is this....

Right now, in a league, some teams play on day 1, some day 2. That's considered one week in GLB time. Let's say you play on day 1, and get a signing or make a trade that takes effect on day 3, a new week. You can't add the dot to your d/c if he played on day 2 (the previous week), but you can if he played on day 1 (also the previous week).

So, +1 if they'll change it to "can't play two games in the same week" as opposed to how it is now, "can't play two games within 24 hours." Otherwise, -1.

Originally posted by Dr. E
This.

Good to see a suggestion instead of just a statement to fix stuff.

Unfortunately, I don't have any programming experience to know what is capable of being done to fix this obvious long standing problem, so me suggesting specific ways to change the problem would be pointless.

I do appreciate the ideas being bounced around, and I will update the OP with some of the options being provided. Hopefully one of the ideas will be workable and they finally get this fixed.