This is mark Joseph “young” blog entry #440, on the subject of Changing Worlds.

With permission of Valdron Inc I have previously completed publishing my first seven novels,

1. Verse Three, Chapter One:  The First Multiverser Novel,
2. Old Verses New,
3. For Better or Verse,
4. Spy Verses,
5. Garden of Versers,
6. Versers Versus Versers, and
7. Re Verse All,

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 eighth, In Verse Proportion, 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.

It was suggested in connection with Re Verse All that shorter more frequent behind-the-writings posts would work better; they proved to be considerably more work in several ways.  Thus this time I am preferring longer, less frequent posts.  This is the third mark Joseph “young” web log post covering this book, covering chapters 43 through 63.  The first was web log post #432:  Whole New Worlds, covering chapters 1 through 21, and the second was #437:  Characters Relate, chapters 22 through 42.

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.

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.

Chapter 43, Slade 182

I had managed to steal some time to write the Brown and Kondor chapters back to back, and knew roughly what happened next for both of them, but ran headlong into another Slade chapter.  He’s got the engineers finishing up the telegraph and starting on water heaters and hot water heat, and I really have no idea what he does next–that is, there are other things he can invent, but he can’t invent everything at once.

As usual, I had my character think about things.  This time, though, by the time I was writing what he could create I’d already settled on the phonograph.  It was different enough from the telegraph and the hot water systems that it would involve an entirely different group of engineering students, I expected.

Chapter 44, Brown 209

I had concerns about whether I would be able to make this chapter long enough.  I knew that Derek was going to be darted by an animal husbandry robot, who would recognize that Derek was not one of the indigs and therefore, by its programming, an animal.  It would therefore effect the capture of the stray animal and attempt to determine where it ought to be to return it.  Derek of course was darted by the porcuperson dart, and he carries darts of that sort with him, so he knows the feeling.

The tension was between having Derek actually spend time looking for the devices and moving the story forward.  The linguistic conversations with Vashti were partly to pad the story, but they brought some interest at least to me.

Chapter 45, Kondor 187

Again I was afraid this was going to be a very short chapter.  The significant moment in my mind was that Kondor was going to carry Leah across the threshold into the bedroom, but I knew the scene had to end before there was anything, well, X-rated (or is that A-19 now?).  There wasn’t really enough time between crossing the threshold and being in bed to make a chapter.  Ultimately I decided I had to cover the trip from the dining room to the bedroom–which wasn’t easy, because my floorplan was rather sketchy.

Leah had expressed the intention to drink enough to relax herself, deal with her nerves.  Of course, she’s drinking wine–distilled beverages have not yet been invented here.  You have to drink quite a bit of wine to get very drunk, and while she might have done so I decided I didn’t want her three sheets to the wind, only mildly intoxicated.  That gave me something to talk about.

I knew that Kondor would close the door for privacy.  It struck me that this was a good way to tell the reader they were not invited to see what happens next.

Chapter 46, Slade 183

This was an awkward start because what I knew was that Slade wasn’t going to go to engineering, and the engineering professor was going to catch up with him at lunch.  But then, I knew that Shella slept in, and in my mind Slade has been more of an early riser, at least as compared with her, so I figured out how to burn the morning and headed for lunch.

On the between meals cafeteria, I was sort of remembering college–but the snack table (which I was originally thinking of as donuts and coffee, but realized I couldn’t make it that human) was added to provide something to do.  The image of students filtering in in anticipation of food was from my memories.

I reached the point at which I ultimately ended this chapter, thinking that I should have the engineering professor arrive and begin the conversation I’d planned for that, but then three things dissuaded me.  First, as the Slades got their food it was a good point to fast forward to the end of the meal.  Second, I’d written enough text for a moderate chapter.  Third, I wasn’t sure what would happen after that conversation, and at least if I stopped here I would know what I was writing the next time Slade came to the top of the pile.

Chapter 47, Brown 210

Going into this chapter, I knew that Derek awoke in a cage of some sort.  I figured a few things.  One was that the locks would be connected to the central computer, so he could override them, but he still would have to escape the robot.  Concerning the robot, it has decided that Derek is an animal, and that means it’s trying to classify him and figure out where in the artificial ecosystems of the ship he belongs.  It also means that because of its programming, it doesn’t “expect” intelligent speech from him and will automatically ignore any sound he makes as being that of an animal.  Birds might mimic human speech, but we don’t really believe they know what they are saying and so only take what they say seriously in the sense that they must be repeating something they heard.  Complicating it, I want Derek to come out of this adventure with a robot, and it makes sense for that to be this robot.  He’s either going to have to reprogram it or get it to access the computer to be reprogrammed.  That actually might not be so difficult–the robot will have no data on Derek, and the computer data will identify “it” as the ship’s first officer.  So maybe that will work.

One thing I haven’t decided is whether the robot will strip him of his equipment, and to what degree.  On the one hand, not knowing what he is supposed to look like it might not recognize, say, a backpack as not part of the body.  On the other hand, it would certainly think that an animal shouldn’t have a laser rifle.

And where did I leave that bicycle?  O.K., at this point I went back and reread several of the Derek Brown chapters in Versers Versus Versers, and determined that he had picked up the bicycle with his equipment when he arrived, and had brought it with him to the bridge.  I went back and added mention of the device in Brown 196, 199, and 217.

I must credit James Ward’s Metamorphosis Alpha for the idea that robots would not feed sounds made by intelligent animals through their language processing programs, because whatever the noise sounded like the first point was that animals don’t talk.  That world changed such that they do talk, or some of them, but the robots weren’t reprogrammed to recognize this.

