176

(0 replies, posted in Starmada)

Just because there wasn't anything like this out in the world before now, I've put together a simple SDS for players to use. Free to download and copy for personal use.

177

(3 replies, posted in Starmada)

Yes. A thrust of 0 in order to rotate without changing direction is a valid option.

178

(2 replies, posted in Starmada)

In addition to computing the number of shields in each arc, an adjustment is also made for the total number of shields.

In this case, the E4 has 81 total shields in Federation Commander. At 5:1, this translates to 16 Starmada shield boxes. However, 7-4-4-3 is a total of 18, so we have to reduce this by 2. Dropping each of the port/starboard arcs gets us where we need to be.

179

(14 replies, posted in Starmada)

I would be willing to continue for as long as ADB provides me with material.

180

(3 replies, posted in Starmada)

Put together a couple of alternate movement systems for Starmada. Check 'em out... feedback appreciated.

181

(14 replies, posted in Starmada)

I have almost all the information required to get started on Rumors of War after the holiday. That will include the Andromedans, Vudar, and ISC.

182

(14 replies, posted in Starmada)

I am hoping to provide both Distant Armada and Battleships Armada to ADB by Thanksgiving.

183

(46 replies, posted in News)

No specific reason, no.

184

(9 replies, posted in Starmada)

Marauder wrote:

Or course with no saves it's tempting to just go plain Jane and go imp=1, dmg=1, no traits and swarm their defenses. If I take a trait (or higher imp/dmg), I get less seekers for the same price, but they are just as easy to shoot down, so I end up with a lesser attack.

Which is why the ORAT computation for seeking weapons is also changing. I've acknowledged before the current calculation is horribly out of whack, so I'm taking the opportunity to change it to (a) bring seekers into balance and (2) address the "Plain Jane" issue without recourse to saving throws.

185

(9 replies, posted in Starmada)

Marauder wrote:

DMG is definitely useless against fighters, but IMP has a small niche in taking out either heavy fighters or seeking weapons that have gained a save via their weapon traits.

One rule that is changing: seeking weapon saves are no longer a Thing.

186

(9 replies, posted in Starmada)

MRCAcct wrote:

I'm guessing that it's repeating but only on a 6 and not 5-6 as normal?

Correct.

187

(46 replies, posted in News)

MRCAcct wrote:

Been mucking around with this a bit more. I'm a big fan of Drake notation, and it's what I record all my ships in, so I'm hoping that'll be  implemented soon.

SOON.

The DISPLAY tab, when I go to select "1" from the filter in Column Y, makes (for me) an unholy mess of the sheet, specifically the weapons listing in Columns TUVW - just stretches and garbles it to death.

It SHOULD fix itself when you go to print it.

Not a big fan of the limited "weapon slots". The old sheet has 6 weapons with 6 arc slots each; max of 36 "weapon slots", where as the new one only has 12 at the moment.

It's a relatively simple matter to add more. But I had thought 12 would be enough...

Looking at the new weapon calcs, I'm not understanding the purpose of the MIN functions in Column I of WEAPONS; they'll always return a value of 1 as written, no matter what is entered into the cells.

I'm not sure what I was doing there.

And having gotten several sheets of scrap paper and hand written the new range formulas down, I think I understand most of it. And while it's great to have Range-based ROF/IMP/DMG as an option again, I find I much prefer the "old" method for weapons - range-based traits being a simple multiplier. So, will "old" calculations still be acceptable for those of us who don't want this much complexity?

Yes. The "old" system is still completely valid.

188

(14 replies, posted in Starmada)

Yes. I do not stock them.

189

(9 replies, posted in Starmada)

That's a good thought. Perhaps making the discount only applicable to ROF and ACC; high IMP and DMG are useless against fighters anyway.

190

(9 replies, posted in Starmada)

As has been noticed by several people, the Drydock v2 beta includes several weapon traits that aren't currently included in the Unity rulebook. Some of them are from the Star Fleet Universe (SFU) conversions; others are truly "new" but not yet implemented. Here is a quick guide:

Power Points (1PP/2PP/3PP/4PP) - The weapon requires a number of Power Points (PP) to fire. This is a SFU-only trait.

Accurate (Acr) - The existing Pinpoint trait is being renamed as this.

Armor Penetrating (AP) - The weapon ignores screens (soon to be renamed "Armor").

Evaporating (Evp) - Applied only to a Seeker weapon, this trait causes the flight to lose one Seeker at the end of every turn until it is gone. Used to reflect Plasma Torpedoes in the SFU.

Multi-Shot Expendable (Exp2/Exp3/Exp4) - The weapon can be fired a limited number of times; e.g. Exp3 means the weapon can be fired three times before being used up. The existing Expendable trait is the same as "Exp1".

Fighter-Exclusive (FtX) - The weapon can only be fired at tiny targets; it is too weak to have an effect on starships.

Pinpoint (Pnp) - The weapon is able to selectively target enemy systems. Each damage die that comes up 4-6 can be rerolled: 1-2 = Engines; 3-4 = Weapons; 5-6 = Shields.

Piercing {special} (Pr+) - This is used for the upcoming Full Thrust conversion.

Semi-Armor Penetrating (SAP) - The weapon applies half damage (rounded up) to the target's screens (soon to be renamed "Armor"); the rest goes through to the ship.

Shield-Killer (ShK) - This is a SFU-only trait.

