The transfer lock is an arbitrary period set by me that prevents transfers around match times for reasons explained above. It's not big deal if I set it wrong or forget it, but it's there to prevent frustration with exact match times and transfers.

When your next transfer will be available is to do with when your last transfers were made. You basically have 2 transfers and they take 7 days to recharge after using. I don't think I phrased this particularly well when explaining it previously, or maybe my implementation is unintuitive. Either way I think that's the best way to think of it at the moment.

The two things don't affect eachother except that transfer locks are a temporary block on all transfers in that league.

Bump for NA time zones, week 5 game is live

There was a bug with creating a team if you'd created one before. That should now be fixed. TY Permzilla

The ESEA Week 4 game is over and the results are in:
First place is won by 5tv and his team $tvvvv, without picking a single Froyotech player.
2nd went to SentientRadio's team Avocado
3rd place went to Debit To Team's team, _ (nice name, also no Froyo)

Pixel trophies can viewed in all their glory here http://beta.fantasytf2.com/WeekDetails/Week/1

The winning lineups just go to show the reward of studying the schedule and not always going with the biggest names.

ESEA Season 19 Week 5 teams can now be created here http://beta.fantasytf2.com/PlayerTeam/Create?seasonid=5&name=&weekid=2
ESEA Season 19 Week 5 home is here: http://beta.fantasytf2.com/WeekDetails/Week/2

Thanks, I need to improve my game when it comes to ESEA watching. Lunacide and milo should now be buyable, Lansky I'll wait and see.

Transfers are currently use them or lose them. There's an economy upgrade in the works so I may alter that to encourage more trading, but there are competitive downsides to it as well.

Late updates to the scoring was caused by ESEA changing their site. Things should now be back in order.

The transfer lock isn't really to stop abuse, it's more to prevent people changing very close to a game and my timing of the game in the system, and therefore when they should get the credit for having the player, not matching up and causing frustration and confusion. Switching between maps isn't really an abuse, just unlikely to be consistent with what I enter.

Class doesn't affect the different points collected, however because I have to enforce class selection the team selection interface would need to be far more subtle to deal with it and it's not up to the job at the moment, so players stay with the class they're born with at the moment. This is also the case with teams, although I think I've got away with switching Forsak3n.

There have been some problems counting non standard ubers so I've gone back and fixed some historical data. Beater and Dikker were the main beneficiaries.

Alpha gamers with huge numbers of friends have pointed out that their friends team lists are incomplete. This should be fixed now, anyone with over 100 friends may see more buddy icons and entries in the friends team lists.

Jeeringsole eats ddos attacks for breakfast, you're fine.

ddos

Bump for the NA day shift. New game type outlined two posts back.

I'm piloting a new feature on ESEA, weekly games. If you've made a bad start to the season or arrived late, or you just want to try a different build, now you can make a new team that will run just for this weeks games. Check out the ESEA schedule carefully to see who is playing.

To create your team look for the summary box to the right of the main season team and player list, which looks like this:

http://i.imgur.com/e13HLoW.png

And hit Create Team to go to the usual team selection page. Details will show you who has currently created a team and what the player's weekly scores are.

As with anything in beta this could be a bit buggy, let me know if you spot anything weird.

Should be done.

Try opening a command prompt and enter ipconfig /flushdns, which should clear your local DNS cache and force your computer to get the location of the ESEA website fresh from your local DNS server, although it would be an unusually long cache to have not seen the change. If it still doesn't work then your local DNS server could be at fault or you might have something overriding it like a hosts file entry.