I mentally played with how this was going to work, going through a lot of options, but realized that Derek had spoken to the computer before, and that would save me a chapter, probably.  But I didn’t want escape to be too easy, so I set up the next chapter.

Chapter 48, Kondor 188

Maintaining the PG adult fantasy fiction feeling, I jumped to morning.  I had to give some coverage to their wedding night, and I was recalling my own experience decades ago to some degree.

Chapter 49, Slade 184

I had originally intended for this to happen in the previous chapter, but as I noted I hit a good spot for a pause and I needed to keep Slade’s story from snowballing.  Most of this I had already covered, but it works as something for Slade to discuss with the head of engineering.

Chapter 50, Brown 211

I was getting Derek to suggest a plan for me.

The idea that robots have a cutoff comes from Star Frontiers, where our characters faced combat robots and had to remove a cover panel and hit a shutoff switch on the front of the robot.  It was an easily exploited vulnerability.  The idea that the switch was in the rear comes from Commander Data of Star Trek:  The Next Generation, who once revealed this to Commander Riker, only to have Riker in turn reveal it when Data was on trial to determine whether he had his own right of free will.

Chapter 51, Kondor 189

Brainstorming to fellow writer E. B. Slayer, it struck me that I would need to slow down Slade a bit, but that Kondor was also headed into a slow time.  I decided that after I finished this Kondor chapter I would go back to Derek and then Slade, reversing those two in the sequence.

I honestly didn’t expect this chapter.  It formed itself in my mind in fragments, although all the fragments had been placed in sequence before I started typing.

Chapter 52, Brown 212

I brought this forward because Derek’s story was pressing for a resolution and Slade’s just wasn’t.

I had pieced this together several ways in my mind, but the idea that Vashti would arrive and distract the robot was best.  I had considered having her be drugged while Derek was shutting down the system, but decided that I needed her to converse with Derek and bring out his thoughts.

Chapter 53, Slade 185

I was here faced with the problem of what to do with Slade when he wasn’t doing anything, and still have something worth reading.

The fountain was color.  The street wasn’t really new, but I wanted to recall the imagery and talk about the commercial aspect.

I had the birds notice Slade practicing in part because it occurred to me that I could get him involved in training indigs in fighting technique.  He had been here in the past practicing with his sword; they would undoubtedly have developed weapons like it.

Chapter 54, Kondor 190

Pretty much all I had going into this chapter was that Zeke would tease Joe, and a vague question about whether the couple would get any kind of special treatment.  But I had teased the idea of Zeke marrying one of the other princesses before this, and decided to put the idea in the text, whether or not anything might come of it.

Chapter 55, Brown 213

I had left reprogramming the robot to this chapter, so I had to do something with it.
In the gap, it occurred to me that Derek would not know in what sense he had shut off the robot, and it made a difference.

Chapter 56, Slade 186

As I mentioned, I had the idea of having parakeet swordsmen engage Slade in practice.  That always presents me with the challenge of how to make the combat interesting.  That is particularly so this time because I expect to make this a regular feature of his day, and while I won’t describe it in detail every time, I’m going to have to describe a few of them.

Chapter 57, Kondor 191

I will need a way to remove Kondor from this world eventually, and I have been thinking that another war should do the trick.  I’m prefiguring that now, making the reader aware of the potential enemies.  My geography follows the real world only very roughly, but adequately that I can use the real world countries for a sketch.

This is, of course, the same balcony on which Derek and Vashti and the others watched (or didn’t watch) the sunset in the earlier book.

Chapter 58, Brown 214

I debated what the possibilities were, and let Derek do the same thing.  I decided that it would be a good cliffhanger to have Vashti activate the robot and put off what happens to the next chapter.

Chapter 59, Slade 187

I was doing these sparring combats mostly because I needed to keep Slade’s story interesting.  The comment about combining the two fighters into one was intentionally setting up the next fight.

Chapter 60, Kondor 192

I saw this coming.  I didn’t really like it, but it gives me a chance to explain how Kondor, who has actually seen an elemental spirit of fire, can disbelieve in elemental spirits.

Chapter 61, Brown 215

I had to make several snap decisions for this chapter, the first being what the robot would do.  I discussed it briefly with Kyler, who thought that it having been shut down unexpectedly, it would believe it had malfunctioned and would head for maintenance.  I decided against this, because for whatever I was going to do with it, I needed Derek to acquire it.  Thus I went with a reboot-and-upgrade option.

My next complication was whether this was constructed as a zoological bot or as a general service bot with zoological attachments.  The former would be of much less use to me, so I went with the latter.

The unit number was just random digits; I saw that the last number was going to be 9, and remembered that this world used base 8, so there would be a conversion and the 9 would tell us that this was base 10.  I realized after I wrote it that the center two digits were consecutive; one of my sons has a penchant for four-digit numbers (PINs, phone numbers) in which the center two digits are consecutive and the first and fourth are also consecutive, and I almost changed the 9 to an 8 to achieve that while retaining my base 10 conversion, but I wasn’t sure even he would get it (or indeed ever read it or notice it if he did).

Chapter 62, Slade 188

I needed to combine the fighting styles of the two best birds without making it seem either too much like they knew how to fight together or that they were not smart enough to figure out any of that.  I also didn’t want Slade to be untouched entirely, but he should still win, and the touch should be something the reader would believe.

Chapter 63, Kondor 193

I’m sort of being dragged into this.  Kondor told Leah that there was no Mithra, and now she’s challenging his assumptions, trying to figure out if he might be wrong.

This has been the third behind-the-writings look at In Verse Proportion.  If there is interest and continued support from readers we will endeavor to continue with more behind-the-writings posts for it and another novel.

