Baron Wulfraed

Without reading every line in the follow-ups... Both scan and sneak feel to me like something the GM would roll, and likely keep note as to which party members succeed, fail, fumble -- only revealing the results for experience checks after the scenario is done. After all, a fumbled scan could mean a party member detects something that isn't really there, so the GM would advise that character of <something> that isn't really significant. And a successful scan that doesn't find anything looks the same as a failed scan... Using a single roll and applying to each party member also seems suitable when using this method. Similar for sneak. Fumbled sneak likely brings out the entire armed populace of the facility. A failed sneak could mean one produced sound, but (GM discretion) it might do nothing more than make a few guards more alert, without actively seeking out the source ("Oh, it was likely just a rat dragging a spoon around").

So I should be expecting an email offer for the print edition soon? Having bought the PDF.

Concur: RQ:RiG exposes enough Gods/Goddesses to get some feeling for how they work, but getting a guide that (hopefully) provides information for raw GMs to create their own scenarios, encounters (and correlating rewards for such) -- instead of relying on pre-published adventure books which they may not be able to justify $$-wise.

CF: the warding cubes in Kurtz's Deryni series https://www.rhemuthcastle.com/index.php?topic=1947.0 https://www.rhemuthcastle.com/index.php?topic=1948.0

Separate on the skill page, add in real-time. However, the front page positions for weapons and spirit combat get the combined totals to reduce the need to flip over to he skill page. I'll need to restudy the rules for skill increase rolls again, after seeing the post two up from here...

Just a wild opinion here, but I'd likely interpret it that IF the wielder of longer weapon has used it to attack some third party, then that weapon is "out of position" to be an effect on the wielder of the shorter weapon. IE; as if WLW has no weapon or is turned to the side.

Probably easier to use Excel (or other spreadsheet) using merged cells for headings, etc. that cross columns. Locked cells for stuff that should not be changed ever, and cell formatting/styles for look...

Well -- Chaosium doesn't sell a print copy of the quick-start, and the PDF is a free download. That looks like someone applied a sepia tone overlay of the grey-scale cover page of the PDF to make it look like the full BRP rules (which is also PDF, just $$)

Though "thane" is an old anglo-saxon and/or Scottish term. https://www.merriam-webster.com/dictionary/thane https://www.britannica.com/topic/thane-feudal-lord So... Taking old French, sorcerie, which isn't enough different to care about, in my opinion. Maybe using a western transliteration of the Greek, μαγεία, which gives mageía (or μαγία, magia)

Blame the proponents of mixing different alphabets to create upper and lower case. After all... Roman period tended to favor what we would call block capitals (especially when carving inscriptions into capitols) Carolingian Minuscule only uses what we would refer to as lower-case letters. Uncial may be considered a Majuscule (all capitals) form, though I think many used a larger representation to emphasize initial capitals from the rest of the word/line. Though "half Uncial" looks to be a Minuscule form. The less said about black-letter/gothic, the better (apparently the dotted i and j came about as one form of black-letter had strokes that made m, n, u look like a series of iii [without dots])

Yeesh... Not only does the width between wheels matter, but the wheel diameters need to be large enough to let the rest of the cart clear the ground!

