Barnum

Current Roster:

Raindance

Velocity

Freedom Eagle

Emissary

That should do it. We'll need to wait until Freedom Eagle is approved before he can start posting. In the meantime, I'll look over the characters and make whatever adjustments need to be made to the encounter. Look for an opening post this weekend.

*is excited*

Current Roster:

Raindance

Velocity

Freedom Eagle

Emissary

That should do it. We'll need to wait until Freedom Eagle is approved before he can start posting. In the meantime, I'll look over the characters and make whatever adjustments need to be made to the encounter. Look for an opening post this weekend.

*is excited*

I think that would work just fine.

For most of the more "free-form" threads, you could probably forgo the OOC thread altogether. We could easily identify the OOC threads by prefixing them with [OOC] or suffixing them with (OOC). Once the thread is complete, you could leave it in the form for all to read, but move the OOC thread to an archive. Should work great.

I think that would work just fine.

For most of the more "free-form" threads, you could probably forgo the OOC thread altogether. We could easily identify the OOC threads by prefixing them with [OOC] or suffixing them with (OOC). Once the thread is complete, you could leave it in the form for all to read, but move the OOC thread to an archive. Should work great.

I think that would work just fine.

For most of the more "free-form" threads, you could probably forgo the OOC thread altogether. We could easily identify the OOC threads by prefixing them with [OOC] or suffixing them with (OOC). Once the thread is complete, you could leave it in the form for all to read, but move the OOC thread to an archive. Should work great.

I think that would work just fine.

For most of the more "free-form" threads, you could probably forgo the OOC thread altogether. We could easily identify the OOC threads by prefixing them with [OOC] or suffixing them with (OOC). Once the thread is complete, you could leave it in the form for all to read, but move the OOC thread to an archive. Should work great.

I think that would work just fine.

For most of the more "free-form" threads, you could probably forgo the OOC thread altogether. We could easily identify the OOC threads by prefixing them with [OOC] or suffixing them with (OOC). Once the thread is complete, you could leave it in the form for all to read, but move the OOC thread to an archive. Should work great.

Combats would almost certainly not be the only time that we will need an OOC thread for dice rolls, character tracking, character belongings, maps, etc.

My second encounter shouldn't have any combat at all, but it will require the characters to explore, investigate, gather clues, etc. How would you like to handle those?

Combats would almost certainly not be the only time that we will need an OOC thread for dice rolls, character tracking, character belongings, maps, etc.

My second encounter shouldn't have any combat at all, but it will require the characters to explore, investigate, gather clues, etc. How would you like to handle those?

Combats would almost certainly not be the only time that we will need an OOC thread for dice rolls, character tracking, character belongings, maps, etc.

My second encounter shouldn't have any combat at all, but it will require the characters to explore, investigate, gather clues, etc. How would you like to handle those?

Combats would almost certainly not be the only time that we will need an OOC thread for dice rolls, character tracking, character belongings, maps, etc.

My second encounter shouldn't have any combat at all, but it will require the characters to explore, investigate, gather clues, etc. How would you like to handle those?

Combats would almost certainly not be the only time that we will need an OOC thread for dice rolls, character tracking, character belongings, maps, etc.

My second encounter shouldn't have any combat at all, but it will require the characters to explore, investigate, gather clues, etc. How would you like to handle those?

How do you want to handle OOC threads and other threads for tracking HPs, wounds, etc? Post them in the same forum with the IC threads? Or should we try to run everything (OOC, characters, dice, etc.) all in one thread?

How do you want to handle OOC threads and other threads for tracking HPs, wounds, etc? Post them in the same forum with the IC threads? Or should we try to run everything (OOC, characters, dice, etc.) all in one thread?

How do you want to handle OOC threads and other threads for tracking HPs, wounds, etc? Post them in the same forum with the IC threads? Or should we try to run everything (OOC, characters, dice, etc.) all in one thread?

How do you want to handle OOC threads and other threads for tracking HPs, wounds, etc? Post them in the same forum with the IC threads? Or should we try to run everything (OOC, characters, dice, etc.) all in one thread?

How do you want to handle OOC threads and other threads for tracking HPs, wounds, etc? Post them in the same forum with the IC threads? Or should we try to run everything (OOC, characters, dice, etc.) all in one thread?

[Edit] Shadow to the rescue (see below). Metamorph is a power feat for Morph. I just missed it.

[Edit] Shadow to the rescue (see below). Metamorph is a power feat for Morph. I just missed it.

[Edit] Shadow to the rescue (see below). Metamorph is a power feat for Morph. I just missed it.

[Edit] Shadow to the rescue (see below). Metamorph is a power feat for Morph. I just missed it.

[Edit] Shadow to the rescue (see below). Metamorph is a power feat for Morph. I just missed it.

It really does.

I do think we can be somewhat flexible, as long as we do it in a measured fashion. Such as . . .

After the first major encounter, players that want to move on can, and new players can be added. I'm going to try to keep things really "open" given the nature of what Endless Flight is trying to do here.

More info coming in the next day or so.

So, if my short campaign has 6 "encounters: the first battle, the clean-up, the investigation, the second battle, the fall-out, and the third battle. We fight the first battle with four heroes. At the end of that encounter, old players can move on, new players can join. Then we play the second encounter, etc, etc.

It really does.

I do think we can be somewhat flexible, as long as we do it in a measured fashion. Such as . . .

After the first major encounter, players that want to move on can, and new players can be added. I'm going to try to keep things really "open" given the nature of what Endless Flight is trying to do here.

More info coming in the next day or so.

So, if my short campaign has 6 "encounters: the first battle, the clean-up, the investigation, the second battle, the fall-out, and the third battle. We fight the first battle with four heroes. At the end of that encounter, old players can move on, new players can join. Then we play the second encounter, etc, etc.

It really does.

I do think we can be somewhat flexible, as long as we do it in a measured fashion. Such as . . .

After the first major encounter, players that want to move on can, and new players can be added. I'm going to try to keep things really "open" given the nature of what Endless Flight is trying to do here.

More info coming in the next day or so.

So, if my short campaign has 6 "encounters: the first battle, the clean-up, the investigation, the second battle, the fall-out, and the third battle. We fight the first battle with four heroes. At the end of that encounter, old players can move on, new players can join. Then we play the second encounter, etc, etc.