This is mark Joseph “young” blog entry #437, on the subject of Characters Relate.

With permission of Valdron Inc I have previously completed publishing my first seven novels,

1. Verse Three, Chapter One:  The First Multiverser Novel,
2. Old Verses New,
3. For Better or Verse,
4. Spy Verses,
5. Garden of Versers,
6. Versers Versus Versers, and
7. Re Verse All,

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 eighth, In Verse Proportion,  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.

It was suggested in connection with Re Verse All that shorter more frequent behind-the-writings posts would work better; they proved to be considerably more work in several ways.  Thus this time I am preferring longer, less frequent posts.  This is the second mark Joseph “young” web log post covering this book, covering chapters 22 through 42.  The first was web log post #432:  Whole New Worlds, covering chapters 1 through 21.

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.

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.

Chapter 22, Slade 175

This sat for over a week with the label “Brown” on it, and I was struggling with how to fast forward Derek’s story without making it feel like I just jumped over stuff.  Ultimately I made a sort of decision about that aspect, but also decided it would feel more like time had passed if I skipped Derek again and came back to Slade.

I have the solution to Slade’s problem, but they don’t have it yet, so it’s going to be delayed.

Chapter 23, Brown 202

My solution to the problem in the Brown story included setting up the feeling of weeks by talking about the calendar, and creating the Bridge Simulation Room to make it seem as if his training had advanced beyond book learning.

When I created the 8-day week I spent a lot of time thinking about it–I figured one day for each finger, but then I couldn’t decide whether it would be a five-day week in which no fingers was the day off, or a four-day week.  Since I’d made their math system base eight and tied it to their fingers (obviously for them the base eight was built on the number of fingers they had, although for me the number of fingers was decided so that I could give them base eight), I decided to tie their calendar to it.  I puzzled over why we have seven-day weeks, and thought it might be an argument for an original divine revelation of a seven-day creation, but ultimately recognized that seven is as close as you can get to a quarter of a lunar month, so there is some logic to it.  Since I know nothing about their planet of origin, I don’t need to figure out how their original calendar fit their astronomical conditions.  So ultimately I decided on an eight-day week with two days off, which originally would have been a standard weekend but that this would not apply to crewmen on the ship, who would have to work shifts to keep stations manned.

Chapter 24, Kondor 180

This was more a matter of necessary preliminaries to the chapter in which the dinner is actually held, but it also gave me an opportunity to play with cultural marriage expectations.

Chapter 25, Slade 176

I had worked out the solution to the legal problems and knew that they would be building a house for the Slades on the university property, and having the university hold the patents in trust for Bob.  The press problem, though, was something that struck me just as I opened the document to begin writing the chapter.  I’m not entirely sure how it will ultimately be handled, but we’ll get there eventually.

Chapter 26, Brown 203

This was actually the last of the pre-written chapters, that is, parts of the story that I wrote before I started the book, and indeed before I started Re Verse All, but that I also had some pre-written chapters for that while I was deciding which characters would feature in which book.  I honestly don’t know where this thread is going to go, or how it can get there, but it seemed an obvious concern for Derek.

Chapter 27, Kondor 181

I had been anticipating this chapter, and had several times mentally composed the opening section before I had a chance to type it.  Still, I had no idea where it was going, and indeed as I finished it I still did not know whether Leah was going to become Joe’s wife, or even if she might become Zeke’s wife.  Still, when Leah explained why she chose Joe, it struck me as exactly the sort of rational reason that would appeal to him.

Chapter 28, Slade 177

I had been thinking about this chapter for several days, even before I wrote the previous one.  I kept trying to figure out how I would present Slade explaining how to build a diaphragm microphone and a simple speaker, which are essentially the same thing with the use reversed, but I didn’t know exactly what would be used to insulate the wire back then, and I wasn’t sure how he would explain wrapping it in a coil, although I decided that they had electrical generators and motors, so they could do coils somehow.  Then I was just settling into the opening, “What we are inventing is kind of the next step up from the telegraph,” and I suddenly thought, wait, do they have a telegraph?  And if they did, what would they use for a code system?  And that then became the place to start.

Chapter 29, Brown 204

I was pondering how Derek could teach the indigs, and recognized several problems and no really good solutions, but I decided to get started on that and go from there.

Chapter 30, Kondor 182

I had been discussing what was going to happen with Joe and Leah with a couple people, one friend by e-mail, and in that the Fiddler on the Roof story had arisen.  As I was finally writing the chapter I bumped into a place where it was just what was needed, so I included it.  I still don’t know whether Joe and Leah will marry, and I’d better figure it out fast, because three chapters from now they’re going to make that decision.

Chapter 31, Slade 178

I wanted to delay the completion of the telegraph, and the idea that the bird language was something like singing very short songs had occurred to me, and I thought I should bring that into the story.  That would have been a very short chapter, but I had realized that there should be gas lighting already, but that I hadn’t done anything with gas inventions, so I could introduce those thoughts at this point.

Chapter 32, Brown 205

Derek and I are kind of stumbling through how to do this.  Maybe he should fail this time; I’m really not sure how to have him succeed without taking a lot longer than I can.  However, for the moment we’re going to try.

I expected this chapter to be pretty much Derek gets on the computer and finds the units in storage and has them delivered, but I realized that would be too short, and anyway Vashti has to be fed.  Thus I changed gears and wound up stretching enough that I never got to actually finding the things.

Chapter 33, Kondor 183

Obviously I had been thinking about this for a long time, and discussed it with several people.  There was a lot of potential in bringing Leah into Kondor’s life, and it really did make sense, so it happened here.

