MT Combat and interupts

[tucker2]

I have a great deal of trouble utilizing interupts properly, especially after a long session and the caffeine doesn't work right anymore. The system gets insane if more than four folks are on either side(s), what with all the interupting interupts.

I pretty much chucked'em out, though I'd be interested to hear how others here deal with the things. What gives, fellas?

 

[tucker2]

I have a great deal of trouble utilizing interupts properly, especially after a long session and the caffeine doesn't work right anymore. The system gets insane if more than four folks are on either side(s), what with all the interupting interupts.

I pretty much chucked'em out, though I'd be interested to hear how others here deal with the things. What gives, fellas?

 

[tucker2]

I have a great deal of trouble utilizing interupts properly, especially after a long session and the caffeine doesn't work right anymore. The system gets insane if more than four folks are on either side(s), what with all the interupting interupts.

I pretty much chucked'em out, though I'd be interested to hear how others here deal with the things. What gives, fellas?

 

[Elliot]

This link has some dicussions

http://www.travellerrpg.com/cgi-bin/Trav/CotI/Discuss/ultimatebb.cgi?ubb=get_topic;f=46;t=000036

I have to say that I really like interrupts - but you have to get your players to know it instinctively -

If it helps I use snapshot/ahl maps and markers for MT combat and number markers for interrupts

 

[Elliot]

This link has some dicussions

http://www.travellerrpg.com/cgi-bin/Trav/CotI/Discuss/ultimatebb.cgi?ubb=get_topic;f=46;t=000036

I have to say that I really like interrupts - but you have to get your players to know it instinctively -

If it helps I use snapshot/ahl maps and markers for MT combat and number markers for interrupts

 

[Elliot]

This link has some dicussions

http://www.travellerrpg.com/cgi-bin/Trav/CotI/Discuss/ultimatebb.cgi?ubb=get_topic;f=46;t=000036

I have to say that I really like interrupts - but you have to get your players to know it instinctively -

If it helps I use snapshot/ahl maps and markers for MT combat and number markers for interrupts

 

[TheEngineer]

Hi !

Well, recursive combat systems can produce mess ...).

Thats why the basic rules and errata deal with the "only one active interupt is permitted per side" aspect.
That keeps things more easy and IMHO works quite well, too.

In order to get along with hardcore interupting, I use - like in programming - a stack system.
Use a few gaming cards, each representing the PCs and NPCs.
If its somebodies turn, play his card, if he is interupted put the approriate card on the deck.
If somebody should be able to conclude his turn, remove the card from the deck.
This might help to keep the story going on and provides some information about the combatants status.

But be careful with stack overflows....

Page 68, Interrupt Restrictions (revision): Strike the rule that states a unit cannot
interrupt the turn of another on his own side. The idea with this rule was to avoid a
complicated chain of interrupts. However, as some players have pointed out, sometimes
a character on your own side may do something stupid, and it makes sense to be able
to interrupt to either help him out or to try and stop him. The rule of no more than
one interrupt per side serves quite well to keep interrupts in check.

Regards,

Mert

 

[TheEngineer]

Hi !

Well, recursive combat systems can produce mess ...).

Thats why the basic rules and errata deal with the "only one active interupt is permitted per side" aspect.
That keeps things more easy and IMHO works quite well, too.

In order to get along with hardcore interupting, I use - like in programming - a stack system.
Use a few gaming cards, each representing the PCs and NPCs.
If its somebodies turn, play his card, if he is interupted put the approriate card on the deck.
If somebody should be able to conclude his turn, remove the card from the deck.
This might help to keep the story going on and provides some information about the combatants status.

But be careful with stack overflows....

Page 68, Interrupt Restrictions (revision): Strike the rule that states a unit cannot
interrupt the turn of another on his own side. The idea with this rule was to avoid a
complicated chain of interrupts. However, as some players have pointed out, sometimes
a character on your own side may do something stupid, and it makes sense to be able
to interrupt to either help him out or to try and stop him. The rule of no more than
one interrupt per side serves quite well to keep interrupts in check.

Regards,

Mert

 

[TheEngineer]

Hi !

Well, recursive combat systems can produce mess ...).

Thats why the basic rules and errata deal with the "only one active interupt is permitted per side" aspect.
That keeps things more easy and IMHO works quite well, too.

In order to get along with hardcore interupting, I use - like in programming - a stack system.
Use a few gaming cards, each representing the PCs and NPCs.
If its somebodies turn, play his card, if he is interupted put the approriate card on the deck.
If somebody should be able to conclude his turn, remove the card from the deck.
This might help to keep the story going on and provides some information about the combatants status.

But be careful with stack overflows....

Page 68, Interrupt Restrictions (revision): Strike the rule that states a unit cannot
interrupt the turn of another on his own side. The idea with this rule was to avoid a
complicated chain of interrupts. However, as some players have pointed out, sometimes
a character on your own side may do something stupid, and it makes sense to be able
to interrupt to either help him out or to try and stop him. The rule of no more than
one interrupt per side serves quite well to keep interrupts in check.

Regards,

Mert

 

[theSea]

But be careful with stack overflows....

Yea - I hear those can be exploited to get your ref to run arbitrary code

 

[theSea]

But be careful with stack overflows....

Yea - I hear those can be exploited to get your ref to run arbitrary code

 

[theSea]

But be careful with stack overflows....

Yea - I hear those can be exploited to get your ref to run arbitrary code

 

[TheEngineer]

Originally posted by theSea:
</font><blockquote>quote:</font><hr />But be careful with stack overflows....

Yea - I hear those can be exploited to get your ref to run arbitrary code </font>[/QUOTE]Hey, THATS worth a try.....

 

[TheEngineer]

Originally posted by theSea:
</font><blockquote>quote:</font><hr />But be careful with stack overflows....

Yea - I hear those can be exploited to get your ref to run arbitrary code </font>[/QUOTE]Hey, THATS worth a try.....

 

[TheEngineer]

Originally posted by theSea:
</font><blockquote>quote:</font><hr />But be careful with stack overflows....

Yea - I hear those can be exploited to get your ref to run arbitrary code </font>[/QUOTE]Hey, THATS worth a try.....

 

[tucker2]

Thanks for heads-up, I'll peruse what has gone before.

 

[tucker2]

Thanks for heads-up, I'll peruse what has gone before.

 

[tucker2]

Thanks for heads-up, I'll peruse what has gone before.