TL;DR: This is not a guide. This is the story of a specific Saturday — March 22nd, 2026 — when Logan and I played Minecraft together for ten hours straight on the family Realm. We built a basalt ridge fortress on the edge of a soul sand valley, fought our way through two Bastion Remnants, lost a shulker box of stuff to a Magma Cube swarm, found it again, ate three meals at the desk, and finished the day with a working glowstone-powered front gate that took me an embarrassing amount of time to wire. The piece is about what made the day actually work — the moment I almost intervened during a frustration spike and chose not to, the food breaks, the silence in the middle that I did not break, and the fact that we did not get to half of what we planned. I think a lot about this Saturday. Not because anything dramatic happened. Because nothing dramatic happened. We just played, all day, and at the end of it Logan said "that was really good" and went to bed. This is the long version of why that mattered.
I want to start with the night before, because that is when I made the only decision that really mattered.
It was Friday. I had just finished a brutal week. Logan was upstairs doing homework. Stephanie was at her sister's. I sat on the couch and did the thing parents of one kid do, where you imagine the next day's schedule and try to find a slot for everything. The yard work. The grocery run. The two hours I had told myself I would spend on the laptop catching up.
And I thought: what if I did not do any of that.
What if tomorrow was just ten hours of Minecraft with Logan, and that was the whole day. No errands. No "we will play after I finish this." No half-attention. Just: open the laptop, log onto the Realm, play until dinner.
I did not announce it. I just texted Stephanie that I was taking the day off everything, set my phone to do-not-disturb, and went to bed.
This is the story of what happened.
Section 1: 8:30 AM — the start
Logan came down at 8:15 in the same hoodie he had worn the day before, hair flat on one side, asking what was for breakfast. I had already made coffee. I told him I was going to be on the Realm all day if he wanted to play.
His face did the small surprised thing it does. He asked if I meant all day all day.
I said yeah, all day all day.
He said okay and went to get his iPad.
By 8:45 we were both logged into the family Realm. He was at his desk in his room. I was at the kitchen island on my laptop. We could hear each other through the open doors but we were not in the same physical space. This is the configuration that has worked best for us — close enough to talk easily, separate enough that we are not two people sharing one screen.
The first hour was him showing me what he had been doing on the Realm during the week. Some scaffolding around a project he had not finished. A new room in the base. A villager he had named Kevin. Kevin was a leatherworker. Logan was very pleased with this, for reasons that did not need explaining.
I made a second coffee. We started planning the day.
Section 2: The plan we made and how it went wrong
Our morning plan, as written in the in-game book Logan keeps for these things:
- Build a fortress on the basalt ridge near the soul sand valley.
- Loot one Bastion Remnant for gold and pigsteps.
- Fight a Wither Skeleton or two for skulls.
- Come back, finish the front gate of the fortress.
- Optional stretch goal: start a wither summon at sunset.
This was, in retrospect, two days of work compressed into one. I knew that. I did not say so. The plan looked great on paper. We started.
By 11 AM we had the fortress framed in. Basalt walls, a flat blackstone roof, two side towers, a bridge over a ravine that Logan was inordinately proud of. The bridge had taken us about forty-five minutes and was the moment in the morning where I realized he had gotten significantly better at building since the last time we played seriously together. He was placing blocks with intention. He was undoing things that did not look right and rebuilding them. He was also, importantly, making the bridge look the way he wanted it to look, not the way I would have made it.
I noticed myself, during the bridge, almost stepping in to suggest a different railing pattern. I did not. He finished it. It looked exactly like a bridge an eleven-year-old would build, in the best possible way.
Lunch was sandwiches at 12:30. We ate at the kitchen island, both of us a little glassy-eyed from screen. I did not check my phone. Logan asked if we could keep going after lunch. I said yes.
Section 3: 1 PM to 3 PM — the bastion run
The Bastion Remnant we picked was about four hundred blocks from our base, in a basalt delta I had scouted on a previous solo trip. I knew it had a hoglin-stable structure and a likely treasure room. I also knew it had at least three Brutes, which are the one Nether mob I genuinely respect.
Logan in netherite, me in netherite, both with full prep — fire resistance, golden carrots, Strength II. We walked in.
The first half of the run went well. We cleared the outer Piglins. We avoided the Brutes by sneaking around the perimeter. Logan found the treasure chest first, opened it with his back to me — I heard him say "yo" in a voice that was higher than his usual voice — and pulled out a pair of pigstep music disc fragments and an enchanted netherite scrap.
The second half went badly. A Magma Cube swarm spawned in the lower passage we had not cleared. Logan was carrying his backup shulker box at the time. He took two cube-hits in quick succession, panicked, sprinted in the wrong direction, fell off a ledge, and dropped the shulker box into a half-lava channel about twenty blocks below.
He did not say anything for about three seconds.
This was the moment. This is the moment the article is about, actually. The moment I almost said something.
What I almost said was something like: "It is okay. We can get it back. We have time. We can build a path down. Don't worry."
What I said instead, in a tone I tried very hard to keep level: nothing.
I waited.
After about ten seconds, Logan said: "I think I can get to it."
I said: "Yeah. I think so too."
He did. He pillared down with cobblestone, killed two more cubes on the way, swam into the half-lava channel with fire resistance, and recovered the shulker box. The whole salvage operation took him about eleven minutes. I watched. I did not coach. He came back up with everything he had dropped, plus three new pieces of nether gold he had picked up on the way.
When he got back to me he was breathing differently. He said "okay, that was scary." I said "yeah."
We went home.
Section 4: 3 PM to 5 PM — the front gate
The original plan said the front gate of the fortress was a one-hour project. The original plan was wrong.
The gate I had sketched on paper that morning involved a glowstone-powered redstone circuit that opened a piston-driven door when a player stepped on a hidden pressure plate inside the courtyard. It also closed automatically after a delay. It also lit up the surrounding torch wall when activated. It was, in retrospect, the kind of redstone project that takes me about three hours when I am alone and attentive.
We had two hours. We had been playing for six. I was tired. Logan was tired in a different way — wired-tired, the over-stimulated edge of tired that kids get to.
We started the wiring. I made a mistake on the first pass — placed a repeater facing the wrong direction, which I did not notice for about ten minutes. The signal was not propagating. Logan saw it before I did. He pointed at the repeater and said "is that supposed to be facing the other way."
I checked. He was right. I rotated it.
The gate started working in pieces. Pressure plate fired the signal. Signal propagated through the wall. Pistons fired. Door opened. Lights came on.
But the closing-after-delay part was wrong. The door was closing immediately, before you had time to walk through it. We needed a longer delay. I put more repeaters in series. The door closed slower but the lights stayed on too long. Logan suggested a comparator. I said comparators do not really work for that. He said "are you sure" and showed me, on the in-game book, that he had already drafted the circuit using a comparator on his Bastion-loot trip.
He had been thinking about this independently. He had a working solution. I did not.
I stepped back. He wired the comparator path. It worked. The gate behaved correctly. The lights faded out at the right time. The door closed at the right time. The pressure plate had a one-tick visual delay that he liked, so we left it in.
This took us until about 5:30. The gate was finished. I ate a granola bar at my desk and felt, briefly, like the kid had outpaced me at something I used to be better at than him. Then I stopped feeling that, because that is not a useful feeling. I told him the gate was good.
He said "thanks dad" in a voice that did not need anything else added to it.
Section 5: Dinner and the half-finished evening
Stephanie came home at 6:00. We had pasta. Logan told her about the bridge, the Magma Cubes, the dropped shulker box, the recovered shulker box, the gate, the comparator. He talked for about twenty minutes straight. She asked questions. I ate.
After dinner the plan had said: optional Wither summon. We did not do it. Logan was tired and so was I, and the Wither fight is its own afternoon (see The Wither Fight as a Family Event for why we never compress that into a tired evening). We logged back in for an hour, did some basic sorting in the storage room, made a backup of the Realm, and called it.
We did not get to:
- The Wither summon (deferred to a future Saturday).
- The second Bastion run we had vaguely planned (deferred indefinitely).
- The redstone-driven flower farm I had wanted to start (forgotten about until I drafted this article, which is honestly fine).
This is, I think, the part of the day that most accurately describes what a successful ten-hour Saturday actually looks like: about sixty percent of the plan happens. Forty percent gets cut, deferred, or replaced with something better that came up in the moment. The salvage of the shulker box was not in the plan and it was the most important moment of the day. The comparator-driven gate timing was not in the plan and it was the second-most.
The plan was the scaffold. The actual day was what happened in and around it.
Section 6: What I think made it work
I do not want this article to turn into a list of takeaways. The whole point is that the day worked because of what was not formalized.
But there are a few specific things, from my position as the parent who was there:
The pre-commitment the night before. Deciding the day was for this one thing — and not telling anyone, including Logan — meant that when 11 AM came and the bridge was taking longer than I had pictured, there was no internal voice saying "well, I had been planning to mow the lawn." There was no competing schedule. The day was just for this.
Phone in another room. I do not always do this. I did this Saturday. It mattered.
Same building, separate desks. Logan does not actually want me looking over his shoulder. He wants me available, in the same air, but with my own thing to do on my own screen. This is, I think, the right configuration for an eleven-year-old. It will be different at fourteen. (See Why Your Kid Hyperfocuses on Minecraft and What to Do With That for the longer version of this thinking.)
Three meals at the table. Breakfast, lunch, dinner, all at the actual table, all without screens. The day was ten hours of Minecraft framed by three meals of being a family. The framing matters more than the duration.
The not-intervening moment. When Logan dropped the shulker box, the most important parenting move I made all day was the one where I said nothing for ten seconds. That silence let him solve it. If I had filled the silence, I would have solved it for him, and the day would have been a different — worse — day.
The fact that we did not finish. A ten-hour Saturday does not need to finish the plan. It just needs to be a real day of play together. We left things on the table. They are still on the table. We will get to them.
Common mistakes
- Trying to compress two days of game-plan into one. The plan should be ambitious enough to be interesting, modest enough that you can finish about sixty percent. We picked roughly the right scale; it could have been smaller.
- Filling the silence after a frustration spike. The kid's recovery from frustration is the lesson. Your verbal intervention takes the lesson away. Wait. (See A Field Guide to Nether Boredom for the related conversation about not over-narrating the kid's experience.)
- Skipping meals at the table. The screen sessions are bookended by family meals, or the day blurs into one long screen.
- Letting your own fatigue at hour eight bleed into the kid's experience. I almost did this with the gate. Step away, eat the granola bar, come back. Do not let "I am tired" turn into "you should be done."
- Making the day about you and the kid being friends. This is a parenting day, not a friendship day. The kid still needs the parent in the room. Same-room presence, not peer-level participation.
- Announcing the day ahead of time. I did not tell Logan the day was reserved for this until 8:30 the morning of. The pre-commitment was for me, not for him. If I had announced it Friday night, the morning would have started with expectations and the expectations would have flattened it.
A closing thought
I think a lot about this Saturday.
Not because it was unusual. It was not. We have had probably six days like it in the last two years. And not because anything dramatic happened — the dramatic moments of the day were small, and only one of them (the silence after the dropped shulker box) felt important even at the time.
I think about it because of what Logan said when he went to bed.
He said: "that was really good."
He did not say it in a moment of high emotion. He said it the way an eleven-year-old says something they actually mean, which is offhand, on the way out of the room, half over his shoulder. He said it and then went and brushed his teeth. The whole exchange took about two seconds.
What I knew, in that two seconds, was that he had felt the day. He had felt the not-intervening, the same-room presence, the family meals. He had felt that I had given him the day. He had felt that we had built a bridge together that he had designed. He had felt the moment of dropping the shulker box and the moment of recovering it. He had felt that I trusted him to figure out the comparator.
He had felt all of it, and he had named it with three words on the way to brush his teeth.
The reason I write Nethercon is, in part, this. The Saturday articles do not need to be common. They need to happen sometimes. The day spent fully present with one kid, doing one thing, with no other competing call on your attention — this is one of the rarer and more valuable things a parent can offer.
The Minecraft is the medium. The day is the gift.
Pair this guide with How to Run a Family Minecraft Realm Without Losing Your Mind and Why Your Kid Hyperfocuses on Minecraft and What to Do With That and A Field Guide to Nether Boredom.
Listen to the audio version above. Send corrections to [email protected] — we read everything.
← BACK TO NETHER WASTES