I also thought it really might offend the Caliph not to be invited to host the wedding.  It would make more sense for others to come to him than for him to travel to others, and he certainly should be invited.  At the same time, I needed to stretch the story without Leah aging too much, so wedding preparations had at least some potential here.

Chapter 34, Slade 179

I was thinking about what to write, but was thinking about Derek’s story, having forgotten that Slade was next.  Thus I came to this chapter with a very sketchy notion of how it should go.

I got as far as Slade asking the question of whether there was anyone at the university who studied language, and realized I did not know the answer but had to give one in order to continue.  So I took a break.  I knocked this question around for a couple weeks, I think, asking a few people their thoughts on it, and ultimately got a couple ideas of how to handle it.

Chapter 35, Brown 206

This chapter had been delayed because I was stuck in the middle of the previous Slade chapter, but in the process I was faced with the issue that the direction I was headed would either work too smoothly or be too complicated.  Then as I considered how to resolve that, I came up with the direction I decided to take.

Chapter 36, Kondor 184

This was the third wedding I was creating for my characters–fourth, if you count Sophia and James Beam–and I wasn’t sure how to keep it interesting, but I was going to push forward with it.  On the other hand, I did not want it to progress too swiftly, because I needed interesting story for Kondor while Slade and Derek moved forward in their worlds.

The Great Wedding Machine was something that my wife and at least one of her girlfriends talked about when they were planning our wedding.  I was hundreds of miles away at college in Massachusetts, so my involvement was pretty much limited to getting fitted for the tux and selecting the best man and ushers, although I worked with my fiancé to write the ceremony.

Chapter 37, Slade 180

Life was in the way of writing, and I was pondering this intermittently over several days.  I realized that Slade now had several irons in the fire, and I should shift to the house.

I had long had it in mind that Slade was going to create hot water on tap plus hot water heat and a gas stove and oven, but the house was going to have to be built with this in view.

It was also important that the house be large, and part of that was that I was expecting the eventual arrival of other versers, for whom Slade was going to have to have space at least initially.

Chapter 38, Brown 207

This had become a significant obstacle.  The problem was how Derek was going to get the handheld computers.  I didn’t want it to be so simple as he told the computer he wanted them and a robot delivered them, as that would be too much like The Industrial Complex that dominated so much of the previous novel.  On the other hand, were I to start him on a trek to go get them I would be caught between a simple uneventful boring trip that didn’t really show the dangers of this world versus a time consuming adventure that would make it difficult to get him accomplishing anything significant in this world before I needed to move him to join Kondor and Slade.  So I was kind of stuck trying to make sense of it.

After probably a week of no progress, I typed the first three paragraphs, in which he announced that he found them (I did not decide how or where) but didn’t know how to get them.  That seemed to be the next step, but didn’t give me where to go from there.

Then I quite abruptly hit a solution, and finished the chapter setting the next steps ahead.  It would be a trek, but limited.

Chapter 39, Kondor 185

I didn’t want this to be too like what I did for Slade and Shella, so I asked for some ideas.  My daughter-in-law Katelyn looked up Persian weddings, and picked up the imagery of an overwhelming decoration of brightly colored fabrics.  A writer I know online looked up Zoroastrian weddings, and came up with the bleached white dress, a candle flame which inspired the thing where they light the central candle together (I’m not sure whether I saw this at a wedding once), and the tying, which I remembered they do in Eastern Orthodox weddings (my artist Jim Denaxas got married in an Eastern Orthodox church).  The rest I invented on the fly.

In my first draft Kondor’s robe was described as “a chocolate color, which nearly matched his skin,” and so on with the embroidery.  One of my wedding advisors said that a brown robe was fine, but that chocolate colored was too cliché, particularly by white writers, so I should find a different word.  I expressed the difficulty that it had to be something Kondor could name–I could say it was burnt sienna, but that’s not a color he would know by that name–and it had to look good on him.  The advice was that he would look good in fire engine red, so I made it red and figured he wasn’t worried about the specific red so it wouldn’t be mentioned.

I considered the vows for several minutes.  I wanted them to be distinct both from those normally used in Christian services and from those I used for Slade and Shella, but to be similar in intent.  For these reasons I avoided “until death do you part” and “as long as you both shall live”, but that gave me “for the rest of your life”–and of course the commitment is not for as long as Kondor lives, but for as long as they both live.  That made it “lives”, and gave me the opportunity to comment on that.

I also hesitated on exactly what would be promised.  In my own wedding the vows were matched, that we promised each other the same things, and although I changed exactly what that was I reflected that in the Slades’ wedding.  Here I thought the disparity of gender would be a factor, and so I made his “love and protect” and hers “love and serve”.  I also replaced “I do” with “I promise”, again so it would be distinct from our weddings.

I decided to include wedding rings, but to do so in a way that suggested they were not part of the traditions in the Caliphate but were added by Kondor.  I also assumed he would have had them made from his own stock of treasure, which means one of his gold diktar and some gems, particularly the emeralds with which he is so well stocked, but some rubies to offset that.

Chapter 40, Slade 181

Having had Slade tell the architect he was going to include hot water and hot water heat in his new home, I figured that he was going to have to get the engineering department working on inventing these things.  Since he had already described part of it to the architect, I could gloss that part and just put in the additional information needed for them.

I hadn’t really planned it, but it struck me that building the house would enable me to keep the story moving without overburdening the invention process or pushing the inventions out too fast.  It gives me something else to cover.

Chapter 41, Brown 208

