I started GM'ing when the beginner's box came out. I had some friends, my brother and my wife who wanted to join a EOTE-group. So we started and already had a lot of fun. Now that the core rules are out, we planned a bbq to do the character creation for the upcoming 'module(s)'. Because we already have some playing history I wanted to give my group a little extra. I decided to let them earn extra credits by joining a podrace...

I took out some hex-tiles that I happen to have, don't ask me why. Took out the micro machine podracers and started thinking.

What I already have is the following:

- To move, players have to do a pilot (planetary) check. Every non-cancelled success is equal to moving one tile. (First tile counts as difficulty)

- Every tile has a rating (little stickers) (easy to hard, one tile is daunting); they are randomly placed in a circle on the table.

- A race is three laps.

- When two podracers occupy the same hex, the have to make a competitive resilience, cool or vigilance check, depending on the 'story line'. The loser gets a setback die to his next check.

- A triumph is considered a 'collectable boost' (token) and can be spend to upgrade a die in the player's next check of his choice.

Still playtesting the following rules (to have a good average)

- 2 (or 3) advantages in a check adds a boost die to the next pilot check. (token)

- 2 (or 3) threats in a check adds a setback die to the next pilot check. (token)

What I need:

- Something that causes a fatal crash.

- Moving restrictions (to make sure you don't pass the daunting tile with a good dice result for example).

Hope these rules are a bit clear. Remember, I'm not making a high level game. Just a fun way to do an epic podrace with some excitement.

I'm anxious to hear from you guys. Ideas, suggestions,...

Of course you are all free to use this too :-)

Sounds fun! I'd run that! Full on Crashes should be caused by despairs.

You might also add in a limited passing rule like Formula Zero where you have to pass players in an unoccupied lane to pass them without crashing into them.

Potentials for fatal crash: Rock fall, tuskan snipers, bantha stampede across the track. Just those three off the top of my head. Please put this in a downloadable document when you've got it all worked up. This looks like lots of fun.

E

This is cool, nice job!

Potentials for fatal crash: Rock fall, tuskan snipers, bantha stampede across the track. Just those three off the top of my head. Please put this in a downloadable document when you've got it all worked up. This looks like lots of fun.

E

Engine failures and sabotage potential...

I really like the idea. Let us know how it goes!

This is fantastic.

I would really suggest you take this idea if you are willing to... and make it a fully functional board game about Star Wars Pod-racing and maybe come up with different Hexes for different types of terrain. Maybe have pod races on Tatooine, on Nal Hutta (however its spelled), the underbelly of Coruscant, having one in the forests of Endor, etc... with each track having unique features regarding different kinds of dangers.

Pod racing on the desert of Tatooine would be pretty different than flying through the wild forests of Endor or going through parts of the city of Coruscant (or a different planet like Coruscant).

I'm a huge board game hobbyist. This game idea has potential.

Update 1 after playtesting a few laps:

- 3 advantages and threats work best. 2 slows down the game

- difficulty counts as one movement -- so to move over an easy hex equals one success, to move over a hard hex equals three success // if you can not pass, you stop on that hex... The starting difficulty makes up for the bonus you get by ending your movement on that hex...

I was also thinking about using the despair, that was my first idea, for fatal crashing, but after playing I noticed that I never use the red die :-) ... That didn't work :-)

To get the feeling of different planets, I use the random placing of tiles... To make 'realistic' Tattooine tracks and others would take me a bit too far in version 1.0 :-) Any ideas are welcome though...