Seeker (Skr) - Used to indicate the weapon is a Seeker.

Multi-Turn Slow (Slw2/Slw3) - The weapon can only be fired every third or every fourth turn (i.e. it must be inactive for either two or three turns).

Starship Exclusive (SsX) - The weapon can only be fired at starships; it is too big and/or imprecise to fire at tiny targets.

191

(2 replies, posted in Starmada)

1) No. "Rules that apply to fighters also apply to seekers, unless explicitly noted otherwise." (p.41)

2) This is not a "rule" as of yet, since the new drydock is still in beta testing. However, the intent is to use the closest range band for defensive fire.

3) The weapon traits in Drydock 2 that aren't currently defined in the Unity rulebook will be described in a separate post as soon as I get to it.

192

(46 replies, posted in News)

You people are never happy. smile

193

(46 replies, posted in News)

Yes. big_smile

194

(46 replies, posted in News)

What massive changes are you seeing?

You've rightly noted the removal of range-based traits. That's to go along with the ability to set different ROF/ACC/IMP/DMG values for each range band. Achieves the same result, but much more flexible.

For example, before you had to do this: 4-8-*; 1x5+/1/1 (Crn)

Now you can do this:

1-4; 1x4+/1/1
5-8; 1x5+/1/1

The other changes are just tweaks, and don't affect the rules themselves.

195

(46 replies, posted in News)

I can't replicate this.

196

(46 replies, posted in News)

Also, from your screenshot I can see the following edit needs to be made:

On the TABLES tab (you'll need to unhide it) go to cell N12 and change it to =SUM(SHIP1!E$20:E$31)*-0.3

197

(46 replies, posted in News)

On the SHIP1 tab, enter the following into cell X20.

=IF(K20=U$20,V$20,"")&IF(K20=U$21,V$21,"")&IF(K20=U$22,V$22,"")&IF(K20=U$23,V$23,"")&IF(K20=U$24,V$24,"")&IF(K20=U$25,V$25,"")&IF(K20=U$26,V$26,"")&IF(K20=U$27,V$27,"")&IF(K20=U$28,V$28,"")&IF(K20=U$29,V$29,"")&IF(K20=U$30,V$30,"")&IF(K20=U$31,V$31,"")

Then select cells X20:X31 and hit Ctrl-D.

Enter the following into cell U43.

=IF(LEFT(V33)="E",U33&CHAR(160)&REPT("▢",W33)&"│ ","")&IF(LEFT(V34)="E",U34&CHAR(160)&REPT("▢",W34)&"│ ","")&IF(LEFT(V35)="E",U35&CHAR(160)&REPT("▢",W35)&"│ ","")&IF(LEFT(V36)="E",U36&CHAR(160)&REPT("▢",W36)&"│ ","")&IF(LEFT(V37)="E",U37&CHAR(160)&REPT("▢",W37)&"│ ","")&IF(LEFT(V38)="E",U38&CHAR(160)&REPT("▢",W38)&"│ ","")&IF(LEFT(V39)="E",U39&CHAR(160)&REPT("▢",W39)&"│ ","")&IF(LEFT(V40)="E",U40&CHAR(160)&REPT("▢",W40)&"│ ","")&IF(LEFT(V41)="E",U41&CHAR(160)&REPT("▢",W41)&"│ ","")&IF(LEFT(V42)="E",U42&CHAR(160)&REPT("▢",W42)&"│ ","")

Enter the following into cell U44.

=IF(LEFT(V33)="T",U33,"")&IF(V33="T1"," ("&W33&")","")&IF(LEFT(V33)="T","; ","")&IF(LEFT(V34)="T",U34,"")&IF(V34="T1"," ("&W34&")","")&IF(LEFT(V34)="T","; ","")&IF(LEFT(V35)="T",U35,"")&IF(V35="T1"," ("&W35&")","")&IF(LEFT(V35)="T","; ","")&IF(LEFT(V36)="T",U36,"")&IF(V36="T1"," ("&W36&")","")&IF(LEFT(V36)="T","; ","")&IF(LEFT(V37)="T",U37,"")&IF(V37="T1"," ("&W37&")","")&IF(LEFT(V37)="T","; ","")&IF(LEFT(V38)="T",U38,"")&IF(V38="T1"," ("&W38&")","")&IF(LEFT(V38)="T","; ","")&IF(LEFT(V39)="T",U39,"")&IF(V39="T1"," ("&W39&")","")&IF(LEFT(V39)="T","; ","")&IF(LEFT(V40)="T",U40,"")&IF(V40="T1"," ("&W40&")","")&IF(LEFT(V40)="T","; ","")&IF(LEFT(V41)="T",U41,"")&IF(V41="T1"," ("&W41&")","")&IF(LEFT(V41)="T","; ","")&IF(LEFT(V42)="T",U42,"")&IF(V42="T1"," ("&W42&")","")&IF(LEFT(V42)="T","; ","")

198

(46 replies, posted in News)

You are correct. TEXTJOIN is not recognized by Office 2010.

Hmph.

199

(46 replies, posted in News)

Do me a favor... unlock the SHIP1 tab (password is "Drydock2") and show me what's happening in cells X20:X31.

200

(46 replies, posted in News)

Figured out the problem. CONCAT is a function that didn't exist prior to Office 365. Made the necessary adjustments and reuploaded.