My writing efforts hit several real world delays, complicated by my uncertainty of exactly how to proceed, but in that time my thoughts on Derek shifted.  My concept of the trek had included that they were going to find a robot that could be programmed to act as translator and/or find the hand-helds for him, and that they would encounter a carnivore, either a lone hunter or a pack, possibly mutant.  I was undecided about the specific function of the robot; I did know that it would have to be reprogrammed to recognize Derek and Vashti as officers.  It then occurred to me that my encounter could be with the robot, or with a robot, which was a husbandry module and which identified them as not a “person” by its standards and therefore an animal, and proceeded to capture them.

The precaution of leaving something near the elevator was a thought I’d had at that instant, and decided to treat it that way for Derek as well.  I also thought he would think that Vashti should also leave something, even though she doesn’t have much, because she can’t sense his belongings if they get separated.

Chapter 42, Kondor 186

I thought this was going to move quickly to Joe carrying Leah over the threshold into their bedroom, but I didn’t want to rush things so I wound up working my way through the reception.

This has been the second behind-the-writings look at In Verse Proportion.  If there is interest and continued support from readers we will endeavor to continue with more behind-the-writings posts for it and another novel.

This is mark Joseph “young” blog entry #409, on the subject of Characters Cooperate.

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 twenty-fifth mark Joseph “young” web log post covering this book, covering chapters 145 through 150.  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:

1. #354:  Versers Reorienting, covering chapters 1 through 6;
2. #355:  Versers Resettling, for chapters 7 through 12.
3. #357:  Characters Connect, for chapters 13 through 18.
4. #359:  Characters Engage, for chapters 19 through 24.
5. #361:  Characters Explore, for chapters 25 through 30.
6. #364:  Characters Learn, for chapters 31 through 36.
7. #365:  Characters Travel, for chapters 37 through 42.
8. #367:  Versers Encounter, for chapters 43 through 48.
9. #370:  Characters Confront, for chapters 49 through 54.
10. #373:  Nervous Characters, for chapters 55 through 60.
11. #376:  Characters Arrive, for chapters 61 through 66.
12. #379:  Character Conundrums, for chapters 67 through 72.
13. #381:  World Complications, for chapters 73 through 78.
14. #383:  Character Departures, for chapters 79 through 84.
15. #385:  Characters Ascend, for chapters 85 through 90.
16. #388:  Versers Climb, for chapters 91 through 96.
17. #390:  World Facilities, for chapters 97 through 102.
18. #392:  Characters Resting, for chapters 103 through 108.
19. #395:  Character Obstacles, for chapters 109 through 114.
20. #397:  Verser Challenges, for chapters 115 through 120.
21. #401:  Characters Hiking, for chapters 121 through 126.
22. #403:  Versers Innovating, for chapters 127 through 132.
23. #405:  Versers Converge, for chapters 133 through 138.
24. #407:  Versers Integrate, for chapters 139 through 144.

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.

Chapter 145, Beam 114

I didn’t really have much to write on this but to keep the group moving.  The book Lauren is reading is of course her Bible.

Chapter 146, Hastings 229

I knew Beam was going to have more confrontations, but that these would not be terribly interesting story-wise if they were always from his perspective.  The notion that some other tribe was occupying the buffet made for a good conflict which Lauren could both observe and resolve without being at the front of things.

Chapter 147, Takano 56

I knew that the space would become more crowded as they approached the surface, and decided that level six was a good spot for the real complications to begin.  The maintenance control room seemed a logical spot, as it would be spacious enough.

Chapter 148, Beam 115

I needed Tommy to practice, and Beam to recognize that she was not secretly a powerful ninja, and also to recognize some other things about them.

Having Beam discuss the problems ahead with Bron seemed the best option.

Chapter 149, Hastings 230

Since Tommy would be needed to lead the people back to the ramp, I figured I could put Bron in back and have some exchange of information between him and Lauren.  I also set myself up for her to teach him some magic, but of course we have that issue that the god of this world honors magic but tries to push people toward technology, so magic is wonky.

Chapter 150, Takano 57

I was filling Kyler in on some of what was happening in the story, and he commented that based on the personality of the person on whom the character was based he was pretty sure that Beam would have been flirting with Tommy.  That’s a problem for me, because I have no talent for flirting with younger girls, but apparently he does, so I was going to have to figure out how to work in that he was flirting somewhat effectively without pretending I know how to do that by writing it.  I’m still not sure how that’s going to work, but it starts with Tommy wondering about it.

I wrote part of it, then decided I was out of my depth, printed it for Kyler who was perhaps equally stymied, and then sent a message to friend Cassandra, who had helped with the question of how to get Tommy involved with her peers in the suburban world.

Ultimately I used a lateral break to get out of the flirting question; the discussion of physical training was really there as an escape.  I was still waiting to hear from my friend.  I had not heard from her before I finished the book.

This has been the twenty-fifth 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.

This is mark Joseph “young” blog entry #407, on the subject of Versers Integrate.

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 twenty-fourth mark Joseph “young” web log post covering this book, covering chapters 139 through 144.  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:

