Sburb v8.15 – Undead Gamemode Walkthrough
Windows
Jump to:
Sburb - Undead Gamemode Walkthrough Version 8.15, August 21st, 2021 By=============================== TABLE OF CONTENTS ================================ 1. Entrances and Exits & The Latter's Lack Thereof... [0000] 2. Walkthrough ...................................... [A000] 2.1. Pre-Entry & Friendship Management .............. [A000] 2.2. Post-Entry & How to Tolerate Your Sessionmates.. [A100] 2.3. The Medium & The Incipisphere................... [A200] 2.3.1.
................... [A201] 2.3.2.
................... [A202] 2.4.
......... [A300] 2.5.
................. [A400] 3.
............................... [B000] 3.1.
.................... [B000] 4.
......................................... [C000] 4.1.
......................................... [C000] 4.2.
............................ [C100] 4.3.
...................................... [C200] ================================================================================== [0000] Entrances and Exits & The Latter's Lack Thereof ==================================================================================
![]()
![]()
![]()
![]()
![]()
================================================================================== [A000] Pre-Entry & Friendship Management ================================================================================== Firstly, you should note that you will need to connect in a particular order. Once you have actually entered the Medium, it shan't matter as much, but your entry process will be guided by one other of your sessionmates and you will guide one other of your sessionmates through their entry process. There will need to be a particular server chain. Let us imagine that there are four players to this session, under the chumhandles AA, BB, CC, and DD. With this in mind, we may construct a sort of daisy chain necessary to enter the game. AA > BB > CC > DD > AA AA will connect and serve as server to client BB, who will be the server for client CC, who will be the server for client DD, who will loop back and serve AA. Simple as that! But, oh, what is this? Let us imagine that BB and CC have a certain amount of unfortunate history. CC ran over BB's dog or something of the sort--perhaps ran over BB's lusus, if you are so trollianly inclined. With BB in the role of server to CC, they possess a certain amount of control over the latter's environment. There are a slim few number of machines to place, but even just moving around objects, BB may neglect the consequences of their actions and "accidentally" drop a bed onto CC's head, fracturing their skull and killing them instantly. How awful, BB will bemoan! I never meant to do such a thing, they will claim! And then, it will very shortly become clear that the resulting session without CC is completely unsalveageable, thanks to their participation being necessary (even if in some small part, to surmount a particular obstacle). I'm sure you can imagine we don't want that happening. So let us arrange your connection chain with a little more care. If AA gets along better with CC, and BB is particularly infatuated with DD, then we can take such things into account when structuring the connection order. DD > BB > AA > CC > DD Et voilà! Our chain will result in as minimal casualty and accidental damage as possible, and we are ready to begin connection.
![]()
![]()
![]()
![]()
![]()
![]()
![]()
![]()
![]()
![]()
![]()
![]()
![]()
![]()
![]()
![]()
![]()
![]()
![]()
![]()
![]()
![]()
![]()
![]()
![]()
![]()
![]()
![]()
![]()
![]()
![]()
![]()
![]()
![]()
![]()
![]()