• Welcome to the Speedsolving.com, home of the web's largest puzzle community!
    You are currently viewing our forum as a guest which gives you limited access to join discussions and access our other features.

    Registration is fast, simple and absolutely free so please, join our community of 40,000+ people from around the world today!

    If you are already a member, simply login to hide this message and begin participating in the community!

Fantasy Cubing 2015!

Thanks Stefan!

Randomno: Probably. To me it seemed a bit silly not to pick at least one or two of those competitors because they've already scored "a lot" of points in this month.
 
Team changing will be February 9-11. I am extremely sorry that I was not around to fix this error. When I first put it up it was working fine both on a local server and cubing.net server. I understand the excitement you guys have for Fantasy Cubing, and I am doing my best to stay on top of it. Again, sorry for the inconvenience.
 
Team changing will be February 9-11. I am extremely sorry that I was not around to fix this error. When I first put it up it was working fine both on a local server and cubing.net server. I understand the excitement you guys have for Fantasy Cubing, and I am doing my best to stay on top of it. Again, sorry for the inconvenience.

No need to be sorry. We are all thankful to you and anyone else who has put work into the site. RL happens and it is better late than never. Again thanks for all your hard work so far.
 
Why was this so successful exactly a year ago at the same time of the school year and now results are being updated about every three weeks? Did school get that much tougher in a year?

When you get to high school, you will compare your freshman year to your eighth grade year, and your junior year to your sophmore year. You will realize how hard school gets.
 
Team changing will be February 9-11.

Does that mean this weekend's results count for January, and affect salaries for February? Or will it be like it was for January?

Btw, if during such three days, some results haven't made it into the WCA export yet, how do you determine the salaries? For scores it's ok to be delayed, but the salaries are problematic as they affect who you can use for your team.
 
Does that mean this weekend's results count for January, and affect salaries for February? Or will it be like it was for January?

Btw, if during such three days, some results haven't made it into the WCA export yet, how do you determine the salaries? For scores it's ok to be delayed, but the salaries are problematic as they affect who you can use for your team.

The salaries will be frozen on February 9 and everything that has made it to the WCA export will be used for January. Everything added to the WCA export after February 9 will count toward February. That way, everybody will have the same advantages.
 
Everything added to the WCA export after February 9 will count toward February.

What about the *changes* of "January points" due to results added after February 9 affecting regional record points for results added before February 9? And what if you have to recompute points because WCA changes old results?

I think this will make it quite hard to re-compute points, and impossible to re-compute just from the export (and team membership data) because the export doesn't tell which results were added when. What if your code has an error and you have to recompute everything? Remember your numbers were wrong a couple times already and are even wrong right now (and not just because you're a few exports behind).
 
Perhaps it would be better to use the results from competitions that would have originally counted for January (i.e. one-day competitions on 31st Jan, and multi-day competitions ending on 1st Feb) with the most recent export? Is such a calculation unfeasible?
 
Perhaps it would be better to use the results from competitions that would have originally counted for January (i.e. one-day competitions on 31st Jan, and multi-day competitions ending on 1st Feb) with the most recent export? Is such a calculation unfeasible?

I'd prefer that, although it has pretty much the same problems. Some thoughts:

There are cuber points, team points and salaries. I don't think they should be treated the same.

For cuber points and team points I'd update points as soon as the results are in the export. If Feliks scores 10000 points on January 20 but somehow that doesn't make it into the export until February 20, then that should still count for January, not February. After all, team owners might have hired Feliks because of that January 20 competition!

For salaries, I'd use the cuber points either frozen at the start of the three-day-period or at the point of time when the team acquired the cuber. So unfortunately Feliks could be acquired in February for 10000 points too cheaply, but in general we can't help it - results simply might take too long to get into the export, and we can't wait for it. And you can't on February 20, when the results come in, retro-actively tell people "Sorry, actually your team is invalid, lol". Cuber and team points, on the other hand, can *and should be* updated retro-actively.

So for salaries, Nathan's way is ok, but for cuber/team points I think it's wrong. Also, it would require some form of keeping track of when results made it into the database, and that's just yet another complication and also makes double-checking the numbers harder (you'd need to know which export he used and you'd need to have that export).
 
Last edited:
I still don't think my way would work that well for salaries either, because then a person might be able to have a team one month and then the next month they are forced to change it because of a retroactive change in salaries for the previous month. There will be definitely be a problem when we get to US Nationals (July 31-August 2) which will count towards August, but everyone will already know all the results of US Nationals before team switching. How do you fix that?
 
I still don't think my way would work that well for salaries either, because then a person might be able to have a team one month and then the next month they are forced to change it because of a retroactive change in salaries for the previous month.

Why? Salaries don't change once a cuber "signed the contract", right? I'd just make it clear in the rules that the salaries are defined by what's currently "known" rather than by what's eventually known.

There will be definitely be a problem when we get to US Nationals (July 31-August 2) which will count towards August

Why would you count that towards August? You recently answered an equivalent question about Jan-31 to Feb-1 by saying that Feb-1 counts towards January. And that's good.

Btw, any word about the current switching period? It's the last day again already (well, at least in Germany) and you're still behind with the exports and I still get "Internal Server Error" all the time when trying to get to my team. Bit weird to drop by but not say anything about the current status.
 
Last edited:
Back
Top