1. #354:  Versers Reorienting, covering chapters 1 through 6;
2. #355:  Versers Resettling, for chapters 7 through 12.
3. #357:  Characters Connect, for chapters 13 through 18.
4. #359:  Characters Engage, for chapters 19 through 24.
5. #361:  Characters Explore, for chapters 25 through 30.
6. #364:  Characters Learn, for chapters 31 through 36.
7. #365:  Characters Travel, for chapters 37 through 42.
8. #367:  Versers Encounter, for chapters 43 through 48.
9. #370:  Characters Confront, for chapters 49 through 54.
10. #373:  Nervous Characters, for chapters 55 through 60.
11. #376:  Characters Arrive, for chapters 61 through 66.
12. #379:  Character Conundrums, for chapters 67 through 72.
13. #381:  World Complications, for chapters 73 through 78.
14. #383:  Character Departures, for chapters 79 through 84.
15. #385:  Characters Ascend, for chapters 85 through 90.
16. #388:  Versers Climb, for chapters 91 through 96.
17. #390:  World Facilities, for chapters 97 through 102.
18. #392:  Characters Resting, for chapters 103 through 108.
19. #395:  Character Obstacles, for chapters 109 through 114.
20. #397:  Verser Challenges, for chapters 115 through 120.
21. #401:  Characters Hiking, for chapters 121 through 126.
22. #403:  Versers Innovating, for chapters 127 through 132.
23. #405:  Versers Converge, for chapters 133 through 138.

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.

Chapter 139, Hastings 227

I had debated on what level Lauren and Tommy would encounter Beam, and had shifted in my mind from level four to level eight.  At the last moment I decided that it would be really odd for Lauren and Beam to have adopted the same day/night schedule, so I decided that the girls would be having dinner at the point where Beam was going to stop for lunch.  That meant an odd numbered level, and I went with level nine.  Lauren still has to decide to travel with Beam, which I’ll have to work out in the next chapter.

It was sort of a last minute decision to have Tommy in the hall when Beam arrived.  I had long known that when the confrontation occurred Lauren could easily raise her psionic shield (she doesn’t know absolutely that it would work, but it has been reliable in the past), but by putting Tommy out of sight I prevented her from doing so immediately.

Chapter 140, Beam 112

I needed to bring the two groups together cautiously.  The notion that Tommy’s graffiti distracted Beam giving the girl the chance to get back to Lauren before the confrontation was kind of abrupt.

The idea that Beam suspected Tommy of being a ninja was abrupt but logical.  After all, Beam wouldn’t take someone along who didn’t contribute in some significant way, and he is a bit awed by Lauren’s powers so he assumes that Tommy must offer something significant to that.

The television reference is to a Tom Baker Doctor Who episode, The Ribos Operation in The Key to Time series, in which the Doctor identifies a young man as a thief and Romana (Romana 1) makes the comment about his honest face and gets that response.

I knew the kawanaga was a ninja weapon, but didn’t expect anyone to recognize it as such so soon–but Beam’s gaming experience would have meant that, like Lauren, he was exposed to such weapons, and the more so because he was a more serious gamer than she was.  Of course, he doesn’t really care if she’s a ninja for the reasons that matter in game, but rather because he thinks that if she is that gives her hidden skills of which to be wary.

Chapter 141, Takano 54

I put Lauren and Tommy on rear guard partly so they could talk about their relationship with Beam.  I moved into the concerns about the computer mostly for fill, but it had occurred to me before that Tommy’s computers might be infected by whatever was bringing down the central system, and I wanted that to occur to her.

At this point I thought I should shift to running the three viewpoint characters in turn, but I had already decided that as they approached the surface they were going to encounter more groups of people, and it kind of had to start with level eight and Beam had to be the front man for it.

Chapter 142, Beam 113

I had not intended to get involved in an effort to fix the main computer, and for plot reasons I know it’s going to fail, but once Tommy started asking about the system problems, which really was inevitable, it just naturally led to a consideration of whether they could be repaired.  The notion of obtaining a clean copy of the basic operating system by ordering a new computer was valid, but won’t work because of the auto update feature that’s been incorporated in more recent computers.

This chapter was supposed to be the confrontation with another tribe, and instead turned into the computer discussion.  I’m not sure how the confrontation is going to play, particularly as it looks as if it has to be done from Lauren’s perspective, and she’s in the rear.

Chapter 143, Hastings 228

I struggled with how to convey the population problem, but it actually worked better with Lauren deducing the problem than it would have with me trying to have Beam confront multiple groups of residents.

I sort of stumbled into the mattress store idea.

Chapter 144, Takano 55

Once I had the mattress store idea it was obvious that Tommy would lead the way to get there.  It also gave me more spotlight for her, making her a more significant part of the group, and probably also showing Beam that she contributed something to the team.

This has been the twenty-fourth 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.

This is mark Joseph “young” blog entry #405, on the subject of Versers Converge.

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 twenty-third mark Joseph “young” web log post covering this book, covering chapters 133 through 138.  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:

1. #354:  Versers Reorienting, covering chapters 1 through 6;
2. #355:  Versers Resettling, for chapters 7 through 12.
3. #357:  Characters Connect, for chapters 13 through 18.
4. #359:  Characters Engage, for chapters 19 through 24.
5. #361:  Characters Explore, for chapters 25 through 30.
6. #364:  Characters Learn, for chapters 31 through 36.
7. #365:  Characters Travel, for chapters 37 through 42.
8. #367:  Versers Encounter, for chapters 43 through 48.
9. #370:  Characters Confront, for chapters 49 through 54.
10. #373:  Nervous Characters, for chapters 55 through 60.
11. #376:  Characters Arrive, for chapters 61 through 66.
12. #379:  Character Conundrums, for chapters 67 through 72.
13. #381:  World Complications, for chapters 73 through 78.
14. #383:  Character Departures, for chapters 79 through 84.
15. #385:  Characters Ascend, for chapters 85 through 90.
16. #388:  Versers Climb, for chapters 91 through 96.
17. #390:  World Facilities, for chapters 97 through 102.
18. #392:  Characters Resting, for chapters 103 through 108.
19. #395:  Character Obstacles, for chapters 109 through 114.
20. #397:  Verser Challenges, for chapters 115 through 120.
21. #401:  Characters Hiking, for chapters 121 through 126.
22. #403:  Versers Innovating, for chapters 127 through 132.

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.

