Your Chance To Participate In A New Football Phenomenon (Sandbox Simulations)

[Rain Man]

I apologize if the mods think this is soliciting, and I guess it is, but at the same time it's beta testing a new product developed by long-time planeteers, and it's free.

cdcox and I have been developing a new football game for the thoughtful fan, where players build franchises and compete against each other. A description is below.

If you're interested, we're offering the game for free in Year 1 to Chiefsplanet members, with the goal of both giving the system a dry run and also hooking you like Phillip Morris. You can go to www.sandboxsimulations.com to sign up, and use the access code 6Lanier3.

Here's the overview:

Build and manage a full 53-player roster over multiple seasons, as an offseason activity to give you year-round football

Select your personnel to match your offensive and defensive scheme. Every position matters – even your blocking tight end.

Realistic and accurate simulations of league games based on head-to-head matchups against other teams in your league.


This is essentially a new concept in fantasy football that attempts to simulate as closely as possible the management of a real NFL franchise over a multi-year period. Unlike regular fantasy football, every position on the offense and defense contributes to your success or failure. On special teams, the punter, kicker, and kick returners matter.

In Sandbox Football you will build a team – an entire 53-man football team – via an initial draft, and will maintain it year after year in annual rookie drafts, trading periods, and free agency. You compete against teams in your league. In the first year of the game, before the start of the NFL season, you will build your roster by drafting veterans and rookies through separate drafts, and through trades with other teams in the league. Your roster is frozen at the beginning of the NFL season. During the real regular NFL season, you can focus on your traditional fantasy games and perhaps keep on eye on your Sandbox roster as our statistical models build the data on player performances. At the end of the regular NFL season, the Sandbox season begins. There will be 16 games in the season. In real time, the season will run about 8 weeks (2 alternate reality games per week).

Game outcomes will be simulated based on the performance of individual players during the just-completed NFL regular season. The simulations, developed by a PhD statistical expert, estimate how individual players will perform in the context of your alternate reality team competing head-to-head against other teams in the league and with the specific team that you have built. The simulations will consider the offensive and defensive schemes that you select. So you can build your roster to support a power running game or a high-flying passing attack. You can run a 3-4 or 4-3 base defense. You can run nickel formations or four-wide receiver sets. You can rotate your DL to keep them fresh.

The game is more about building a team than playing video games. So this isn't Madden, but you will have the ability to tweak your game plan to take the best advantage of your roster and the weaknesses of your opponent. Injuries are a factor in the game. If a player is unavailable during weeks 3 through 6 in the NFL, he is also unavailable during the same weeks in the alternate reality season. So roster depth matters. The game simulations are based on the most advanced statistics and the latest research regarding what matters in winning an NFL game. But, the outcomes of the games have a random component, just like real NFL games.

The calendar for the alternate reality league year will look something like this:
• Jan to Mid March: Alternate Reality regular season and playoffs.
• Mid-March to the beginning of NFL season: Roster building through trades, veteran draft (first year), free agent drafts (2nd year and beyond), and rookie draft.
• Beginning of NFL season to end of regular NFL season: Alternate reality league is dormant, but the NFL players are generating their performance stats for the up-coming AR league.
• Rinse and repeat.

Copyright Sandbox Simulations, all rights reserved.

We're still finalizing the cost structure, but this won't be an expensive game to play at all. It might range from a few bucks a year to $50 per year, depending on a few factors.

Year 1 will require a couple of days of drafting with rather high intensity, but we've got it set up where you can put your draft list together and do customized and automated drafting if you like.

So...go! Now! Time to get ready for the draft!




Note that we are still in beta testing, so things could change if we find problems in the system.


How Free Agency Works:

Free Agency will begin before the 2012 season after the rookie draft.

Our process is as follows for the 2012 season. In 2013 and beyond there will be minor changes as noted later.

1. We will unveil the list of available free agents so you can check out the talent pool.

2. If you look in "Standings", you will see that you have a salary account value of $1,300. You will use this to sign your veterans to contracts, sign your rookies to contracts, and (in a competitive bidding process) sign free agents to contracts.

The cost of a contract is as follows for players already on your roster (both veterans and rookies).

$0 - 1 season contract
$10 - 2 season contract
$22 - 3 season contract
$37 - 4 season contract
$55 - 5 season contract
$76 - 6 season contract
$100 - 7 season contract

You will sign your existing players to contracts using an interface that we will unveil shortly. If your 53-man roster is set you can spend your $1,300 on your current roster. However, it may be worthwhile to hold some money back so you can compete for free agents.

3. The free agency period begins.

Bidding for free agents will be open and competitive. As players come available, teams will be allowed to sign them if they are the high bidder. The contract length is automatically calculated by rounding down the bid to the chart below.

Contract Length (Seasons) Salary Points Bid
1 0 to 9
2 10 to 21
3 22 to 36
4 37 to 54
5 55 to 75
6 76 to 99
7 100 or more

For example, if you submit the winning bid for a player at a price of 25 salary points, that player becomes yours under a 3-year contract. If you submit a bid for 35 points and win, it’s also a 3-year contract. If you submit a bid for 38 points, it’s a 4-year contract. If you submit a bid for 120 points, it’s a 7-year contract.

