Data Developers - Please use this issue to push new releases if doing so via comment.

Explainer

• Create an issue comment that starts with /release on the first line.
• Second (non-empty) line will be used as a release title/name.
• All following lines will be interpreted as a release description/body.
• Description (even if empty) will always be appended with a comparison link to the previous release, unless there is no previous release.

How to

Add a comment with one of the following to push a release:

For a standard release:

given latest release v2.2.2, will create a release v2.2.3 (increases patch)

/release

This is title of v2.2.3

For a Chapter Approved/Big FAQ initial releases (game-wide updates):

given latest release v2.2.2, will create a release v2.3.0 (increases minor, resets patch)

/release bump=minor

This is title of v2.3.0

For a new game edition:

given latest release v2.2.2, will create a release v3.0.0 (increases major, resets minor and patch)

/release bump=major

This is title of v3.0.0

Currently, the Rebel Guerillas are missing the spotters, Pioneers, and Veterans, along with their equipment and abilities. in addition, the jeeps do not have the ability to upgrade with heavy plating. This is missing due to the current version being v2 while the current is v2.6 (https://onepagerules.com/portfolio/grimdark-future/)

Spotters [5] Qua 5+ Def 5+ Carbines (18”, A1), CCWs (A1) Scout, Stealth I 85pts
Pioneers [5] Qua 5+ Def 5+ Shotguns (12”, A2), CCWs (A1) Ambush, Dug In J 90pts
Veterans [5] Qua 4+ Def 4+ Carbines (18”, A1), CCWs (A1) Fearless A, G 90pts

I Replace any Carbine:
Marksman Rifle (30”, A1, AP(1)) +5pts
HE Rifle (30”, A1, AP(1), Blast(3)) +10pts
AT Rifle (30”, A1, AP(4), Deadly(3)) +15pts
Upgrade any model with:
Spotting Laser +15pts

J Replace any Shotgun:
Flamethrower (12”, A6) +5pts
Fusion Rifle (12”,A1,AP(4),Deadly(6)) +10pts
Replace any CCW:
Energy Sword (A2, AP(1), Rending) +5pts
Energy Fist (A2, AP(2)) +10pts

L Upgrade with:
Heavy Plating (Tough(+3)) +55pts

Special Rules:
Dug In: Enemies charging this unit don’t count as having charged for the purpose of special rules, and they must take a dangerous terrain test before attacking.
Spotting Laser: This model may try to mark an enemy unit instead of firing one of its weapons. Pick one enemy unit within 36” and line of sight and roll one die, on a 4+ it’s marked. Friendly units may remove markers from the target to get +X to their shooting rolls against the marked unit, where X is the number of removed markers.

Data Developers - Please use this issue to push new releases if doing so via comment.

Explainer

• Create an issue comment that starts with /release on the first line.
• Second (non-empty) line will be used as a release title/name.
• All following lines will be interpreted as a release description/body.
• Description (even if empty) will always be appended with a comparison link to the previous release, unless there is no previous release.

How to

Add a comment with one of the following to push a release:

For a standard release:

given latest release v2.2.2, will create a release v2.2.3 (increases patch)

/release

This is title of v2.2.3

For a Chapter Approved/Big FAQ initial releases (game-wide updates):

given latest release v2.2.2, will create a release v2.3.0 (increases minor, resets patch)

/release bump=minor

This is title of v2.3.0

For a new game edition:

given latest release v2.2.2, will create a release v3.0.0 (increases major, resets minor and patch)

/release bump=major

This is title of v3.0.0

Data Developers - Please use this issue to push new releases if doing so via comment.

Explainer

• Create an issue comment that starts with /release on the first line.
• Second (non-empty) line will be used as a release title/name.
• All following lines will be interpreted as a release description/body.
• Description (even if empty) will always be appended with a comparison link to the previous release, unless there is no previous release.

How to

Add a comment with one of the following to push a release:

For a standard release:

given latest release v2.2.2, will create a release v2.2.3 (increases patch)

/release

This is title of v2.2.3

For a Chapter Approved/Big FAQ initial releases (game-wide updates):

given latest release v2.2.2, will create a release v2.3.0 (increases minor, resets patch)

/release bump=minor

This is title of v2.3.0

For a new game edition:

given latest release v2.2.2, will create a release v3.0.0 (increases major, resets minor and patch)

/release bump=major

This is title of v3.0.0

Data Developers - Please use this issue to push new releases if doing so via comment.

Explainer

• Create an issue comment that starts with /release on the first line.
• Second (non-empty) line will be used as a release title/name.
• All following lines will be interpreted as a release description/body.
• Description (even if empty) will always be appended with a comparison link to the previous release, unless there is no previous release.

How to

Add a comment with one of the following to push a release:

For a standard release:

given latest release v2.2.2, will create a release v2.2.3 (increases patch)

/release

This is title of v2.2.3

For a Chapter Approved/Big FAQ initial releases (game-wide updates):

given latest release v2.2.2, will create a release v2.3.0 (increases minor, resets patch)

/release bump=minor

This is title of v2.3.0

For a new game edition:

given latest release v2.2.2, will create a release v3.0.0 (increases major, resets minor and patch)

/release bump=major

This is title of v3.0.0

Data Developers - Please use this issue to push new releases if doing so via comment.

Explainer

• Create an issue comment that starts with /release on the first line.
• Second (non-empty) line will be used as a release title/name.
• All following lines will be interpreted as a release description/body.
• Description (even if empty) will always be appended with a comparison link to the previous release, unless there is no previous release.

How to

Add a comment with one of the following to push a release:

For a standard release:

given latest release v2.2.2, will create a release v2.2.3 (increases patch)

/release

This is title of v2.2.3

For a Chapter Approved/Big FAQ initial releases (game-wide updates):

given latest release v2.2.2, will create a release v2.3.0 (increases minor, resets patch)

/release bump=minor

This is title of v2.3.0

For a new game edition:

given latest release v2.2.2, will create a release v3.0.0 (increases major, resets minor and patch)

/release bump=major

This is title of v3.0.0

Data Developers - Please use this issue to push new releases if doing so via comment.

Explainer

• Create an issue comment that starts with /release on the first line.
• Second (non-empty) line will be used as a release title/name.
• All following lines will be interpreted as a release description/body.
• Description (even if empty) will always be appended with a comparison link to the previous release, unless there is no previous release.

How to

Add a comment with one of the following to push a release:

For a standard release:

given latest release v2.2.2, will create a release v2.2.3 (increases patch)

/release

This is title of v2.2.3

For a Chapter Approved/Big FAQ initial releases (game-wide updates):

given latest release v2.2.2, will create a release v2.3.0 (increases minor, resets patch)

/release bump=minor

This is title of v2.3.0

For a new game edition:

given latest release v2.2.2, will create a release v3.0.0 (increases major, resets minor and patch)

/release bump=major

This is title of v3.0.0

/release
Robot Legions 2.18

Data Developers - Please use this issue to push new releases if doing so via comment.

Explainer

• Create an issue comment that starts with /release on the first line.
• Second (non-empty) line will be used as a release title/name.
• All following lines will be interpreted as a release description/body.
• Description (even if empty) will always be appended with a comparison link to the previous release, unless there is no previous release.

How to

Add a comment with one of the following to push a release:

For a standard release:

given latest release v2.2.2, will create a release v2.2.3 (increases patch)

/release

This is title of v2.2.3

For a Chapter Approved/Big FAQ initial releases (game-wide updates):

given latest release v2.2.2, will create a release v2.3.0 (increases minor, resets patch)

/release bump=minor

This is title of v2.3.0

For a new game edition:

given latest release v2.2.2, will create a release v3.0.0 (increases major, resets minor and patch)

/release bump=major

This is title of v3.0.0

Can't Upgrade Units with Frenzy