Chapter 133, Takano 52

I’m hoping the graffiti will be something different for the reader.  The discussion of attacks and blocks has given me a problem, though, because it’s obvious to me that Tommy would see she could order a weapon from the computer even though it wouldn’t occur to Lauren, and I’m facing the perennial problem that if Lauren teaches Tommy to fight with the same weapon Lauren uses, Tommy will fight like Lauren and my stories will be more the same.

Chapter 134, Beam 109

I had mentally created two disruptions for Beam, and having two trucks going opposite directions was one of them.  I was not certain I wouldn’t lose someone, but I played it out and managed what I think was a moderately tense scene.

It was also a bit of a tricky scenario to envision, and I wound up re-writing because I believed I had the ascending and descending trucks reversed in one paragraph–the descending truck had to pass behind the ascending truck, which had moved out of the lane, and the ascending truck had to return to its left.  I was still making corrections the day I released it.  Anyway, I hope that’s correct.

Chapter 135, Hastings 226

I had been struggling over the question of how to keep Tommy from becoming a Lauren clone, and pulled out my old Advanced Dungeons & Dragons Oriental Adventures book.  I quickly found the kawanaga, and liked it immediately–it was similar enough in name that Tommy could have ordered it by mistake, and it was a flex weapon similar enough to the kau sin ke that Lauren would be able to adapt her techniques to it while different enough that it couldn’t do everything Lauren did but could do quite a few things she couldn’t.  I ran it past Kyler, who agreed that it was exactly the sort of thing he was thinking.

The recollection that Lauren was “into” horses as a girl suggested to me that she probably had handled a lariat at some point, and throwing a grapple is undoubtedly easier, so she could adapt some of those techniques to explain why she was able to use the rope weapon so readily.

Chapter 136, Beam 110

For a while I had in my head that one of the events in the Beam pilgrimage would have to be encountering another large group.  This was that.  I did not know how it would go, but felt my way through it.

Chapter 137, Takano 53

Lauren and Tommy are about to connect with Beam, but I wanted to create the feel of multiple days of travel and practice before they did.

Chapter 138, Beam 111

I had managed to bring Beam up far enough that it was time for him to intersect with Lauren.  The discussion of why he was unaware of her approach but Dawn wasn’t I thought obvious and straightforward.

I intentionally misspelled the name of the other group leader because it would reflect the fact that Beam didn’t care.

This has been the twenty-third 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.

This is mark Joseph “young” blog entry #403, on the subject of Versers Innovating.

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 twenty-second mark Joseph “young” web log post covering this book, covering chapters 127 through 132.  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:

1. #354:  Versers Reorienting, covering chapters 1 through 6;
2. #355:  Versers Resettling, for chapters 7 through 12.
3. #357:  Characters Connect, for chapters 13 through 18.
4. #359:  Characters Engage, for chapters 19 through 24.
5. #361:  Characters Explore, for chapters 25 through 30.
6. #364:  Characters Learn, for chapters 31 through 36.
7. #365:  Characters Travel, for chapters 37 through 42.
8. #367:  Versers Encounter, for chapters 43 through 48.
9. #370:  Characters Confront, for chapters 49 through 54.
10. #373:  Nervous Characters, for chapters 55 through 60.
11. #376:  Characters Arrive, for chapters 61 through 66.
12. #379:  Character Conundrums, for chapters 67 through 72.
13. #381:  World Complications, for chapters 73 through 78.
14. #383:  Character Departures, for chapters 79 through 84.
15. #385:  Characters Ascend, for chapters 85 through 90.
16. #388:  Versers Climb, for chapters 91 through 96.
17. #390:  World Facilities, for chapters 97 through 102.
18. #392:  Characters Resting, for chapters 103 through 108.
19. #395:  Character Obstacles, for chapters 109 through 114.
20. #397:  Verser Challenges, for chapters 115 through 120.
21. #401:  Characters Hiking, for chapters 121 through 126.

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.

Chapter 127, Hastings 224

I kind of stumbled into most of this because I needed something.  They are actually getting close to the truth about the people, but I don’t think it will ever be confirmed.

Chapter 128, Beam 106

I had set myself up for this speech, although I had not rehearsed it.  Even the opening was spur of the moment.  I have not even decided whether he loses anyone when he continues.

I asked Kyler his thoughts, and he said roll a charisma check and use relative success.  Since I specifically don’t use dice to guide the stories in the books, I’m going to have to think it through a different way.

Chapter 129, Takano 51

For at least two days I pondered what I could write for Tomiko, opening the last Hastings chapter and closing it again several times.

I came to these thoughts by imagining the duo walking in the plain hallways and comparing that to walking in our world.  It struck me that there wasn’t even any artwork.  I had been thinking about what I thought about when I used to walk, as home from school and such or hiking with scouts, and I’m afraid I was very internalized.  However, it struck me that other people on walks notice the world around them (I had been watching the BBC’s Springwatch program, hosted by such people) and that Tommy had nothing to notice.  The chapter developed from there.

I feel like the chapters are too intellectual, because I’m struggling to get Beam to the surface and it’s a long trek which has to be broken up with stories of Tommy and Lauren, who are similarly on a long trek trying to get to him.  I’m pushing to get to the end and start the read-through edit–this past weekend I published the last installment of Versers Versus Versers and started posting the support materials, so I’m going to be done soon and needing the next book.

Chapter 130, Beam 107