For the 2012 free agency period, we will enforce the 53-man rule. You will need to cut down to 53 players before the free agency period starts, and if you sign a player to go above 53, you will need to cut a player to stay within the roster limit. NOTE: DON'T CUT YET UNLESS YOU WANT TO. WE'RE STILL FINALIZING THE SYSTEM AND WANT TO BE SURE THAT THIS RULE WORKS IN 2012.

4. Ending Bidding and Ending Free Agency.

Bids on an individual player will begin once the first player places a bid. For the 2012 season that bid must be $1 or more. Bidding ends when the existing high bid had not been raised for 72 hours. At that point, the high-bid team is awarded the player under the contract terms described in Step 3.

The free agency period in 2012 will end once there have been no bids on any players for 72 hours.

5. Unused Salary Points

If you do not use all of your salary points in a given year, they will roll over from year to year. This is experimental and we'll have to see how it works. If it doesn't work, they'll expire each year, or maybe a portion of the points can roll over. Right now, assume they all roll over.

6. Salary Points and Roster Management

In the Sandbox system, salary points and the salary cap are used only for acquiring players. You will never have to track the number of salary points “on your roster” and you will never have to cut a player for salary cap reasons.

Additionally, you are not obligated to keep a player for the full length of his contract. You can cut him or trade him at any time. However, recognize that it’s a waste of salary points to cut or trade a player before the end of his contract. But it doesn't hamstring you going forward - it's just past money that you wasted.

7. Free Agency and Contract Length - Retaining Your Current Players

When a player reaches the end of their contract, they go back into the free agency pool and teams will bid for their services. You are eligible to bid on them to get them back, just like you can bid on any free agents.

There is one exception to the rule of free agents going into the free agency pool, as follows:

• At the end of the bidding process, you have the opportunity to re-sign your own players by outbidding the high bidder. Your bid must be the minimum points to increase their contract period by a year over the high bid. (Example: your player goes to free agency, and another team bids 50 points for him, which equates to a 4-year contract. You can keep the player by paying 55 points for him, which is the minimum amount for a 5-year contract.) If the high bidder offered a contract of 100 points or more (7-years), you can keep the player by bidding 10% more points than the high bid.

8. Free Agency and Trades

If you trade for a player, their contract length is a consideration. Trading for a player with 6 years left on his contract will give you his services for that amount of time (unless you cut him or trade him, or he retires). Trading for a player with 1 year left on his contract means that he’ll go back into the free agency pool at the end of the season. (Of course, you can still retain him via Step 7.)

9. Future Years

In future years, the process will be identical to that shown above, with the following exceptions.

a. Because you will have a lot of veteran players under contract, you won't need $1,300. You'll get a new annual allotment of signing dollars. We're still working on the exact amount, but it looks like it'll be between $500 and $600.