The common way distributed version control systems (Git and Mercurial -- I have the latter running locally as I don't work on anything meant to be seen by others) seem to function is that You initially clone the desired archive to your machine (this creates a copy with all version meta data to-date). You create a working directory from the clone (this may actually be done as part of the initial cloning -- you end up with a directory of working files and a special versioning subdirectory with the archive) You make your edits/additions/deletions to the contents of the working directory You push/update the changes to the special versioning subdirectory Now comes the tricky part -- IF you have direct/update privileges to the master repository you can just "push" your changes to that repository, and have to then handle any merge conflicts. MORE LIKELY, you will not have update privileges -- you instead create a clone on the same server machine, push your changes to that clone, and then notifiy the maintainer of the master repository that you'd like them to "pull" the changes from your (on server) modified clone. They then pull the the changes and perform any merge conflict resolution. If you are using Windows, you might be interested in a graphical interface to Git, rather than using just command line tools... https://tortoisegit.org/ (The Tortoise folks also created interfaces for Mercurial [tortoisehg], older SVN, and maybe a few other version control systems)

Sounds like a cousin of (one of) my RQ2 characters (where SIZ was still 3D6, not 2D6+6). So... SIZ 6, STR 18 -- roughly a 4.5-5ft tall character swinging a 4ft (bastard) sword one-handed. I was influenced by my GM of the 80s -- we normally used "best N of N+1" die rolls, but no rerolls or swapping allowed. One still had the potential of getting minimum rolls (for a 3D6 stat, one could end up rolling 4x1s, so best 3 of 4 is still 3), but the average roll is tweaked upwards just a bit.

Think the comic is Freefall. The alien is using the name Sam Starfall.

The popcorn, or the worms? Save the worms for quiche Lorraine ver de terre* * yes, a recipe for such got printed in the Grand Rapids Press during my college days (76-80)

Heh... In too many representations -- slaves to the Romans... Spartacus was Thracian

Do these grow there? https://en.wikipedia.org/wiki/Amorphophallus_titanum

I haven't checked recently, but have vague memories that items used to show a set of flags indicating what countries items were available in. I've been caught by that message myself. One product was only available from UK and wouldn't ship to US.

The primary book comment about for reusable spells, that RPs "must be replenished".

Main book, page 314 Given that page 314 states for a non-fumble failure (hmm, no way to insert a quote block?) """ If the casting success roll is greater than the adventurer’s relevant Rune affinity, the spell is not cast, and there is no Rune point loss. If the adventurer is boosting the spell with additional magic points, they lose 1 magic point (no matter how many are being spent). On a fumble, the spell fails and the adventurer loses the Rune points intended for the spell. """ """ Once spent, Rune points must be replenished before they can be used again. """ It would seem rather punitive to have a permanent loss on a fumble when plain failure essentially has no effect at all. Permanent loss might make sense if a failure resulted in the (recoverable) loss of the RPs -- as if the spell had succeeded -- but with no spell effect taking place. Including the success categories, I see four levels of cost here: Critical Success: spell succeeds, NO RP COST (spell is free) Normal Success: spell succeeds, at REGULAR RP COST (recoverable via worship) Normal Failure: spell does not go off, NO RP COST (absolutely nothing happens) Fumble: spell does not go off, at REGULAR RP COST (ie; recoverable via worship) In contrast to the second quote above, the RBoM, page 9, on one-use spells explicitly states """ The Rune points used to cast spells designated as ‘one-use’ in the Rune spell or cult descriptions cannot be replenished. """ The four levels of cost for one-use spells (still page 9) come out to be Critical Success: spell succeeds, NO RP COST (spell is free) Normal Success: spell succeeds, at PERMANENT RP COST (not recoverable) Normal Failure: spell does not go off, NO RP COST (absolutely nothing happens) Fumble: spell does not go off, at PERMANENT RP COST (not recoverable) Note the symmetry between one-use and reusable spells: 0 RP, x RP, 0 RP, x RP. The difference is that one-use spells have permanent RP loss while reusable spells have recoverable RP loss.

Especially if the javelin is closer to the Roman Pilum in design (though I wouldn't think bronze would be suited to a light spear meant to stick into a shield and then /bend/ so the shaft dangles and interferes with moving the shield around).

That is a very strange definition of "self-loading weapons". No body that I know of considers common* revolvers to be "self-loading". They require either manual cocking of the hammer -- which also rotates the cylinder bringing the next chamber into alignment with the barrel (single-action mode), or cocking/rotation as an effect of pulling the trigger (double-action mode). Semi-auto weapons are those in which, from whatever is considered the "ready" stage (minimum requirement for those that fire from a closed bolt is that a round is in the chamber -- may be single-action [hammer cocked by action that also loaded initial round in chamber], striker-fired [trigger needed to operated spring-loaded firing pin], double-action [typically first shot-only, and usually after having decocked the hammer for safety]; the rare "fire from open bolt" requires the bolt to be, well, open -- pulling the trigger releases the bolt to close, whereupon it picks up/loads a round, slams shut firing the round, then recoils back to open). Fully auto weapons are those which repeat the cycle so long as the trigger is held down (semi-auto have a trigger disconnector, requiring one to release the trigger to reconnect to the rest of the firing mechanism). * Webley did make a semi-auto revolver in the early 1900s. The barrel and cylinder assembly slid back&forth, cocking the hammer, while pin(s) on the non-moving frame ride in grooves in the cylinder to rotate it to the next position.

I'd likely treat them as separate implementations. Consider the sidebar for "Heal Wound" on page 330. This is one of the "common" spells known to pretty much all cults, yet they are incompatible in how they take effect. Even if an associated cult originally "learns" the spell from the "parent" cult, it may have developed differences making it incompatible.

Note that the discussion was with regards to parchment/vellum which is not that easily produced, as demoed on PBS/NOVA it is also slow to write upon (taking dictation when using parchment is futile if it takes a day to fill one page). Papyrus, OTOH, was shown to be fairly rapid when writing, so dictation is feasible; the grain of the reeds making up the papyrus provide natural guidelines. Paper (as in cellulose pulp pressed in a drying frame) was never a consideration here. There is no entry for "paper" in the price lists from the rulebook -- only papyrus and parchment. Parchment was used in the example as the subject was a "book" -- covers, individual pages that can be flipped (created from signatures made by folding the animal skin a number of times and then trimming the edges). Papyrus, by the nature of production (weaving strips of soaked reed), is more suited to the format of a scroll as the length is determined by how many layers one can fit into a drying press.

My interpretation would be that you'd have to cast the spell such that the foot/sandals and corridor floor are both in contact at the moment the spell goes off. One does not cast it on the floor, and then hope someone walks on it and gets stuck. IOWs: it is more like a contact cement (applied to both surfaces, and then sticks when the two surfaces are brought in contact), and NOT like fly-paper or rodent glue traps (in which one object is permanently sticky, and anything making contact will adhere to it)