Bren

No, at most a handful. In the US, we do a lot of green field construction. Because we have a lot of fields, in most locales our tax and other incentives favor new construction, and people who can afford it, tend to like building a new house, rather than fixing up an old house. But that's as much off topic as I should allow myself.

Did the Romans routinely apply those traditions to their non-Roman enemies? I don't know the answer. Though some of Caesar's campaigns against fellow Romans had quite low casualties. I seem to recall fighting in Hispania against Pompey's troops that were a war of maneuver with few casualties for the defeated. (Probably in part so that big Julie could recruit the survivors into his armies.) It seems to me, that the Greek city states considered other Greeks to be part of a category of we Greeks, rather than being an other. That may have contributed to the much higher ratio of Persian casualties at Marathon. The Romans initially seemed to divide the world into Romans and others. Now once Rome started acquiring allied states, they had three categories: Romans, allies, and others. Fighting others, usually makes it easier to inflict heavy casualties. In addition, for various reasons of tradition and superstition, the Romans contrived to interpret all of their wars as defensive wars. I think that their defensive claim probably encouraged infliction of higher casualties on the vanquished.

Chronic pain often interrupts sleep and chronic pain isn't the same as unbearable pain. Most chronic pain is, more or less, bearable. It seems reasonable to me that "unbearable pain" would interrupt a light sleep.

In the real world, I've seen a house jacked up from the foundation and transported by road.

True, but a light sleep. The description says, "Once the spell expires, the target moves into a light sleep, and awakens easily." We aren't talking about using Sleep as a 3-point cure for simple insomnia outside of combat. The unbearable pain that Mossmac uses in their example would awaken a light sleeper after two minutes, so not much rest. Needing to spend 90 MPs to give a sufferer an hour of rest falls into what I would call effectively useless for the noncombat purpose described.

Several points: In the article the author checked his numbers against battles with lists of the fallen, which were done by name. That seems like a very accurate method of counting. Do we have such accurate lists for Rome's battles? I believe there is pretty good evidence that Caesar, for example, overestimated enemy casualties in his Commentaries. So potentially the loser's casualties are overestimated. My impression is that Classical Greek city states had a level of formality and, I guess civility is the word, in most or many of their battles. Once the battle was over, a truce was declared so that each side can collect and bury their dead. I don't recall the Roman's doing that. Their wars seemed to follow more of a total war model. If the Spartans had conducted war in the Roman fashion, there would have been no Athens or Athenians at the end of the Peloponnesian War. Historically, Carthage didn't survive the Punic Wars. If war is conducted differently, casualty ratios could easily change. My impression lately, is that Alexander is kind-of, sort-of a model for Argrath. If we accept that, then the wars of Alexander (and probably his father Philip) may provide a better model. I don't know what those casualty ratios would look like. They may not be too accurate as I've seen some extremely high numbers for the Persians vs. Alexander. (Not as bad as the numbers Herodotus gives us, but still suspiciously high. That said, I wouldn't be surprised if the losses for the losing side would be higher than for Classical Greek battles. Obviously, everyone is free to choose the model they find most convincing or enjoyable. What I like about the lower casualty figures is that I think players would find lower losses on their side more fun. Low casualty ratios make it reasonable that player characters are unlikely to be killed in battle by one bad die roll. In addition, for campaigns where multiple battles are a significant feature such as player led war bands or companies, clan vs. clan conflict, or where a player character has the roll of warband leader, chieftain, or rex, having lower troop casualties is probably more fun than the players losing 20% or more of their troops or clan fighters every time a battle occurs. And from he GM perspective, I don't want to have to create or stat up new clans, companies, or regiments to oppose the players. And, in the same way that lower ratios justify low probability of PC/protagonist death, they also justify low probability of antagonist death.

Nor in the RQ3 rules.

Sleep has a 10 round duration. Two minutes isn't much of a rest. Still basically useless.

Is it out yet? Is it out yet? [This should be heard in the voice of an 8-year old on a long family car ride.]

So, hostile, but not enemies. Gotcha. 😉

The Punic Wars were a different style of combat than most battles in Classical Greece. And those two battles are exceptions from the vast majority of battles in history. Cannae is highly unusual. It was one of the greatest tactical defeats in history. The Roman army was completely enveloped. Virtually none of the Romans could retreat. Lake Trasimene, while not as bad, had the Roman army completely surprised while strung out along their line of march. The army never had no command and control and never had a chance to form up. Many groups were destroyed piece meal.

