20 x 20 Infinity Mission System Feedback Thread

[Prophet_of_Doom]

I have given the Destroy Beacon mission a bit of thought. It would make sense to set up an exlusion zone there. You could insert:

Exclusion Zone : No trooper or marker (including hidden deployment) may be placed inside the opponent’s half of the table during initial deployment.

Into the mission description. This way no super killer infiltrating and impersonating ninja could destroy the beacon early in Round 1. This goes a bit against my idea that all skills should be able to be used in the scenarios. But I guess the hardship would weigh less than the benefit for the scenario. Superior infiltrators could still use their infiltration skill, just not to the max. AD troopers can still jump right next to the beacon if they dare.

[Prophet_of_Doom]

I fixed up some little things, so the current download is v1.4 now.

[TanKoL]

Damn you, I printed it out yesterday !
Meh, V1.3 will be good enough for now

[Prophet_of_Doom]

I am really sorry about that. unfortunately i have to use the forum readers as my proofreaders and playtesters. You have all done very well.

I did not change much. just a typo and a clarification oin the evacuate diplomats mission. If you cant place an objective or civvie due to dispersion, your opponent gets to place it. No reason to print this out again, i believe. Thank you very much for your interest.

[TanKoL]

Eh, no need to apologize mate
You're doing a great job with this mission system

[funmomiji]

Is a reason not to make the missions get 10 points like regular infinity missions? Can be cool make a tournament with different types of missions.

[Prophet_of_Doom]

This system is designed to be used in tournaments. I could have used 10 points, but have seen no real reason to do so. I thought 8 would be cool, because the digit almost looks like the symbol for infinity.

[Errhile]

Well, if you are ever going to update it, this would be a neat idea (just in case some TO wishes to use both 20x20 and ITS missions in the same tournament).

So far, my bunch seems to have switched from YAMS to 20x20 almost completely

[Prophet_of_Doom]

Well, if you are ever going to update it, this would be a neat idea (just in case some TO wishes to use both 20x20 and ITS missions in the same tournament).

I will update it. I have not considered this compatibility issue. ITS does not seem to work on a fixed number like 20x20. The last tournament I attended, I won games but got a low score because there was not enough time to play all three rounds in each game. A bit silly, that could not happen in 20x20 I believe. If it is an advantage, i will change to 10 points, which is mathematically less neat.

So far, my bunch seems to have switched from YAMS to 20x20 almost completely

Really? That makes my day! They are very welcome for further feedback. 20x20 version 2 should be my next project.

[Errhile]

Well, that's the truth. We still haven't tried all of these, though.

I'll pass you any feedback should I hear any. Basically, we consider 20x20 to be a better system than YAMS, because it doesn't make each player follow a different set of objectives.

[funmomiji]

Thanks for the update! I use all the time! Time to ckeck the changes.

[Sobakaa]

Gonna give it a go, thanks. First version was very good.

[Errhile]

And from what I've seen, v2 is even better.

One thing I would love to see clarified is a defined size for the objectives. Now, when we have N3 Silhouettes, it could be pretty easy to give almost all of these a Silhouette value. Actual, physical representations of objectives - i.e. terrain/objective models - are great, but I'd prefer to know how big one should I be using.

[el_presidente]

Errhile makes a good point. I've just assumed that all the OM are on 40mm bases, but never bothered with the height. Over here we just say that the OM provide cover

[MARC C]

And from what I've seen, v2 is even better.

One thing I would love to see clarified is a defined size for the objectives. Now, when we have N3 Silhouettes, it could be pretty easy to give almost all of these a Silhouette value. Actual, physical representations of objectives - i.e. terrain/objective models - are great, but I'd prefer to know how big one should I be using.

Very good point. For my last event I ruled that S6 was the silhouette for consoles and transmission antennas.

[Prophet_of_Doom]

The idea with the silhouettes is interesting. The reason why I was less specific about this is that I want to give people the flexibility to play with what they have. So if people don t have crates, they can use objective markers. Markers don t have a visible height and I think it is easier to play in a what you see is what you get" way.

I prefer to have physical crates or consoles as objectives. I accept any height they may have.

Of course, you can play using silhouettes. My ideas for the scenario objectives are like this:

Access Supplies: 25mm Silhouette 2 crates. I guess 40 mm and silhouette 3 would be more realistic.



Collect debris: prone silhouette 1 markers. This mission uses 12 markers. I don t expect people to have that much crates etc. I play it with using whatever tokens we have at hand and putting them upside down.

Destroy beacon: Definitely S3 and 40mm here.

This mission is a clear break with my general principle that a maximum of 2 crates and 2 civvies per person is required.

Seize Hardware S2 25 mm
Teseum run: The caches should be 40mm, but the teseum shard tokens just the normal ones. Consider the shards to be prone.

Launching sequence: S3 would not hurt here.

Recover Data: Use 25 mm S2 markers for the consoles.

If N3 Human Sphere brings changes, I may want to release a version 2.5 I could include such measurements. I haven t really seen this as an issue. I think ITS is not that specific on this topic either.

[Errhile]

Nah, that's fine.

Debris being S0 25mm's for example means it is almost impossible to use them as cover. Which is good - not because you can't use thme for cover, but because you exactly know whather you can or can not (in this case, not).

And so on.

I guess I'll have to get some 25mm-based consoles from MAS witrh my next order (the ones initially meant ofr Campaign Paradiso don't fit too wellonto 25mm bases, but they are fine on 40mm bases), but I don't conisder that a problem

[Prophet_of_Doom]

I think people should just use whatever they have that fits the description.

[Sobakaa]

Hey guys, can you clarify something please? Some missions (like Data Recovery) have only this constraint written:

Data can be downloaded multiple times from the same console during the game. However, it is not
possible to download data more than once from each console in a player’s turn. Take count on
how often each player has successfully downloaded.

So, it means that a single trooper can potentially make this roll 3 times in a row (3 game rounds)?

[Prophet_of_Doom]

Hey guys, can you clarify something please? Some missions (like Data Recovery) have only this constraint written:

Data can be downloaded multiple times from the same console during the game. However, it is not
possible to download data more than once from each console in a player’s turn. Take count on
how often each player has successfully downloaded.

So, it means that a single trooper can potentially make this roll 3 times in a row (3 game rounds)?

I guess the answer to this question is yes.

Now I will try to make this super clear:



Each console can be downloaded from once per turn, meaning 3 times during the 3 turns of the game.
3 consoles times three game turns equals 9. Therefore, the maximum number of downloads for each player is 9.

A trooper can try as many times as needed to make the roll. However, once this succeeds at one console, no own trooper can download again in the same player turn at the same console. The trooper could stay at the console and do it again in the next active phase of the owning player.

Is this clear? If not, I am happy to try again. You are also welcome to ask me to clear other things up. This helps me identify phrases which are not clear enough.

[Sobakaa]

Thanks, Prophet. At first i thought that giving a single trooper an ability to just continuously roll on the same device/artifact/console was a bit too good in case of some infiltrating camo hi dudes, but then i figured that he'll score just 3 points for the whole game, which is not a big deal.
I also noticed that this thread is for 1st ed of 20x20, but i came here from 2nd ed post on Data Sphere, you might want to fix that.

[Prophet_of_Doom]

well, I guess people write where ever they want to.

The idea in Data Recovery is that troopers indeed try stay at a console and download data every turn. The opponent is unlikely to just let that happen, so the fight is for the control of the consoles. TO camo infiltrators obviously have a an easy time getting to the consoles, but they reveal once they download and can then be attacked. I have played this scenario several times and there is no problem with infiltrators that I see.