Home
Creators
Search Recent Random
Posts
Search DMs Popular Hash Lookup Tags Random
Importer
Import FAQ
Register Favorites Keys Review DMs Logout
Community
Telegram ThePornDude
Home Creators Posts Import Register Favorites Logout

The Eclectics | Kingmaker | Episode 44 (Patreon)

Published:
2025-12-16 19:18:55
Edited:
2026-01-27 14:37:07
Imported:
2025-12
Tags:

Content

Where can I find the rest of the episodes or Narrative Declaration's other shows?

You can find all of our shows and more via the collections page.

Where can I find the podcast version?

To keep the show Patreon Exclusive, the audio is uploaded directly on Patreon. You can find the podcast posts by going through the collections page here. If you want to learn how to add the RSS feed to your preferred app, check here.

How is this show distributed?

Please read our post about Kingmaker here.

Why are there Ads in this video?

Woops! There aren't suppose to be! We never intend to place ads in Patreon exclusive content, so if you're seeing ads please let us know and we'll try to fix it!

If there are ever any issues with the VOD or anything else, please let us know in the comments or by contacting ZoranTheBear on the community Discord!

Files

Kingmaker | Episode 44

You can support our actualplay show and more via the links below! ► Patreon: https://www.patreon.com/NarrativeDeclaration ► Stream: https://www.twitch.tv/narrativedeclaration ► Podcast: (Exclusive to Patreon) ► Website: https://narrativedeclaration.com/ ► Discord: https://discord.com/invite/narrativedeclaration (or: https://discord.gg/5ZgpHkBXbX ) PLAYERS ▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀ • @ZoranTheWizard as Fell Marrow: https://twitter.com/ZoranTheBear/ • @Kabhaal as Geren the Hewn: https://twitter.com/KabhaalVT • @FroggyLoch as Lalaoopsie: https://twitter.com/FroggyLoch • @SaltyJub as Buchtvana: https://twitter.com/SaltyJub • @PartyDemoness as Arasne: https://twitter.com/partydemoness • Maddikus as Vinki: https://twitter.com/Maddikus • @OnCallGM as our Game Master: https://twitter.com/OnCallGm OTHER CREDITS ▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀ Editor: @Ezekieru Thumbnail Art: SaltyJub https://twitter.com/SaltyJub Geren the Huge and They Be Giants Edits: By Fae https://bsky.app/profile/faeropmorphia22.bsky.social Background Music from: https://tabletopaudio.com/ & tabletoprpgmusic Intro Music: By CrazyTunes - "Medieval Music" All Rights Purchased #pathfinder2e #dnd

Comments

Afell Tale

Kab. You missed the opportunity to say 'This Big Buffoon'.

Brayden Leeds

Arasne embracing her inner Roy Mustang. You love to see it

toadbear

This is how its been explained to me by someone I know..... Wed-Fri is spent fixing whatever bugs were brought up during the last cycle. Weekends you try to avoid anything thats not a critical hotfix, in order to minimize service interruption during whats likely your peak concurrent player count. Monday generate reports from telemetry and Jira (or equivalent) from the last week, have a meeting, and make plans for the week. Tuesday is server maintenance day, because thats when you're traffic is going to be the lowest across all time zones (letting you work on core infrastructure with the least amount of impact). Depending on game, Tuesday may also be when patches are deployed. This gives you the rest of the week to hammer out bugs on LIVE prior to the weekend rush. If your devs love chaos, or always rushing fixes until the last minute, then major patches are going to be on a Friday. In either case, weekend is your monitoring period as the current build gets put under an amount of stress that you can never properly replicate in QA. Someone in LIVE OPs is either actively monitoring things, or at least on call if the servers fail over the weekend. Now ideally you should never need that kind of down time, or your back end is segmented enough to run semi-autonomously when one part of the system is down. But most game studios and their publishers don't wanna pay for that kind of resilience... so significant chunks of the back end code base have some kind of accretion problem, that they are avoiding by just restarting the various services on a routine basis. Think like the old days where "you need to reboot windows every couple of days, or runs like trash". Some really advanced MMO backends are more autonomous on a granular level, where Overhead management and the actual Game Services can keep doing its thing, even if another connected service is down. So you could, for example, keep the game running and work on the authentication gateways (aka the login services) and not have to kick out players. Theres also this concept of a rolling update, where you can have 2 versions of the game running in parallel. Your orchestrator software has to be able to talk to all available versions; But basically you deploy the new patch into the infrastructure, and all NEW instances of services will run the latest patch. Meanwhile existing instances of the game can keep running on the old patch version to avoid interruptions, giving time for players to naturally log off on their own. As instances depopulate and gracefully shut down, they still save to the database, and migrate it over to the new system if needed. The only time you would need to shut down the entire front end and back end is if the two versions in question are incompatible due to major changes; like database schema, what or how data is tagged in netcode, major security roll outs, architecture changes, etc. In that case the whole migration has to be done upfront and/or clean slate, and players file in once its back online. I know for sure Guildwars 2 can do this with most stuff, outside of massive content updates. And they're one of the few games crazy enough to run a unified BETA on the LIVE servers. By hooking up two account management systems (the normal LIVE database, and a cloned BETA database), enabling BETA client and characters to run on the same game servers as LIVE players. It really raises the question of how characters and class abilities fit in how the game servers operate. Because under normal circumstances the server would have to have all the code for 2 versions of every skill, in every class, to be able to run both versions coexist in the same map instance that like.

Carl Edward Tencheira-Jones

To Kab, I'm listening to you at work. They think I'm listening to a religious podcast so they can't tell me not to as it's not interrupting my ability to work.