The skeleton came apart wrong.

  Not wrong in the way skeletons were supposed to come apart — the way the first three had, crumbling into pale blue motes that drifted upward and dissolved before they reached the vaulted ceiling. That was designed. That was deliberate. Someone had spent real time calibrating the exact drift speed of those particles, the way they caught the torchlight, the half-second of visual silence after a kill that let you feel the weight of it. Good design. Clean.

  This one came apart wrong because the woman hit it so hard that the dissolution sequence couldn't keep up with the physics.

  Sara — he'd caught the name during Voss's introductions, hadn't retained much else beyond the posture and the way she'd tested her avatar's range of motion with the methodical precision of someone calibrating a machine she intended to use hard — had found the skeleton's timing window on her second exchange. Two feints to map the aggro pattern, a sidestep that used exactly the corridor width available to her, and then a strike from an angle the skeleton's tracking couldn't compensate for fast enough. The impact sound was deeply satisfying in a way that Zane suspected had been the subject of at least three internal meetings. The skeleton staggered. Sara hit it again before it recovered, same angle, because she'd already determined the angle worked and she was not, apparently, someone who experimented when executing.

  The bones flew apart. The blue motes tried to catch up. For a flickering half-second, the skeleton existed in two visual states simultaneously — physically scattered and digitally dissolving — and the effect was like watching a rendering engine have a polite argument with itself.

  Zane filed this away. Not the kill. The seam.

  He'd been doing this since they loaded in.

  Not the fighting — he was adequate at the fighting, had contributed a reasonable number of hits to the collective skeleton problem, had not embarrassed himself with the shortsword in any way that felt worth examining. The fighting was fine. The fighting was what you were supposed to be paying attention to.

  Zane was paying attention to the walls.

  Not because he didn't care about the skeletons. Because the walls were more interesting. The stonework in the tutorial chamber was deliberately imperfect — chisel marks placed at irregular intervals, mortar lines that varied in width, the specific kind of simulated age that required someone, or something, to have thought carefully about how stone looked after centuries of weight and weather and quiet. It was beautiful work. It was also slightly different on the left side of the chamber than on the right.

  The left wall had been designed by a human. He was almost certain of this. The imperfections had the quality of intentional roughness — an artist's idea of what old stone should look like, informed by reference material and aesthetic instinct. It was excellent. It would fool anyone who wasn't looking for seams.

  The right wall had been designed by something else.

  The imperfections on the right were not aesthetic. They were statistical. The variation in the mortar lines followed a distribution pattern that was too even to be handmade and too irregular to be a simple texture tile. Something had studied what real stone walls looked like — not pictures of stone walls, but the underlying mathematics of how stone aged — and had generated these surfaces from first principles. The chisel marks weren't placed for visual effect. They were placed because that was where chisel marks would actually be, given the grain direction of the stone and the angle of approach a medieval mason would have used.

  The right wall was better. It was better in a way that most people would never notice and that Zane could not stop noticing.

  He'd mentioned it to Voss during a lull between skeleton waves. Just a casual observation — hey, the environmental rendering changes partway through the room, is that intentional? Voss had glanced at the wall, glanced back at Zane, and said something careful about iterative development processes and asset pipelines. Then he'd looked at the wall again, longer this time, and hadn't said anything else.

  Find this and other great novels on the author's preferred platform. Support original creators!

  Zane had filed that away too.

  The fourth wave was bigger.

  Five skeletons instead of three, entering through the archways on both sides of the chamber in a pattern that was clearly designed to split the party's attention. Voss called it out — flanking approach, watch the sides — in the slightly winded tone of someone who was simultaneously fighting and narrating and trying to remember what the encounter was supposed to do versus what it was actually doing.

  Luke was already moving. The EMT had a way of being in the right position before the situation fully developed, the spatial awareness of someone whose job required reading a room in the time it took to cross it. He'd placed himself at the left archway, shortsword up, stance low, and the first skeleton through the gap ran into him like it had hit a professional disagreement.

  Raj was at the other archway, and if his technique was less practiced than Luke's, his enthusiasm was making up the difference. He'd figured out something about the timing — the skeletons had a recovery window after each swing that was consistent enough to exploit — and he was working it with the careful, repeating attention of someone who had found a system and intended to understand it completely before he trusted it.

  Sara was everywhere. Not recklessly — there was nothing reckless about the way she moved, every action was deliberate and economical — but she had a radius that was larger than anyone else's, a willingness to cover ground that came from somewhere deeper than the game's mechanics.

  Zane was at the back. This was, he told himself, tactical. Someone needed to watch the full picture. Someone needed to be the person who noticed things.

  What he noticed was the door.

  Not the main archways. Those were open, permanent, part of the chamber's designed geometry. This was different — a heavy wooden door set into the far wall, partially concealed behind a collapsed stone column. The kind of thing you wouldn't see if you were busy fighting skeletons. The kind of thing you would see if you were the person at the back, watching the walls instead of the fight.

  It was closed. Iron-banded. Old, or designed to look old, but with hinges that sat in their brackets with the particular precision of something that was meant to move.

  Zane glanced at the fight. Still in progress. Luke and Raj had the archways controlled. Sara was cleaning up a skeleton that had gotten past the initial line and was doing so with a level of efficiency that suggested she'd already mentally moved on to the next thing.

  He crossed to the door.

  Up close, it was heavy — he could tell from the construction, the thickness of the planks, the depth of the iron banding. Built to hold. Built to close and stay closed. He ran his fingers along the frame and felt the slight gap where the door met the stone, felt the air moving through it — cooler air, with a different quality, the particular stillness of a space that hadn't been entered.

  The hinges were functional. The door opened inward, toward whatever was on the other side. Which meant it closed outward, toward the chamber.

  Toward anything standing in front of it.

  He didn't open it. He didn't need to. He just needed to know it was there, and how it worked, and what eight hundred pounds of iron-banded oak would do to something that wasn't expecting it.

  He filed this away with everything else. The walls. The seam. The rendering glitch when Sara hit the skeleton too hard. The door and its hinges and the weight of it and the direction it swung.

  The dungeon was talking. Most of it was talking in a language called atmosphere and set dressing and immersive environmental storytelling.

  Some of it was talking in a language called engineering.

  Zane was listening to both.

  A sound rolled through the chamber — not a skeleton sound, not the clatter of bone on stone. Something deeper. A resonance that came from the floor itself, as if something beneath them had shifted its weight. The torches along the walls flickered in unison, then burned lower, amber shading toward red.

  Voss looked up from the skeleton he'd been ineffectually poking at with his staff. The expression on his face was new. Not the slightly harried competence of a developer walking testers through content. Something closer to recognition. Something closer to pride.

  "Okay," he said, and the room got quieter around the word. "That would be the boss."

  At the far end of the tutorial chamber, the largest archway — the one none of them had been through yet, the one that had been dark and still since they loaded in — began to glow. A cold luminescence, blue-white, rising from the floor like something waking up.

  The Hollow Warden emerged from the light. It was barely larger than a man and it moved like someone's first attempt at a scary skeleton, which should have been funny and wasn't, because the haptic feedback translated its presence into something the body understood before the mind caught up — a wrongness in the air, a weight, the particular quality of attention that came from something old turning to look at you.

  Zane stood by the door. His hand rested on the iron banding. He was thinking about hinges.

  He was thinking about weight.

  He was thinking about the fact that the Warden had to come through a space to reach them, and that spaces could be shaped, and that shaping spaces was just engineering with different materials.

  The Warden's empty eyes swept the room. The temperature dropped four degrees.

  The tutorial's final exam had arrived.