b. In the 2012 season, we will introduce all free agents at once to catch up. In the 2013 season and beyond, the free agency period will occur during the actual NFL season. We will sprinkle the free agents in one division at a time over the course of the season. (The divisions may be randomly selected or we may release a calendar. It doesn't matter that much.) This system should be interesting because some free agents will come available early in the season when you don't know their performance for the year - greater risk, greater reward - while other free agents will come available later in the season when you know what their performance will be, but so does everyone else.

c. In the 2013 season and beyond, you will be able to retain more than 53 players through the rookie draft and the main free agency period. You will then have a cutdown period to get to 53 and we will have a final free agency period where you can sign any players who have been cut. In that final period you will have to enforce a 53-man roster, so if you sign a player you have to cut one.

10. When you think about the schedule in 2013 and beyond, it will go like this:

a. Sandbox season goes from February through April.
b. Rookie draft in May. No 53-man limit.
c. Free agency from (likely) September through December, with free agents sprinkled in throughout that period.
d. January. Roster cuts to 53.
e. Late January. Final free agency period to flesh out rosters and sign players cut in Step d.
f. New Sandbox season begins.

[MagicHef]

I just noticed that Vladimir Ducasse, my 326 lb G is listed as a TE. Will this affect his play?

[cdcox]

Originally Posted by MagicHef

I just noticed that Vladimir Ducasse, my 326 lb G is listed as a TE. Will this affect his play?

Based on 2011 snaps, I moved him to RT. That should be better than TE if you want to use him as a G.

[topher79]

Still wondering how I ended up with Cam Newton, LaGarrette Blount, Darren Sproles, AJ Green, Andre Johnson and Steve Smith.

Championship.

[cdcox]

I've taken the site down for the update. There are a lot of database tables to install, so it might take a while. When it come up, the simulations for first week of the season will be viewable. Hopefully this goes smoothly.

[AustinChief]

TIMEZONE ERRORED!



Your codeigniter is throwing all sorts of timezone warnings!

(I'm sure you already know this)

You may want to look at this fix...

http://philsturgeon.co.uk/blog/2009/...ter-on-PHP-5.3

[cdcox]

Well, needless to say, it didn't go smoothly.

Making progress, but not there yet.

[AustinChief]

Originally Posted by cdcox

Well, needless to say, it didn't go smoothly.

Making progress, but not there yet.

If you need any PHP or MySQL help, just let me know.

[Hammock Parties]

fffffuuuuuuuuuuuuuu

[cdcox]

I have the choice of two versions of php on the production server: 5.2 something and 5.4 something. Codeigniter doesn't play well with 5.4.

I'm using a feature that was new to php 5.3. I think the easiest way around this is to rewrite 600 lines of code without the 5.3 feature so I can use php 5.2.

[AustinChief]

Originally Posted by cdcox

I have the choice of two versions of php on the production server: 5.2 something and 5.4 something. Codeigniter doesn't play well with 5.4.

I'm using a feature that was new to php 5.3. I think the easiest way around this is to rewrite 600 lines of code without the 5.3 feature so I can use php 5.2.

What's the feature? I work with CI quite a bit and may have a work around for you.

You are probably much better off using php 5.4 and getting CI to work with you there. Much easier then rewriting 600 lines of code.

[cdcox]

Originally Posted by AustinChief

What's the feature? I work with CI quite a bit and may have a work around for you.

You are probably much better off using php 5.4 and getting CI to work with you there. Much easier then rewriting 600 lines of code.

Goto

I know, goto isn't the best coding practice. But it can sure come in handy for events that can happen at multiple places in the code, like touchdowns. I'm hoping that I can move a few things around to get rid of the goto statments.

To me, writing code is much easier than dealing with package installs and upgrades. I'm still running CI 1.7, so I'd have to do the upgrade to 2.0, which looks time consuming. Then get php 5.4 working on my localhost. Then hope that would take care of the error messages on the production site that are pointing to the CI core, not to my code. So even if I updated, it isn't clear that would take care the error messages that look very difficult to track down.

[AustinChief]

Originally Posted by cdcox

Goto

I know, goto isn't the best coding practice. But it can sure come in handy for events that can happen at multiple places in the code, like touchdowns. I'm hoping that I can move a few things around to get rid of the goto statments.

To me, writing code is much easier than dealing with package installs and upgrades. I'm still running CI 1.7, so I'd have to do the upgrade to 2.0, which looks time consuming. Then get php 5.4 working on my localhost. Then hope that would take care of the error messages on the production site that are pointing to the CI core, not to my code. So even if I updated, it isn't clear that would take care the error messages that look very difficult to track down.

Yikes..

If it were me, I'd bite the bullet and move everything to php 5.4 and CI 2.1.1 .. since you will have to do so at some point anyway... BUT if you want to wait on that nightmare.. then getting rid of GOTO is a good idea anyway.

Can't you just make classes/functions that can be called instead?

Again, if you need a hand on anything I can whip through php/CI code pretty quickly and debug. I have also installed PHP 5.3+ and CI 2+ about a dozen times this year so feel free to ask me there as well.

Your production server an Amazon instance? or something similar?

[cdcox]

Originally Posted by AustinChief

Yikes..

If it were me, I'd bite the bullet and move everything to php 5.4 and CI 2.1.1 .. since you will have to do so at some point anyway... BUT if you want to wait on that nightmare.. then getting rid of GOTO is a good idea anyway.

Can't you just make classes/functions that can be called instead?

Again, if you need a hand on anything I can whip through php/CI code pretty quickly and debug. I have also installed PHP 5.3+ and CI 2+ about a dozen times this year so feel free to ask me there as well.

Your production server an Amazon instance? or something similar?

Building the initial code it was easiest for me to conceptualize the game simulation, coaching decisions and mechanics of keeping track of the game situation by writing 600 lines of stove pipe code. That 600 lines calls 3400 lines of functions. I haven't done any object oriented with this project, although my playoff simulator is all object oriented.

Now that I have the basic logic down in that 600 lines of code, I think I can reorganize it slightly using if statements with a reasonable level of nesting to get rid of the goto statements.

Our production server is a 1&1 shared host, but we will probably move to a managed cloud server or something within the next couple months.

[AustinChief]

Originally Posted by cdcox

Building the initial code it was easiest for me to conceptualize the game simulation, coaching decisions and mechanics of keeping track of the game situation by writing 600 lines of stove pipe code. That 600 lines calls 3400 lines of functions. I haven't done any object oriented with this project, although my playoff simulator is all object oriented.

Now that I have the basic logic down in that 600 lines of code, I think I can reorganize it slightly using if statements with a reasonable level of nesting to get rid of the goto statements.

Our production server is a 1&1 shared host, but we will probably move to a managed cloud server or something within the next couple months.

Cool.

On the hosting side, I would advise against a managed solution simply because I can't imagine you'll really need it. Once you have an instance up and running, it pretty much takes care of itself. For something like this it would probably double or triple your costs for no good reason.

[cdcox]

Originally Posted by AustinChief

Cool.

On the hosting side, I would advise against a managed solution simply because I can't imagine you'll really need it. Once you have an instance up and running, it pretty much takes care of itself. For something like this it would probably double or triple your costs for no good reason.

Thanks, I may pick your brain about server options, because I know very little about the various options, advantages and disadvantages.