elglin: (Default)
First, a story.
A decade ago, I was running a campaign (still my best, I think). However, our friends from a neighboring village (both players, I knew their DM) came to stay for a few days. So, I asked the party if they were okay that there will be two more characters, I asked the friends if they were okay for a one-session wonder with a throwaway character, we had a session, and before the next session I asked one of the friends if she was okay with my killing of her character in the final dungeon to show the shit was getting real. Well, I got okayed on all the questions, and that's exactly how it all went.
As DMs go, I'm on the dictatorial and non-picky side. Other DMs I know go to much greater lengths when it comes to such issues in a sometimes most absurd, but also most gentlemanly way.
Second, over the years, I've elaborated a convention (which I've also seen in play with other DMs), that if we are having a session, and someone can't make it because life happens, then the character is temporarily under DM control. The character provides the resources as per the game system (skill checks etc.) as required, participates in combat with reasonable efficiency etc. etc., so the party isn't lamed from the functionality standpoint. On the other hand, the character does not make any decisions, does not have a say in whatever happens at the table - in other words, even more limited than an ally NPC who is still entitled to a quip or two or a parcel of information.
This convention isn't perfect, but it works reasonably well - for occasional and/or unforeseen absences. One important thing here is that the character, if occasionally controlled by DM, is still owned by the player.
Third, what if those absences become frequent and yet irregular? If they are regular, one can work something out, rearrange the campaign so that the party spends every third session indoors, where Grask the Ranger isn't much needed - which perfectly coincides with Mike, Grask's player, being absent every third session because life happens. But what if Mike has a one-in-three (perish the thought, two-in-three) chance to miss any given session, yet you get only a short notice and sometimes not even that?
Well, if the DM and the party want to play it out gentlemanly, they're screwed. Any and all Grask-related quests may just hang in the air because Grask didn't show up, and the DM and the party will have to scramble to work around that... or if there's none, then it's unfair to Mike (who will be bored) who showed up. And what if those weren't just throwaway quests, what if that was an entire questline, perhaps created specifically for Mike to put Grask into the limelight?
You could say that life happens. Cry me a river. Two months ago I bid farewell to a colleague who had, on a short notice, to quit the job and move away from the country "to take care of a relative for a year or so" - sapienti sat. That's how life happens.
Sure, life does happen. But most of the time it does that gradually and semi-predictably. In this case, the onus is on Mike to get together with the DM and let him know that he will be, "because reasons", we respect privacy, frequently and yet irregularly absent. They sit down together and work something out. And if they don't, I assert that the interest of the game, of the party and even of the DM (because it is a job) in this case prevails over Mike's interests - of course only in the case when an amicable agreement has not been reached.

Which means that if Mike had a foreseeable scheduling issue (e.g. impending divorce, house renovation, commitment as a reserve player in a local team etc.) yet did not elaborate that to the DM and carried on "just as normal", he's done a number on both the DM and the party. Don't be Mike.

