I will note that the online ticket setup was FAR from fair. Why do I know this? I got more than a dozen tickets.
First of all- it's cookie based, with the URL for the refresh embedded in the URL of the "waiting room" screen (which is not really a line at all, just a refresh window that beats you against their servers).
Second- when the "cookie" is set to the point you get to the "SINGLE EVENT TICKET" window, you can cut/paste that window's URL into multiple tabs, thereby ensuring ONE of the cloned windows will not time out.
It gets a little hairier with the word confirmation. You can't have multiple word confirmations running... so you have to process them serially (one at a time). That's a bottleneck- so it's good to have three or four browser instances (on multiple computers, if you have them), so you can get past the word confirmation screen.
Once you're into the confirm/pay screen, you can then clone THAT window into multiple tabs as well.... I never ended up in the same browser tab than I started- one of the cloned windows would ultimately break through to confirm your purchase, check out, and get your confirmation screen.
Basically... when the cookie changes, clone the windows. I got through 5 times this way, and was able to get seats for my family/friends. None were resold above face.
There is also another safeguard- the "ev3,ev4,ev5,etc." server pool is not random in the way it jumps.
evenue.net didn't even enforce the 4 ticket limit in software. Their cookie mechanism was not that complex... and needed to be beefed up to be fairer.