I like the idea that the target says something like, "So sleepy..." as they lie down and curl up for sleep. If this was in a movie the scene would be funny and would easily let the audience know what just happened and that the victim was asleep, not dead. Neither are bad side effects in an RPG session. As far as the fictional plausibility of people falling unconscious without being injured by the fall to the ground, we have just about every action movie or science fiction franchise ever as precedent. Nobody in a noir detective story breaks their nose or sprains their wrist when the fall down after being sapped or hit with a gun barrel* and nobody in Star Trek or Star Wars gets stunned and then breaks their arm while falling to the ground. * Not to mention the infrequency of any actual brain damage from repeated closed head trauma for the likes of Sam Spade or Philip Marlowe.

Tossing Sleep at a swimmer would be another problem area.

The Gamemaster Adventures lists Chalana Arroy among the deities with shrines in the Colymar tribe (p. 14) and the Chalana Arroy priestess, Kerisdana Hollybright, as being at the Lighbringers Temple in Clearwine. So shrines but no dedicated temples.

I had a chance to read the article. I had to look at his table twice to figure out how he calculated his ratios, but it is interesting how low the casualties were for the losers. The author identifies a lack of effective pursuit by the Greeks, as a major factor (perhaps the major factor) in the low casualties for the loser compared to many other battles. I wonder it this might be a good model for typical Orlanthi warfare. I can see where chasing down and killing fleeing enemies might conflict with Honor.

Thanks for sharing that, I'll give it a read. Casualties for the victors is about what I would have guessed. Casualties for the losers seem low unless there was either little or no pursuit by cavalry or light infantry or else virtually the entire phalanx surrendered en mass.

Thanks for a succinct explanation for the oncoming train. Now I want to watch a Road Runner cartoon from the point of view that the Road Runner is High Priest casting Eurmali spells. Hey, wait a minute. If a Eurmali had the Rune spell, Become Road Runner and enough Rune points, they could be the Road Runner.

I'm finding this way of thinking about Illusions and, by extension, Hallucinate to be very helpful. Thanks! Road Runner cartoons also help me to visualize Gloranthan Illusions. When Wiley Coyote paints a tunnel mouth on the side of a cliff, the painted tunnel mouth for him is just paint on the wall. He can't go through the tunnel. But for the Road Runner (and any oncoming trains) the painted tunnel mouth acts just like a real tunnel mouth. For a few moments it is a real tunnel mouth. In Gloranthan magic terms, Coyote paints a tunnel mouth, then the Road Runner casts Hallucinate so he can pass through the tunnel mouth. (For the moment, like Wiley Coyote, we shall ignore the oncoming train.) Painting the tunnel mouth doesn't correspond to anything in Gloranthan magic, but we, the audience, need the Coyote to paint a tunnel mouth before the Road Runner casts his hallucinate so we can understand what happens. And because it is funnier with a visible tunnel mouth.

A koku is 48 gallons. Wikipedia tells me a koku of rice is enough rice to feed 1 person for a year. (And presumably they don't only eat rice.) A bushel is 8 gallons. Clearly, that is not enough to feed 1 person for a year.

Jeff, would you please explain a bit about why it now doesn't make sense to you? (Apologies, if you have explained elsewhere, but if so, I missed it.)

I don't sweat an exact rationale, but it is easier for me to envision the world if I assume demographics are similar to Earth's bronze age and/or classical antiquity. Glorantha seems to have a higher proportion of women in roles (like warrior) that on Earth were primarily masculine. I assume this decreases the birth rate so the counterbalancing factors aren't only monsters and magical peril .

If it sinks, even a little, it displaces water. So we are back to displacing water. Just like the boat.

No. But if it doesn't displace any water it is nearly frictionless. Which is why I see the boat and the raft as the same. Either both work or neither works.

Although the colors are different, it reminds me of parts of Rainbow Mound. Why either or? Use sea trolls.

A trap I find easy to fall into. One of the things that drew me to Runequest back in 1979 or so was a world simulation/emulation design emphasis (monster stats same as PC stats, Greg's comment, etc.). I've only recently felt like I both understood and felt comfortable with the PC focused, RQG design philosophy.