This is mark Joseph “young” blog entry #381, on the subject of World Complications.
With permission of Valdron Inc I have previously completed publishing my first six novels, Verse Three, Chapter One: The First Multiverser Novel, Old Verses New, For Better or Verse, Spy Verses, Garden of Versers, and Versers Versus Versers, in serialized form on the web (those links will take you to the table of contents for each book). Along with each book there was also a series of web log posts looking at the writing process, the decisions and choices that delivered the final product; those posts are indexed with the chapters in the tables of contents pages. Now as I am posting the seventh, Re Verse All, I am again offering a set of “behind the writings” insights. This “behind the writings” look may contain spoilers because it sometimes talks about my expectations for the futures of the characters and stories–although it sometimes raises ideas that were never pursued, as being written partially concurrently with the story it sometimes discusses where I thought it was headed. You might want to read the referenced chapters before reading this look at them. Links below (the section headings) will take you to the specific individual chapters being discussed, and there are (or will soon be) links on those pages to bring you back hopefully to the same point here.
There is also a section of the site, Multiverser Novel Support Pages, in which I have begun to place materials related to the novels beginning with character papers for the major characters, giving them at different stages as they move through the books.
This is the thirteenth mark Joseph “young” web log post covering this book, covering chapters 73 through 78. It was suggested that more shorter posts were a better choice than fewer longer ones, so there will be posts every six chapters, that is, every other week, for this book. Previous entries were:
- #354: Versers Reorienting, covering chapters 1 through 6;
- #355: Versers Resettling, for chapters 7 through 12.
- #357: Characters Connect, for chapters 13 through 18.
- #359: Characters Engage, for chapters 19 through 24.
- #361: Characters Explore, for chapters 25 through 30.
- #364: Characters Learn, for chapters 31 through 36.
- #365: Characters Travel, for chapters 37 through 42.
- #367: Versers Encounter, for chapters 43 through 48.
- #370: Characters Confront, for chapters 49 through 54.
- #373: Nervous Characters, for chapters 55 through 60.
- #376: Characters Arrive, for chapters 61 through 66.
- #379: Character Conundrums, for chapters 67 through 72.
History of the series, including the reason it started, the origins of character names and details, and many of the ideas, are in earlier posts, and won’t be repeated here.
I was beginning to get boxed in with Lauren. I had promised that she would not get back to the city alive, but at this point she could easily jump over all the dangers ahead. I had, as it were, too many commitments, and too few options.
I was getting worried about Tommy’s story, because there wasn’t much else to do with it. I kept prefiguring a fatal car accident, but it was too soon to put her in her final world. The answer that struck me was that I needed another world, perhaps a stall world, perhaps something more serious, and then when everything else was ready I would bring her into the final setting.
This was all routine stuff, and I was trying to get through it quickly without making it more boring than it might be. There was more boring stuff ahead.
I didn’t name the third leader, partly because I was tired of naming people, partly because doing so would push toward more detail I didn’t want. That became a bit of a problem when I started writing the next book, and Lauren had to meet the group leaders, because he needed a name then and I had to be certain I hadn’t incidentally given him one somewhere along the way.
The darkness occurred to me belatedly. I had even considered having the light spell be still effected, but that would create a problem for me that the party would have managed to get past all the dangers, and I would be stuck trying to find a way to verse out Lauren before they reached the surface. However, I had already decided that there was some small amount of light near the entrance to the drow kingdom, because despite their superior dark vision there were some things that not even a drow could see without light. That gave me a target point and space for more story.
I had discussed the situation with Kyler, who felt that if the actual assassins had fled the scene the nobles would not have been too particular about whom they executed, and there was no climate for negotiation at this time. Further, he felt that Gojo and Sheegoka would quickly recognize this and agree to depart.
I really had no idea what to do with this world, other than to have Tommy struggle to survive it. That, though, was as good a place as any to start.
When I was setting this behind-the-writings section for HTML publication it occurred to me that this snow-filled forest is very like a stall world that has been used in play, originally by Richard Lutz and once by me. It has happened to Michael di Vars (a.k.a. Roland of the Sar) that he has versed in at the top of a snow-capped mountain more than once, and died trying to get to the bottom. I used that once in a demo game, including having di Vars there to explain things to a new verser (player character) before they both fell to their deaths. I was getting tired of the Tropical Island scenario. This lacks the mountain and the consequent climbing hazard, but it is a survival against the cold scenario.
Honestly I was caught between trying to move this story forward and recognizing the complexities of what Beam was doing. I needed the people to learn how to use the technology, but it had to be obvious that this wasn’t happening quickly. I didn’t really like it much at all.
This has been the thirteenth behind the writings look at Re Verse All. If there is interest and continued support from readers we will endeavor to continue with another novel and more behind the writings posts for it.