Tabletop roleplaying games are generally about shared storytelling, and stories are generally pretty boring if the story ends because the protagonists don't find the clue, don't get past the locked door, or don't survive a battle. Failure needs to continue the story by leading to something else interesting, being only a partial failure, or being success at a cost.
I will detail some of the concepts and approaches used by different systems, including several open source alternative roleplaying games, that can be incorporated into your game, even if the specific mechanics are not.
A related concept is the treatment of character death, which is usually the ultimate failure.
Some systems, like early Dungeons & Dragons, or revival games like Dungeon Crawl Classics, treat the adventuring group more like a wargaming troop, where when one character dies the next steps up to continue as the protagonist. Other modern systems have more explicit success at a cost mechanics or alternative ways to handle death.
The discussion is organised by concept, with examples given from different systems, including Fate, Dungeon World (Powered by the Apocalypse), Blades in the Dark, and Gumshoe.
Continue reading RPG Mechanics: Success at a cost(18 min read)
Network address translation 6-to-4 (NAT64, RFC 6146) is a transition technology that can be used, in conjunction with DNS64 (domain name system 6-to-4, RFC 6147), to replace NAT44 in dual-stack networks, and allowing support of IPv6 only devices.
Dual stack is a common deployment solution for adding IPv6 for both consumer and corporate networks, although IPv6-only is becoming more common, with the typical guidance being "IPv6-Only Where You Can, Dual-Stack Where You Must"
Even if you are still stuck in dual stack, it still makes sense to use some of the IPv4 as a Service technologies, such as NAT64 and DNS64, which have the upside of allowing you to support IPv6 only devices, and no downside. As an additional benefit, you also get valuable experience in IPv6 systems.
The cost is that you need to have infrastructure that supports NAT64, either provided by your ISP, or from your own networking equipment/router. This is not as much an issue for DNS64, as public DNS64 is available, e.g. Google.
If your network supports it, look at implementing NAT64 + DNS64 today; if it does not, contact your equipment provider to find out when they will support this important technology for IPv6.
Continue reading Running NAT64 in a dual stack network(5 min read)