I was going to take thirty from Beam’s crew, but got confused about how many were in which groups and which group belonged to Tennan Tamis.  I wound up taking twenty five, mostly from his group, then upped it to thirty; I had never established which group lost the people killed in the accident.

Having Beam climb two levels was a push I knew I could do based on his mood–he’s a bit angry about people turning away from him, even before he knows how many he lost.  The third level was an extra I added because I figured I had a chance to push the story forward a bit faster.

I hate bean soup, but the guy on whom Beam is based loves it and frequently when he visits us he makes a big pot of it and leaves it in our refrigerator until it goes bad and I throw it away–but then, I don’t know whether anyone else likes it because frankly I’m generally the only one who really eats the leftovers.

Again I had to adjust the numbers because I had gotten it in my head that there were about a hundred fifty when it was only just over a hundred.  I had to cut down several of the numbers to make it work.

Chapter 131, Hastings 225

The double T image was the first graffiti idea I had; the sun comes from memories of native American symbols, and the spiral was because I needed at least three that were recognizable.

I had set up the paint delivery in the previous chapter but hadn’t mentioned it to Lauren, so this was all surprise to her.  Tommy is experimenting and will probably improve at graffiti over time.

Chapter 132, Beam 108

I had been complaining to myself that at one level a day it was going to take a long time to get Beam out of the caves.  Each level took at least one chapter, and complications usually caused them to take longer but were needed to keep the story interesting.

I was seriously thinking about packing four levels into this chapter by covering two days, but as I was writing I had two significant events enter my head both of which would probably stretch the chapter–one a problem with two trucks going opposite directions, the other a confrontation with another tribe, probably inhabiting one of the apartments.

This has been the twenty-second behind the writings look at Re Verse All (and the one hundredth look behind the writings of the Multiverser novel series).  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.

This is mark Joseph “young” blog entry #401, on the subject of Characters Hiking.

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 twenty-first mark Joseph “young” web log post covering this book, covering chapters 121 through 126.  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:

1. #354:  Versers Reorienting, covering chapters 1 through 6;
2. #355:  Versers Resettling, for chapters 7 through 12.
3. #357:  Characters Connect, for chapters 13 through 18.
4. #359:  Characters Engage, for chapters 19 through 24.
5. #361:  Characters Explore, for chapters 25 through 30.
6. #364:  Characters Learn, for chapters 31 through 36.
7. #365:  Characters Travel, for chapters 37 through 42.
8. #367:  Versers Encounter, for chapters 43 through 48.
9. #370:  Characters Confront, for chapters 49 through 54.
10. #373:  Nervous Characters, for chapters 55 through 60.
11. #376:  Characters Arrive, for chapters 61 through 66.
12. #379:  Character Conundrums, for chapters 67 through 72.
13. #381:  World Complications, for chapters 73 through 78.
14. #383:  Character Departures, for chapters 79 through 84.
15. #385:  Characters Ascend, for chapters 85 through 90.
16. #388:  Versers Climb, for chapters 91 through 96.
17. #390:  World Facilities, for chapters 97 through 102.
18. #392:  Characters Resting, for chapters 103 through 108.
19. #395:  Character Obstacles, for chapters 109 through 114.
20. #397:  Verser Challenges, for chapters 115 through 120.

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.

Chapter 121, Takano 49

I had Lauren order breakfast to demonstrate that she had learned how to use the computer to obtain food.

This was another nothing happens leg of the journey, but I decided to delve a bit into the background for the world by having Tommy ponder the design of the machine and why the world was as it was.

Chapter 122, Beam 103

Bron’s decision to get the power tools was something of an abrupt choice.  I figured he knew how to use them from the bunker, and he knew they were more efficient than what they were using, and it made sense for him to add them to his cart.

I had envisioned the destructive wake of the mining machine previously, and wanted to continue the evidence that the computer was malfunctioning, so having it destroy the restaurants and head somewhere else made sense.

Chapter 123, Hastings 223

I was on some level filling space as I turned to Lauren musing about guidance and whether she was right in seeking the other verser and dragging Tommy along with her.  I don’t think it was wasted, though, as her musings on guidance are of some value.

Chapter 124, Beam 104

The double reason to have the construction crew stand by the bridge was obvious, but actually I thought of the second reason first:  they would have to be there in case the bridge broke, so they could repair it.  It would be better, though, for that not to be the first reason, and the idea that they should be honored for their work was an easy idea to set first.

I knew these chapters were all short, but it was difficult to make them longer.  The story was being told in pieces.

Chapter 125, Takano 50

I knew it was a training day, and I knew they would be stopping in an apartment block, so I had to wrap my head around what they would have that Lauren could use as training equipment.  I remembered that in my own game Raiden had me walk on the backs of benches; I didn’t remember whether I had included that in Lauren’s training, but it seemed likely and anyway a reasonably obvious option.  The mattresses were not as obvious, because I wasn’t sure whether I had previously said they could or could not be removed, but I wanted Tommy to have a soft surface for rolling and falling, so I decided to go with that.  I still have to do a read-through edit, so maybe I’ll notice if I didn’t make them removable, and I’ll try to reconcile it then.

I had actually thought of pot roast for the last Beam chapter, but didn’t go for it, and then this time I decided that it would work for Tommy and Lauren.  I did not decide whether it was pork or beef, but instead ignored the question.

Chapter 126, Beam 105

The potential mutiny of the people struck me, given that they had climbed eight levels and nothing was different.  I’ve set myself up for a Beam speech, which I’m going to have to figure out in his next chapter, but I’m not too worried about it.  I am worried about how I’m going to decide whether he loses people, and who he loses.

This has been the twenty-first 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.