RMU Attack Tables

I have spent my down time over Christmas working on a spreadsheet to create attack tables in the most usable format we have seen so far.

The biggest issue with RMU for me has been the size rules. There were two issues really, firstly, in incessant math required to even work out how much damage an attack does. It may be relatively simple math but it is a mechanical step that slows down almost every attack. In fact it is more than one step as a quick calculation is needed to work out the size of the attack before the attack roll and then a calculation after the attack roll to calculate the damage. Size also still effects the OB and DB of the targets, according to Beta 2 but that may have changed and it then adjusts the critical.

My second issue with the size rules is that it looks like a solution looking for a problem. The same progression that is being applied via the size rules is being applied every which where regardless of whether it works or not.

On one hand the proponents that like the size rules are seeing this as an elegant solution unifying many disparate game mechanics. Those, like me that do not like the rules just see a bad rule wrongly applied.

It is possible that I am wrong, according to Mrs R that has happened before.

To that end, the game I am going to run this year is going to use the size rules but there are some attack chart layouts that have been suggested on the forums that precalculate the size shifts.

So stating in the bottom left with Diminutive, then tiny, small, the bold result is the medium, then the top row, right to left is big, large and huge.

That image is from the spreadsheet I am working on. Merkir from the forums has shared a Google Sheet that will generate attack tables on the fly for any of the standard weapons. If I paste that into my spreadsheet it then explodes every individual result into the seven displayed sizes. That takes away one of the game slowing steps.

Another option is that once you paste the Merkir table into the spreadsheet you can apply adjustments to it. So Rather than a short sword being a Dagger +1 size I can apply a +10OB shift to the Dagger table and then generate a dedicated Short Sword table. I can do the same for two handed swords so they are no longer Broadswords +1 size. This takes away one more size calculation.

I accept that magic and things like charging will always involve a size shift. I do not have a problem with that. I personally feel that +1 size for charging is a retrograde step that harks all the way back to D&D basic rules where a charge just gave you double damage. +1 size does basically the same thing and ignores 40 years of increasing sophistication and any attempt to model what happens in the real world. I am happy to accept the size solution as it fits nicely with my desire for fast and simple rules.

The sizes of the damage shifts in my tables do not follow the RAW in beta 2. As Hurin has pointed out the RAW favours smaller attackers by giving them disproportionate amounts of damage. The result being that rabbits being overly dangerous.

My tables will diverge slightly from the standard tables and it is all down to rounding. Normally if you were doing 0.4 of a hit in damage you would expect that to be rounded down to nothing. The problem with this is that all touch magic requires a successful unarmed attack that delivers 1 hit. If you have a small or diminutive spell caster it is impossible for them to cast any magic against a foe in AT 9 or 10. For that reason I have chosen to always round up to the next whole hit in damage. So if the Medium attack did at least 1 hit then at all sizes at least 1 hit will be delivered.

This puts my charts mostly towards Hurin’s toned down charts, without the killer rabbits, but fractionally above them so a bit from a rabbit will still do 1 hit if it hits where the Hurin formula would have rounded down to zero.

What I have left to do is mostly donkey work of copy and pasting my spreadsheet formula into hundreds if not thousands of cells. I cannot just fill the spreadsheet as the formula has too many nested functions that Excel cannot cope with updating all the references to the look up tables. As soon as I have something to show I will share some finished tables with you. How much I can share is a different question as I think I am really on the edge of the Beta NDA if I start sharing complete sets of attack tables!



Big Beasts and Big Hits

There is an ongoing discussion on the RMU beta test forum over weapon sizes. How do you handle a halfling wielding a trolls dagger? Is the dagger a shortsword or a broadsword to the halfling. Does the fact that it was made for different hands make a difference to how you wield the weapon? There were complications where using an under or oversized weapon such as a undersized two handed weapon may be more effective than using a one handed weapon specifically made for you race. So all your human warriors are using halfling two handed swords rather than broadswords.

This is a long rambling debate and you can check the ICE forums if you want to get involved. One of the things I find frustrating is that one never really knows what the devs have taken on board, what their solution is, if any, and is just being ignored because that part of the rules is are already written.

I will say I am not a fan of the RMU size rules. I think they sound fine in principle but they just didn’t work for my play test group so much so that the group didn’t want to play any more.  The play test lasted two sessions!

So how do I handle size variation between different size combatants? I totally agree that all things being equal a giant hitting hitting a halfling should do more damage than the halfling hitting the giant. There is just more kinetic energy in the attack!

The big monster hitting the little character requires no modification. The big monster has its size and mass figured into its OB. So that was easy, just play the RAW.

The smaller combatant hitting a larger one though does need a slight adjustment. It doesn’t need the multiplied hits or stepping up and down for criticals. The very largest creatures have this built in in C&T anyway. So what I do is for every relative size smaller than Medium incurs a -10 OB, every relative step above Medium gives a +10 OB. That results in smaller creatures doing less damage and maybe a lesser crit. Larger combatants tend towards harder hits.

Breaking 150

In another closely related rule is my ‘breaking 150’. For me I use a +1 on your critical roll for every 10 more than 150 rolled. So an attack roll total of +175 would give a +2 to your critical. This also tends to mean that massive attacks tend to do better criticals. My critical tables have an UM66 and a second 66 result. Obviously you cannot shift your critical up to the UM66 result.

Wrong Size Weapons

So how do I handle wrong sized weapons. Well the weapon uses the table for what the weapon actually is. So a halfling using a human broadsword as a two handed sword still uses the broadsword table. But for every one step in size difference gives a -10 OB. This reflects the fact that the weapon was just not designed for that size hand.

It also takes into account that a dagger is a stabbing weapon designed for pushing into the gaps between armoured plates. A broadsword is a swinging weapon designed to use speed and mass to inflict damage. A human picking up a halfling breadsword does not change the shape and design of the weapon and turn it into a dagger.

So the example of Sting. Could Bilbo wield Sting? Sting is regarded as a Elven shortsword in RM terms. So Bilbo would be using it as a shortsword but at -10 OB. Chances are that Sting has a greater than +10 magical OB anyway so even with my penalty it is still worth using Sting in combat and its orc sensing powers make it even more useful.

So in conclusion I would say whilst it may not be the idea engineers solution my rules are very quick and easy to use, easy to understand and cope with all the combinations I have ever had to adjudicate on.