Brandon Sanderson

Dragonsteel Entertainment
  • Content count

  • Joined

  • Last visited

  • Days Won


Brandon Sanderson last won the day on January 30 2016

Brandon Sanderson had the most liked content!

Community Reputation

5,316 Worldhopper

About Brandon Sanderson

  • Rank
  • Birthday 12/19/1975

Profile Information

  • Gender
  • Location
    Provo, Utah

Recent Profile Visitors

16,104 profile views
  1. Happy Birthday Brandon!!


  2. Happy Birthday Brandon! I know you won't see this, but have a great day!

    Happy Birthday to you!

    Happy Birthday Day to you!

    Happy Birthday to Brandon!

    Happy Birthday to you!


    ...boy does it feel weird wishing happy birthday to a corpse

  4. Happy Birthday! You are the bestest author ever!


  6. This is an order to get back on the Shard disguised as a happy birthday wish.

    Happy Birthday!

  7. Well, you're never gonna see this, but Happy Birthday! Thanks for answering one of my questions.

  8. Happy (late) birthday!

  9. Haaaaappy Koloss-Head-Munching-Day to you!

    Haaaaappy Koloss-Head-Munching-Day to you!

    Haaaaappy Koloss-Head-Munching-Day dear Brandon Sandersoooon

    Haaaaappy Koloss-Head-Munching-Day to yoooooou!

    (Happy birthday!)

    1. Chasmessian


      happy birthday Brandon!


  11. Happy Birthday Brandon!!


  12. Happy Koloss Head Munching Day!!

  13. Happy birthday, Brandon!

    Many happy returns.

  14. Hey, all. Brandon here. With the release of this book, there have been some minor updates to continuity that I think some of you will find relevant. The big one has to do with Hoid's visit to Terris in The Well of Ascension. For those unfamiliar with the backstory, this little behind-the-scenes action has been a source of some consistent problems. The outline, and original draft, of Well had Vin and Elend traveling up to Terris, then into the mountains, to find the Well itself. This was a huge momentum killer in the story. Having your cityscape-focused book suddenly turn into a traveling quest fantasy for a few chapters felt very out of place, and required too much strange time-jumping to make it work. In revisions, I set about finding a way to repair this, and to overlap the Well of Ascension discovery with Vin's return to Luthadel. The end result worked much better, but I was forced to cut Hoid's cameo. (In the form of footsteps in the snow and frost leading to the Well, hinting that someone had been there just before her.) I knew where Hoid was, and added in the cameo of him with the Terris people—with the plan still being that he visited the Well sometime during the days after Vin's return to the city. Well, in working on Secret History, I found that this had a problem with it. Hoid had to already know where the Well is, because after the destruction of the Pits, he'd need to use the Well to return to Scadrial after leaving in the middle of book one to attend to certain other events. If you've read the story, you know this is how I proceeded. Official continuity is that Hoid went up to Terris after visiting the Well, as he had things to do there. He did not go looking for the Well. This doesn't change continuity for any of the books, though it does render one of the annotations for Well obsolete. Otherwise, I'm quite pleased about this novella. I wasn't certain how it would go, writing something using threads I'd left dangling ten years ago. (You should thank the beta readers, who are all Sharders I believe, for their continuity help. They made me aware pf several things I needed to make much more clear from the original draft, so that canon would be more crisp.) I know there has been a lot of discussion regarding which times when someone appears to hear Kelsier's voice were actually Kelsier. The story offers the official canon for this as well. It's nice to finally be able to give the answers to some longtime fan questions, such as what spooked Vin during her inspection of Hoid and what was up with Preservation and the Mist Spirit. It's entirely possible that, despite our efforts, we slipped up and made some continuity error here or there. If so, I'm terribly sorry! This one has been particularly challenging to do. Thanks, as always, for reading.