P.S. If you know someone who you know and I know and who you think Mike is based on - you are probably right.
elglin: (Default)
Давно не писал в открытую по-русски, но тема иммиграционная, поэтому почему бы и не.
Итак, власти этой нашей Германии придумали сабж, который позволяет въехать в Германию и год легально в ней искать работу и, найдя таковую, получить обычный рабочий вид на жительство.
По ссылке https://chancenkarte.com/en/ детали, а я сейчас вкратце.
Обязательная программа
Официальный документ о хотя бы двухлетнем послешкольном образовании. То есть хватит диплома колледжа, в девичестве техникума.
Документ о знании английского на уровне B2 (IELTS, TOEFL, etc.) или немецкого на уровне A1 (telc, Goethe).
Справка о наличии финансовых средств, в качестве которой принимается действующий трудовой договор на хотя бы полставки.
Произвольная программа
Надо по развесистой балльной системе набрать хотя бы шесть баллов. Примерные сценарии:
Достаточно обученный крот
За признанный в Германии диплом (https://anabin.kmk.org/cms/public/startseite) дают 4 очка. Собственно, при наличии оффера на нужную сумму это почти готовая Голубая Карта. Чтобы не набрать оставшиеся два пункта либо возрастом до 35 лет (2 очка) либо пятью годами работы из последних семи календарных (3 очка), надо очень креативно жить.
Достаточно молодой крот
Если диплом не признан, то при двух пунктах за возраст и трех - за опыт работы (что реально в возрасте под 30), можно набрать лишний пункт, к примеру, дефицитной областью (кто сказал ИТ), и таким образом выполнить произвольную программу, даже не зная ни слова по-немецки.
Достаточно немецкоговорящий крот
Это потому, что за каждый лишний уровень немецкого сверх А1 по модели CEFR дают по баллу - и так до трех. Так что тому, кто учил немецкий в школе и не весь его забыл, даже возраст более сорока не препятствие.
elglin: (Default)
Die Grenze steht offen!
elglin: (Default)
Setting 101: a West Marches styled campaign in a "fantasy post-apocalyptic" world. The Event was a zombie plague, only not a proper zombie-skeleton-undead plague, but more like corruption-based Resident Evil or Last of Us plague. All the original population went dead, or corrupted, or undead, or worse. And is now roaming more or less aggressively around.
There is a base camp (with field hospital etc.). A boat-navigable canal runs due south past the camp, enters an enchanted forest approx. 50 miles from the camp, then runs for a further 50 miles through the forest up to and past the enchanted elven settlement.
Long story short, in the aftermath of a boat raid on the said town, the party wizard almost succumbs to said corruption plague (the reasons thereto are best left off the page). It's a splendid evening, the party is appropriately tired, battled and out of spells as befits a day of adventuring, and a knowledgeable person says that the party wizard has "two nights till he succumbs finally, unless the party finds a magical artifact in this accursed forest". He remains more or less fully operational, though. A hundred miles to the hospital, 25 miles/day of traveling even at fast pace, good night, sweet prince?
Well, quite possibly so, yet...
1. A day of travel (Day 1) at fast pace brings the party 25 miles along the road running alongside the canal.
2. Then, if the wizard burns all his spell slots on Expeditious retreat, he can get himself and the party druid 5 miles further within an hour. (Edit: it would be more beneficial to use that during Wild Shape, but this thought came to me as I was typing this, and I describe how it had been presented to the DM)
3. The party druid has 2x Wild Shape for 2 hours each. The giant eagle has a 60ft flying speed, and, as a Large creature, can carry our Medium wizard, who is a vanilla human. Then, the good old riding horse has a 60ft land speed and, as a Large animal, can be ridden by our Medium wizard. This brings us a further 20 miles, exactly to the edge of the forest, 50 miles both from the elven city and base camp.
4. The party has limited and fantasy-style, but comms to the base camp. And the boats carrying the raid, although considerably closer to the base camp (they left a day earlier), are, on that "splendid evening", approximately at the aforementioned edge of the forest and can stay there a day longer - pretty safely.
5. The druid, who is properly FUBAR from exhaustion, as well as the wizard, get loaded onto the boats, which then travel the entire rest of the night (Night 2) for approx. 20 miles - against the current. So, 70 miles from the elven city and 30 miles from the base camp.
6. Meanwhile, a mounted rescue party issues forth from the base camp at the same morning of Day 1 as the adventurers leave the elven city and camps approx. 30 miles from the base camp.
7. In the morning of Day 2, the wizard mounts (or is put on) a horsey and travels the same 30 miles to the base camp and arrives before nightfall - in time to get wheeled into the field hospital so that the base camp clerics can run him through the cleansing ritual, or, more accurately, the ritual through him. The fate of the druid, who is still mostly FU, but thankfully not beyond all recognition, is less important - he just gets a lifelong aversion to night flying and passive night horse-riding.

At this moment the DM said something on the lines of: "Holy cow, that might actually work" and "well I never, I thought you never had the chance to cover 100 miles, but i never thought of the boats".
Then, because he is a respectful and polite DM, he asked us: "What if I told you right now, not to nullify all that effort, that your wizard is FUBAR enough that the camp clerics actually won't be able to heal him, and all your hope, indeed, must rest on some kind of an artifact you must find in this accursed forest?"
Then, because we are players respectful of DM preparation and effort, we replied that we would be very thankful for the insight and focus our efforts, indeed, on that accursed artifact in that magical forest.
elglin: (Default)
Today, I've played (for the third time already) as a replacement on one of the last boards in the club's second team. Depending on how it turns out, the last boards can be anywhere near 1800 (lost), 1600 (drew), or, as today, unrated but suspected to be about 1000.
In the words of Levy Rozman, that you're rated 1200 doesn't mean that you cannot play an extended sequence of moves at the 1800 level. It's just that at some point your brain short-circuits and you play a couple of moves at the 600 level. In fact, the game I lost - I lost it from +2 engine evaluation, while the game I drew (due to perpetual check) - I drew it from +1.5 and up the exchange.
Long story short, by move 26 I was up a pawn and +3, mostly due to the opponent very graciously playing right into my prep. But as my opponent wasn't a complete newbie, he knew the idea that allows people to save countless games: when behind, be aggressive and counterattack.
Well, I've overestimated his counterattack and opted, instead of maintaining the tension and the pressure on the position (which was the right thing to do according to the engine), to go for simplifications, because I thought that I'd gladly play a queen and bishop vs. queen and knight endgame being up a pawn. I also thought that I was escaping the perpetual check - eventually.
Wrong. Right after the exchanges, the engine immediately showed a dead even evaluation because, in fact, in the very same line I thought I've calculated, I did not escape the perpetual. Thus, between moves 29 and 32 my opponent had this or that opportunity of a perpetual. Whether he didn't see those, whether he (much as I) wrongly assumed that I was eventually escaping, or whether he thought his counterattack gave him good chances gobbling up my pawns - I'll never know. Within those moves, we also exchanged the light pieces, so it was a clean queen endgame.
I'm crap at endgames, especially queen endgames. They are also generally hard because queens have so much mobility, so situations where you may spend a dozen moves jockeying for a slightly better position are quite real - the engine analysis I've run at home suggested maneuvers I can't even begin to understand.
But as the saying goes, you don't need to run faster than the lion - you need to run faster than John. And as the subject saying goes, when you're playing someone at your level, but half your age, you tend to be a little less crap at the endgame.
So my opponent took the wrong pawn, and then made a suboptimal queen move... and the difference was that he didn't have any checks, while I did. Perhaps there was also the time factor - I had mere minutes on the clock, and he had almost a half-hour on me, so he may have been tempted to play quickly to get me into Zeitnot.
However, it was already move 35, and the move sequence, consisting mostly of checks with fork and pawn captures was easy to calculate. By move 41, I had only some 90 seconds... but it was the classical time control, which gives you the very generous 30 minutes if you survive the first 40 moves. And as it happened, move 41 was a pawn capture which not only left me up two pawns, but put my queen on the very same diagonal as one of my surviving pawns - which was a passer as well.
To be frank, although it was an absolutely won position, I couldn't have won it in 90 seconds, quite probably not in 900 as well. However, when you have 30 minutes, you can afford to spend a few of them to work out your endgame plan - and since it was an absolutely won position, it took me just seven minutes.
It may have been the question of endurance, as my opponent had to defend the entire game - an experience I can easily relate to, and a very unpleasant one. But much as the engine evaluation jumped from dead drawn at move 33 to +4 at move 41, it jumped to "mate in 23" by move 49, at which point my opponent resigned. Of course I wouldn't claim to see a mate from that far, but at that point the choices Black had were either to let the pawn promote, or to sacrifice a queen for that pawn (both outcomes leaving White up a queen with no stalemate shenanigans), or, which was the top engine line, to trade queens and a pair of pawns - which would leave White three pawns against one, i.e., a completely won pawn endgame even with imperfect play.
The result, however, had no impact whatsoever on the overall outcome, as the team won 5:2 on the remaining boards.
elglin: (Default)
Wenn man in einer Großstadt lebt, und auf die Bücher in den "zu verschenken"-Kisten achtet, kann man binnen wenigen Jahren eine ziemlich gute Bibliothek sammeln.
Wenn man dazu zur gebrauchte Buchhandlungen geht, wird diese Bibliothek zur sehr gute.
elglin: (Default)
https://tvtropes.org/pmwiki/pmwiki.php/Main/MaybeMagicMaybeMundane for an introduction to the concept.
Right now, many people (probably most) think that magic doesn't exist in our world. So there must be a perfectly mundane explanation for anything seemingly magical - it's quite probable though that you (or I, or even anyone) don't know it yet.
For a DnD player, the magic is very real. You've got your spellbooks etc. and you see occasionally the good old trusty Fireball spell. You know, a good old ball of fire appears on the mage's hand and flies to the impact point, everyone in 30 ft. radius rolls a Reflex save to get half instead of full Xd6 damage.
For a medieval person, or at least for a medieval person as we think he/she was (it's not like we can ask around), the question of magic was... less certain. A lot of things were quite mundanely explainable, some weren't.
Say, was the legendary Excalibur a magic sword, or was it by change an exceptionally well-made sword in an age when most swords were somewhat underwhelming? Was Achilles's armor magically impenetrable, or was it just a well-worked high-tin-content piece?
An interesting applied question is how can a GM, with judicious usage of concealed rolling, maintain uncertainty? Does this NPC weapon wield a weapon with magically enhanced damage, or is he just naturally rolling high damage? Is this pendant really cursed, or is the wearer plain unlucky with saving throw rolls? Does this armor piece have a magical enhancement, or do the enemies just roll too low to get past its regular DR?

It appears that there is quite a possibility for an enterprising GM to do just that - with some concealed rolling, of course, and a careful selection of spells involved. That is, the spell effect is involved from a purely mechanical Doylian perspective; however, from the Watsonian point of view, the observed effect cannot be distinguished from a stroke of luck.
elglin: (Default)
GURPS isn't dead in the sense that there are plenty of gamemasters using it to run lots of campaigns. Problem is, the majority of those gamemasters are on the wrong side of 40, and once they kick the bucket or otherwise retire from gamemastering, GURPS will be well and truly dead.
Just for comparison, d20 systems like Pathfinder or DnD5e are alive and well. How did it come to this?

Don't get me wrong, GURPS is a terrific system. It has mountainloads of info, to the point that some GURPS manuals still are better than respective wiki articles. It has potential for gameplay and story integration not seen in DnD since ADnD2. It is astoundingly well-researched. And GURPS combat lends itself to realistic description of what's happening the way DnD never dreamed of.
Okay, Harnmaster (how many have even heard of it?) is another painstakingly researched system which reads almost as a historical and economical treatise on manorial England - and has a terrific default setting. Also consigned to the depths of the oblivion. There are doubtless many others. But GURPS was, at its peak, one of the top systems.

First, GURPS is hard. Seriously hard. It's harder than ADnD 2 was, not to mention Pathfinder/3e or later editions. As a GM, I still make mistakes (covered by the Zeroth Rule, of course, and "When in doubt, roll and shout").
Second, it's long. Including the basic set, I've read over a thousand pages in preparation for the current campaign. Even if you are a GURPS aficionado, you still need to read up or refresh a couple hundred pages (mostly of splatbooks) when switching to a substantially different setting, e.g. from Rome to pirates to steampunk to post-apocalypse. "Too long, didn't read" is in full effect.
Third, it's campaign-oriented. The previous two points hint at an obscene (by today's standards, not so by 80-s or 90-s though) amount of preparation. Makes sense for an overarching multi-session campaign with a complex plot, makes no sense for a one-shot adventure (for which, incidentally, ready-made Pathfinder modules using pregen characters are so good).
Fourth, it's too slow and too realistic. Space Odyssey, not Star Wars. It lends itself to a slower-paced, more thoughtful tempo rather than to hack-and-slash action DnD (or Savage Worlds) is so good for. A Sherlock Homes novel, not a buddy cop movie. While there certainly is a niche (and a pretty cosy niche) for such plot and pacing, it's decidedly not mainstream nowadays.

Bottom line, tabletop RPG systems have evolved, hand-in-hand with popular demand, to rules-light and a more cinematic/superhero feel. The tabletop society has moved in the same direction, and GURPS (along with many other, lesser known systems) is now a relic of the past, a living fossil.
And, eventually, destined to die out with its gamemaster populace.
elglin: (Default)
As far as I remember an article I once read, Tolkien originally set out to write a Norse-like mythology which he felt the English culture lacked. It all turned out completely different, of course.
A certain Mr. Sapkowski expanded his short story collection to a fantasy saga, in a large part, due to a lack of a fantasy saga in contemporary Polish literature. Long before the forgettable Netflix series and even long before the acclaimed video game series, this saga was well-known and well-liked in Eastern Europe.

What if Geoffrey of Monmouth, being sick and tired of the Matter of France, found a distinct lack of the Matter of Britain and decided it was his task to fill that void? If not with blackjack and hookers, then with knights and ladies?
If it were so, he was no less, if not more, successful, than the aforementioned acclaimed authors whom he predates by almost a millennium. And we cannot really blame him for the fact that generations of historians used his writings as the authoritative source - that would be akin to blaming Bernard Cornwell for taking liberties with the Peninsular campaigns which, historically, never saw a certain Sharpe make quite a career.

Agile Werte

Jun. 7th, 2023 09:56 am
elglin: (Default)
In der heutigen Welt der Information gilt der alte Zyklus: "Verstehen - Entscheiden - Machen" nicht.
Das ist vielleicht alles, das man über solche "agile" Werte wissen muss.

Urlaub

Apr. 15th, 2023 08:25 pm
elglin: (Default)
Istanbul ist natürlich eine Stadt zu besichtigen. Meiner Meinung nach aber, keine gute Stadt, um zu wohnen oder zu arbeiten. Berlin ist nicht die beste Stadt der Welt, aber ich war sehr froh, zurückzukehren.
Ansonsten habe ich meinen Vater sowie meine Schwiegermutter und meinen Schwager getroffen.
Meine Aufenthaltstitel hat auch ihre erste und wichtigste Prüfung an der Grenze bestanden.
Jetzt zurück zum Leben und Arbeiten.
elglin: (Default)
Ich habe nichts besonders interessantes, übers Jahr 2022 zu schreiben, fast nichts gutes auch. Doch gab es unbedingt etwas gutes darin, und dafür bin ich dankbar.
Einen guten Rutsch ins Jahr 2023!
elglin: (Default)
I gave some thought to the concept (a trivial introduction is here), and came to the idea that it might be after all a religious debate if not on par with vi vs. EMACS, then at least in the same area code.
Bottom line, IT happens. Unless you're on par with Donald Knuth or something, you will, sooner or later, run into a case when a bug of whatever kind has somehow escaped code review, automated and manual testing, lower environments runs and has finally crept into production. I will look at two edges of the psychological spectrum here; in a futile attempt to escape labeling I would name them "debug" and "last known good".
A "debug" person sees this as a technical challenge. After all, this bug has somehow avoided all the traps set for it, so it's quite a worthwhile opponent. If the person had a major part in setting those traps, the challenge becomes almost personal. Also, if the codebase is of pretty high quality, such things are few and far between, and are a welcome distraction from the tedium of, you know, release process. In this case as well, the bug is quite likely to be something probably not trivial to find, but relatively easy to fix or at least work around - so for a pretty minor investment of extra effort you don't let the effort of writing the 99+% of good code lie on the shelf for an extra release cycle because of that 1% of bad code. This is a pretty concise mindset which is internally consistent. Once again, in a futile attempt to avoid labeling, I will refrain from any judgement.
A "last known good" person sees the same situation in a different way. The proof is in the pudding, after all. Why are we so sure that the Eiffel tower could be built? Because, quite obviously, it was. So we have that previous version of code, which we know can work - because it has, probably for quite a while. We also have this new version, which we know has a chance of not working - because, currently, it doesn't. If this person does not have a personal affinity to the newly deployed version, and indeed is for whatever reason concerned with the stability of the code, no matter what version it is - well, we revert, and better luck next time. Ironically, if the codebase is pretty good so this doesn't happen often, this point is valid - hey, people will be paying extra attention next time, so what are the chances of a pretty good codebase to fail twice in a row? That effort developing the new version - well, it's not thrown away, just shelved for a while - and meanwhile, both the system is stable and whoever is responsible to fix the problem has all the time in the world to do it - also without management and business peeking over his shoulder and asking distracting questions. This is also a pretty internally consistent mindset.

A very good quote (I certainly fail to reproduce it verbatim) says: "Fight, flee, or play dead - all these are evolutionarily confirmed strategies, and any can be optimal in a given situation". Here we have the same - depending on the details, where the devil is, leaning towards either may be more effective.
However, my personal experience (and I'm really not a great judge of character) is that a person, while certainly not immovable on this scale, tends to shift pretty slowly to either side. Which means that, in a fixed place and time, people working on a same issue, but having pretty distant views on this scale, may find it surprisingly hard to understand each other. It ultimately comes to "values", or, better said, cognitive presuppositions. It is a pretty rude awakening to understand that another does not think something very important to you is worth much, and, of course, vice versa. But that problem, I guess, runs much wider than IT.
elglin: (Default)
...is, of course, naming the variables.

Case in point, King Charles III, but in Russian. In English, of course, Charles, Prince of Wales, became Charles III, King of, well, United Kingdom and lots of other places which I don't have to remember as I'm not his subject.
In Russian, however, Prince Charles became King "Karl". A bunch of dimwits ran with that as "he changed his name, he was Charles and now he's Karl". A bunch of other dimwits ran with the story "Oh those idiot Russians who rename people when they become kings and queens" - I leave it up to the reader to decide, which of those bunches is more asinine.

In fact, it's purely a naming convention. Of course while the French had quite a few kings Louis and several kings Henry, they most certainly don't name them "Ludovicques" or, perish the thought, "Guinriche". William the Conqueror, too, was likely never called "Wilgelm".
Still, not really sure when that convention arose in Russian historical literature, but it became an established convention that kings and queens were named "based" on the Latin spelling of their names, even in cases when it sounded nowhere near the real enunciation. That extended beyond the strictly royal line to people like Charles Valois, brother of Philippe IV. So, while Charles Windsor was still the Prince of Wales, he wasn't the subject of that convention, but now, as a king, he pretty much is. End of story.
Of course, one could say that this convention is pretty dumb, and it quite probably is. However, as many practical programmers (the kind who write code instead of waging flame wars) know, following a bad naming convention already established in a codebase is preferable to having two naming conventions within it. An even better option, of course, would be to refactor the code to a good convention; however, it's quite often impractical even in the case of a codebase.
Therefore, until some kind of naming authority (Now where's the Russian Academy of Sciences when it's needed) decides to alter the convention, "es bleibt immer so wie es ist". Of course, this doesn't preclude me from continuing to call him Charles in private. Certainly not a case of lese majeste.

On a side note, there was quite some speculation in the mid-2010s on which royal name Charles would eventually take, and people were more of the thought that he'd become George VII, as both previous Kings Charles left a pretty questionable legacy. So he actually did have an option of renaming himself - he just chose not to.
Page generated May. 20th, 2025 12:24 pm
Powered by Dreamwidth Studios