Disclaimer: I Am Not A Linguist, and the following should not be construed as linguistic advice applicable to your particular campaign.
But I did take linguistics 101 once and now I know just enough to be dangerous.
Recently on the way back from lunch on a workday, I somehow ended up with both "Krishna" and "Grishnakh" in working memory at once, and went "Tolkein, you clever bugger, taking proper names from other languages and performing slight shifts on them to distinctly change their tone!" In this case the shift from 'k' to 'g' is voicing a velar plosive that was previously unvoiced (and then appending a k, but that's more of a phonotactical move). The k->g voicing is similar to the devoicing of 'd' in the High German consonant shift (ex: door vs tür in German).
The question, of course, is "How can I apply this to the Scaled Continent?"
Let's start with snakes. They hiss. A snake-language should have lots of unvoiced fricatives. If we take a base of say, Aztec names and convert z -> s (which is actually proper pronunciation in Nahuatl, but reversed elsewhere for flavor), ch -> sh (and x -> sh for ease of reading and in keeping with the Nahuatl pronunciation), we get something slightly different. If we figure crocodiles might favor nasal (crocodiles have long heads, probably sizable nasal cavities) and gutteral sounds, and we convert say co/a to go/a (voicing) and say l to n (alveolar nasalization?) and apply it to the same set of names, we start to get different accents. Chichimecatecle (good lord that's a long name) becomes Shishimecatecle in snake, but Chichimegatecne in crocodile. Lizardman probably falls somewhere in between, with some fricative devoicing and some nasalization (or just use base Aztec names for them). Beetlemen have a buzzing language, converting sh -> j, s -> z, and f -> v. I have no idea what sea turtles sound like; I guess clicks, nasals, and vowels probably carry best underwater, though, if dolphins and whales are any indication. Tricky. Frogmen might have l -> r and p -> b (I foresee Zorton the Frogman being a party favorite; it's fun to say).
And I haven't even touched vowels yet, but that's because standard english transcription does a horrible job with those and getting vowel pronunciations right is hard.
So if we apply the accent filters and then feed the results into the Markovinator... I should have sufficient names of reasonable variety but shared roots and flavor.
For now.
(Though players, being players, will of course mangle Shishimecatecle into "Sheesh" and Chichimegatecne into "Megatech". *sigh* At least I know what I'm in for)
(Also, apologies to any actual linguists reading this. I know converting sounds using regular expressions on text is a travesty, but computer voice processing is complicated and sort of a hard problem to be tackling as a hobby project due next week at first game)
Sunday, October 27, 2013
Saturday, October 26, 2013
A Broker of Consequences
Parenting advice from one of my coworkers:
Anyway, I thought "broker of consequences" was a wonderful turn of phrase for describing the role of a sandbox DM.
"I tell my children that I don't deal in reward or punishment; I only deal in consequences. Reward and punishment are matters of opinion; the edict 'If you eat everything on your plate, I will give you a bowl of peas and you will have to eat them all' is a reward if you like peas, and 'If you eat everything on your plate, I will give you a bowl of ice cream and you will have to eat it all' is a punishment if you're too full to eat any more. Consequences, on the other hand, are a matter of fact, and I make it clear to them that I am a broker of consequences. If you do X, I will do Y; whether or not you choose to interpret Y as punishment is up to you."I'm not sure if it's particularly good parenting advice; upon further examination, I'm left a little unsure of the intent in that arena. It certainly seems reasonable DMing advice, though, where the source of punitive intent (say, a king who has been offended) is (or should be) divorced from the agent responsible for enforcing consequence (the DM). The DM does not punish; the DM administers the logical consequences an action within the world. And hey, if you needed to end up in the royal dungeons to ask a political prisoner some questions about where you can meet his conspirators to bring his plot to fruition and you have a good escape plan, it might not be a punishment. But save versus death to avoid contracting some unpleasant malady from the filthy dungeon bedding... (consequences!)
Anyway, I thought "broker of consequences" was a wonderful turn of phrase for describing the role of a sandbox DM.
Friday, October 25, 2013
Free the OGREs!
I am sad that I missed the OGRE 6e kickstarter, but SJG has been so kind as to release the rulebook and everything else except for the counters and maps to the internets. Mighty nice of them to finally give me a chance to read the rules, which I found interesting. Coming from the Domains at War and Stargrunt tradition, the thing that struck me as I was reading was "Where are the morale rules?" Which, naturally, would be a poor fit for the sort of 'humanity's last stand against their own best weapon' engagements that the game models. Other than that, though, the rules seem pretty reasonable; ranges in particular are plausible given the 1.5km hexes (one of the things that grinds my gears about BattleTech). I also like how tread damage is handled as gradual attrition and a cost for ramming. Could use some air support rules too. The rulebook gives enough detail of the OGRE map for me to probably set it up on my hex mat, so that might be a fun solo game this weekend... I'll probably also pick up the pocket edition when it comes out, because for that price, why the heck not.
It might be fun to write a program to run the OGRE while I play humans...
It might be fun to write a program to run the OGRE while I play humans...
Tuesday, October 22, 2013
Settlements of the Scaled Continent
In ACKS' default 'borderlands' setup, it is assumed that there is a region of human civilization on one map edge, with forbidding wilderness on the other side and a sparse line of frontier towns down the middle. The Scaled Continent has a very conveniently navigable dividing line, namely coastline. And so, a list, named in my typical town-naming style:
- Notable non-border settlements:
- Salvation - The largest settlement on the Islands of Voltager, so named due to its position as a source of fresh water in the middle of an otherwise massively empty ocean. Once occupied by the lizardmen, fell to a short Auran siege due to Voltari complicity and poor fortress design.
- The Forks - Once-capital of the Thrassian Empire, located at the massive fork in the Serpent's Tongue from which that river derives its name. A multiracial city, hosting large resident populations of lizardmen and vipermen along with representatives and slaves of a hundred jungle races, along with man, dwarf, and elf. The Citadel, a massive castle once home to the dragon-king Itzcoatl, rises eighty feet from an island at the center of the city.
- The Pit - An immense sinkhole deep in the jungle whose walls the vipermen have riddled with burrows. Known for its market, where it is said to be possible to buy any poison known to man, and many more exotic.
- First, towns that are where they are for a good reason:
- Stillwater (town) - A trading port at the mouth of the River Langour. Primary port for man-crocodileman interactions, and a designated Human Preserve / slave-trading area. Named for the speed of the aptly-named river on which is sits.
- Haven (village) - a good natural harbor located midway between the mouths of the Langour and the Serpent's Tongue. Old lizardman ruins on the promontory overshadow the town.
- Unity (village/hamlet) - Settled by a passing ship's crew due to generosity of friendly natives. Good relations persist to this day.
- Port Maw (town) - Positioned at the mouth of the Serpent's Tongue river, a major trading port with the lizardmen and vipermen of the upcountry. Once a major slave port, less so now. Named for the impression of early sailors that the overhanging canopy resembled a toothed mouth.
- Mission (hamlet) - An Auran religious / military outpost some ways south of Port Maw.
- Guano Cave (town) - Midway between the Serpent's Tongue and the Islands Innumerable. Primary natural resource and export is guano from the extensive nearby cave complexes, contested by cave inhabitants.
- Liberty (village) - Carved into the cliffs of the Turtle's Beak by escaped dwarven slaves. Remains a dangerous place for slavers to put ashore.
- Scurvy's End (village) - Among the northwestern Islands Innumerable, and home to extensive fruit trees and abundant fresh water. A favorite stop of sailors.
- And of course, those settlements with less fortunate origins (mostly villages / hamlets)...
- Mire - A hellhole in the Crocodile Fens founded by poor benighted (and beknighted) fools in search of a city of gold. Enjoys regular visits from hungry crocodileman raiders.
- Miasma - A barrier island off the coast of the Fens settled by sailors who ran ashore during a storm. The whole place stinks of rot from the salt marshes, and malaria is its primary product. The soil is good for growing rice in the marshes, but mortality is atrocious.
- Rat's Nest - North of Port Maw, a ship washed ashore during a tremendous storm was caught in the canopy of the jungle. Most of the original sailors have left, but the elves enjoy the humor of the place and congregate here.
- Splinter - A treacherous reef in the Islands Innumerable, inhabited by sharkmen. Their religion prohibits them from eating anyone who makes it to shore, and a small colony of survivors has sprung up on the nearby atoll as a result. They trade crude alcohol, crafts, and stories to the sharkmen for fish, but are always careful to stay out of the water...
- Mutiny - Beyond the Islands Innumerable lies the Bay of Black Sand, abutting the Desert of Black Sands. A fool captain once attempted to chart the coast of that miserable place. When he came upon a river running north into the desert, and a merciful source of fresh water, he let it be known to his crew that he intended to continue east along the coast after only a day to gather provisions. His mistake in henchman morale management cost him his life, and a town sprang up at the river's mouth. These days it caters to fools seeking to explore the desert's interior, and is inhabited by the desperate, the wanted, and the slightly-unhinged.
Labels:
ACKS,
Scaled Continent,
Worldbuilding
Friday, October 18, 2013
Scaled Tongues
Setting work on Scaled Continent continues. Start date of campaign at FLGS is set for 3 November, so I have just over two more weeks. Running a game for a group of complete strangers will be... interesting (provided I can get any to sign up). If not, well, I've heard good things about Roll20...
Been working on mapping, custom treasure, and custom spells. Not Joe Orcs these beastmen - Player's Companion and custom spells for their witch doctors and shamans. Got to thinking about language and the importance thereof in dealing with natives recently. I like the assumption that the various beast species have their own languages (crocodileman, viperman, toadman,...), along with a general 'Thrassian' pidgin from the Imperial days and a religious / court / high language, probably Draconic. Common is the language of slaves and former slave races, who also have their own racial languages (Elven, Dwarven, Auran).
The plethora of languages suggests some fun complications to me which are typically glossed over. First off, how many languages do beastmen speak? Off-the-cuff heuristic says that the higher up the chain of command they are, the smarter and better travelled they are. Normal beastmen speak only their tribal language, while champions speak two languages (tribal + pidgin or rival tribal), subchiefs three (tribal + two pidgins or rival tribals), and chieftains, shamans, and witch-doctors four or five (tribal + two pidgins or rival tribals + Draconic, typically).
Entertainingly, this means that the guys you're most likely to capture to interrogate for intelligence (the grunts) are the least likely to be able to communicate with you. Hi-larious! Also, the Comprehend / Read Languages / Tongues / Telepathy / ESP spells are much more useful when language barriers crop up reliably than in a game where you occasionally meet a dead script in some guy's tomb but all the beastmen speak Common. As are the Thief ability to read languages and the late-binding +Int language slots. ACKS provides plenty of ways to work around this problem, but it could still get in the way occasionally and entertainingly.
The other side of the coin is that the language you're speaking may effect your reaction rolls. Choose wisely; an armed band of demihumans addressing a lizardman in Common comes off as a slave revolt, while the same armed band of demihumans speaking Thrassian is more likely to be perceived as Voltari mercenaries. Speaking the tribal tongue of those you are addressing is liable to get a bonus, while speaking the tribal tongue of an enemy group may net a penalty. Common sense applies, but a plus or minus one bonus to reaction rolls from language might be utilized to good effect by canny PCs.
Been working on mapping, custom treasure, and custom spells. Not Joe Orcs these beastmen - Player's Companion and custom spells for their witch doctors and shamans. Got to thinking about language and the importance thereof in dealing with natives recently. I like the assumption that the various beast species have their own languages (crocodileman, viperman, toadman,...), along with a general 'Thrassian' pidgin from the Imperial days and a religious / court / high language, probably Draconic. Common is the language of slaves and former slave races, who also have their own racial languages (Elven, Dwarven, Auran).
The plethora of languages suggests some fun complications to me which are typically glossed over. First off, how many languages do beastmen speak? Off-the-cuff heuristic says that the higher up the chain of command they are, the smarter and better travelled they are. Normal beastmen speak only their tribal language, while champions speak two languages (tribal + pidgin or rival tribal), subchiefs three (tribal + two pidgins or rival tribals), and chieftains, shamans, and witch-doctors four or five (tribal + two pidgins or rival tribals + Draconic, typically).
Entertainingly, this means that the guys you're most likely to capture to interrogate for intelligence (the grunts) are the least likely to be able to communicate with you. Hi-larious! Also, the Comprehend / Read Languages / Tongues / Telepathy / ESP spells are much more useful when language barriers crop up reliably than in a game where you occasionally meet a dead script in some guy's tomb but all the beastmen speak Common. As are the Thief ability to read languages and the late-binding +Int language slots. ACKS provides plenty of ways to work around this problem, but it could still get in the way occasionally and entertainingly.
The other side of the coin is that the language you're speaking may effect your reaction rolls. Choose wisely; an armed band of demihumans addressing a lizardman in Common comes off as a slave revolt, while the same armed band of demihumans speaking Thrassian is more likely to be perceived as Voltari mercenaries. Speaking the tribal tongue of those you are addressing is liable to get a bonus, while speaking the tribal tongue of an enemy group may net a penalty. Common sense applies, but a plus or minus one bonus to reaction rolls from language might be utilized to good effect by canny PCs.
Wednesday, October 16, 2013
Hijinks Again Follow-Up
After consultation about this prosposal with my former spymasters and the internet at large, comments were as follows:
Speaking of scripts, been thinking about the Mother of All Scripts again. Some stuff from work has me thinking about ncurses and XML (both sort of groty technologies, but serviceable). In particular, XML seems like it might be somewhat useful for encoding deep structures in text; all the contents of a 24-mile hex, subdivided by 6- and 1.5-mile hex, including NPC and monster stats down to treasure, spells known, and Markov-generated names is not an easy thing to put into a text file in an organized and reloadable fashion (see: the Art of Unix Programming). XML could do it, but it would be verbose about it. I guess that's the tradeoff. The other option is to handle depth via directory structures in the filesystem, and then put hundreds of small text files all over the places throughout that directory tree. They're sort of equivalent; seek a way to handle a gross use case, end up with gross alternatives. As for ncurses, the problem there is one of displaying deep data in a useful way, as well as handling hex-mapping (and zooming in multiple layers of hexes) in a way that doesn't involve actual graphics...
So yeah... cue the A(CKS|X)ML jokes...
- Additional complexity is annoying
- Reduction of thief income might have unclear ramifications for the domain ecology
- On the other hand, our thieves were generating operating revenues far in excess of that intended by the system's designers. Scaling a cash-generating Fraud hijink to intended levels might solve this problem, with extra cash from stealing and selling cargos of treasure mapping being a bonus for work done
- Agreement that reduction of timescales down to weeks is a nice idea, but punishment remains problematic
- Realization of incompatibility between the mid-level wilderness exploration style of play and thief hijinks being town-centric
- The immediate nominal counter is that magic research is also town-centric, but the counter to that is that wizards can be gathering monster parts and unknown spells while wilderness adventuring, whereas the thief can't really use wilderness adventuring as leverage for hijinks
- Treasure hunting and stealing are both enablers for the wilderness game, but there is nothing in the wilderness that compels a gold-desiring mid-level thief out into it except want of magic items.
- Upon further reflection, Witness' comment on previous post solves this to some degree. The thing in the wilderness for thieves is not being in town while law enforcement are investigating the case. Hate to use the term, but an 'aggro'-like mechanic might serve. Multiple hijinks in rapid succession boost probability of being caught, lying low reduces probability of being caught, and being out of town reduces it even further (but sometimes they figure it out anyway, the wanted posters go up, and the bounty hunters come out...).
Speaking of scripts, been thinking about the Mother of All Scripts again. Some stuff from work has me thinking about ncurses and XML (both sort of groty technologies, but serviceable). In particular, XML seems like it might be somewhat useful for encoding deep structures in text; all the contents of a 24-mile hex, subdivided by 6- and 1.5-mile hex, including NPC and monster stats down to treasure, spells known, and Markov-generated names is not an easy thing to put into a text file in an organized and reloadable fashion (see: the Art of Unix Programming). XML could do it, but it would be verbose about it. I guess that's the tradeoff. The other option is to handle depth via directory structures in the filesystem, and then put hundreds of small text files all over the places throughout that directory tree. They're sort of equivalent; seek a way to handle a gross use case, end up with gross alternatives. As for ncurses, the problem there is one of displaying deep data in a useful way, as well as handling hex-mapping (and zooming in multiple layers of hexes) in a way that doesn't involve actual graphics...
So yeah... cue the A(CKS|X)ML jokes...
Tuesday, October 15, 2013
Kushan Battlefleet
While working on my test ships for Colonial Battlefleet the other day, I found myself upon the Homeworld wiki. There I espied the claim that Homeworld had been intended as a videogame adaptation of Battlestar Galactica. That Colonial Battlefleet was Galactica-inspired got the gears turning, and correlations starting to be made. I'm not familiar with BSG, but the no-shields rules in Man vs Machine ought to serve might fine for modelling Homeworld...
So some conversion notes and thoughts (not going to spring into building ships, as CBF's shipbuilder spreadsheet makes my Open Source Excel Clone Of Choice segfault, which makes me bloody nervous... besides, I want to do things it probably wouldn't let me)
So some conversion notes and thoughts (not going to spring into building ships, as CBF's shipbuilder spreadsheet makes my Open Source Excel Clone Of Choice segfault, which makes me bloody nervous... besides, I want to do things it probably wouldn't let me)
- Motherships. Proposed new role: Fleet Carrier, providing some combination of Carrier, Flagship, and Fleet Support functions.
- Tech lets us do most of the equipment manipulation. Since it was a mighty symmetrical game, tech levels are pretty much universal.
- Antimatter somewhere around 2, for the torpedos (as used on Assault Frigates). Homeworld capital ships are not particularly maneuverable.
- Conventional Weaponry at least 3. We know the Taiidan possess strategic bombardment weapons, as employed against Kharak. Optional rule that Max P.Def is equal to Conventional Weapons is in effect.
- Fighters 4-5 all round. The upper levels of the fighter tech tree will probably need replaced.
- Lasers 1 for screen role, but no shields.
- Orbital Construction... peculiar. Haven't decided how I'm handling tonnage yet. Nominally 4, since there are some damn big ships.
- Quantum Manipulation 2 for Taiidan, 3-4 for Kushan / Hiigaran. Ion Beams are modelled as disruptors, and are available to both sides. Stealth ships are the Kushan 'special' counter to the Taiidan defense frigate.
- Tonnage is complicated by the fact that Homeworld's ship naming conventions are mixed. Two ways to play this one:
- Corvettes translate to destroyers, frigates translate to cruisers, destroyers to heavy cruiers, carriers, shipyards and battle/heavy cruisers translate to battlecruisers, and motherships and dreadnaughts translate to battleships, or
- Problem - unfaithful conversion of corvettes as fuel-constrained small craft, further mangling of the fleet construction system to accomodate large number of corvette / destroyers
- Corvettes are gunships per MvM, frigates are destroyers, destroyers to light cruisers, heavy cruisers to heavy cruisers, battlecruisers and carriers to BC, and motherships and dreadnoughts to battleship.
- Problem - modelling multi-gun, salvage, repair, and minelayer corvettes as gunships
- I lack a good way to model the Taiidan defense frigate's ability to shoot bullets out of space. Screen is great and all, but that's not what it does. Providing something like L1 shields to a nearby ship would actually sort of work, with the caveat that shields are ignored by missiles, fighters, and disruptors. Taiidan defense fighters should probably work the same way.
- Gravwell and stealth generators likewise problematic. Stealth generator is just not going to happen under CBF's stealth rules. Gravwell might be workable as something like a spatial disruption torp.
- Missile destroyers fire cluster missiles since they're good against fighters
- The sensor arrays and probes are probably doable as a cross between Screen and Scout, with the +1 to hit nearby ships and the no-cloak within a certain distance, but without cloaking and +point defense. Call it a Sensor role.
- Lots of unarmed support ships in Homeworld. Not sure how well that's gonna work out... Might need to change things up a little and have say Assault Frigate hulls with different roles representing point defense, sensor, or other gear. The other option is to make stuff special equipment that uses lots of space, and then assign role Fleet Support to unarmed ships. That seems a bit silly, though.
- FTL travel is somewhat contentious within the Homeworld universe; HW1 permitted capital ships to perform tactical hyperdrive sort of maneuvers. Might be something to steal from MvM's Raider rules.
Labels:
Colonial Battlefleet,
Videogames,
Wargaming
Subscribe to:
Posts (Atom)