ObsequiumMinaris
New member
- Joined
- Nov 7, 2022
- Messages
- 16
- Points
- 3
Thank you for the story!![]()
Newly Awakened Outer God Works as a Truck Driver
REWRITE V3 IS FINISHED! Ichiro Yamashita’s life is spectacularly 'ordinary'—until it isn’t. At 23, Ichiro has traded a burnout-inducing IT career for the open road, hauling cargo across Japan as a truck driver. The pay’s steady, the scenery’s decent, and if the worst thing he faces...www.scribblehub.com
Thanks in advance, I have one question about my first chapter. Did I did the infodump right? I would like to hear you answer!
Okay, so you asked about the infodump in the first chapter, so that's primarily what I'll be addressing here. I apologize in advance if I come as a bit forceful in this particular post - infodumps are something I feel strongly about in fiction. I'll explain why as we go, but if I'm a bit forceful here, that's why. It's nothing personal at all, and in fact I think the rest of your story has a very solid foundation to it, but that infodump is something I think I really need to address as directly as possible.
Let me begin by stating that I'm not a fan of infodumps in general. Doesn't matter what story they're in, I do not like them there. They are a distraction from what would otherwise be a great story. I keep harping on this point in most of my feedback because I think it's important to understand - you only get one chance to make a good first impression on the reader. You want your first chapter to be as attention-grabbing as possible because of that reason. It doesn't necessarily need to be action-packed, though that's generally a simple way to do it, but we need something there that catches the eye and makes it hard to look away. Ultimately, if the reader isn't hooked by the end of the first chapter, the only thing keeping them going at that point is inertia, and inertia runs out very quickly.
So, why am I not a fan of infodumps? Simple - because they generally don't really add anything that couldn't be added elsewhere in the story. You have an entire story to share this information with the reader - it doesn't have to happen right at the start. In fact, adding it at the start risks losing the reader's attention. And if your infodump is at the beginning of the story... that's not really a strong first impression. When you throw a whole bunch of information at the reader like this, especially at the start, there's little to no context for it - there's no engagement on their part because they don't have a reason to really care yet. since they don't know who anyone is or what's going on. You're basically asking them to do a bunch of reading and thinking and for them to get invested right at the start of your story, but you're not providing anything in return for their investment yet - basically, an infodump is not entertaining enough to justify the reader putting in the work to really learn what's going on with it. When the reader opens up a story and immediately sees a big infodump like this, the first thing that goes through their mind is something along the lines of "Why should I care?"
"Why should I care?" - this is probably the one phrase you do not want your reader to even consider thinking about at any point in your story, let alone the start. The moment it goes through their mind, they're done - the suspension of disbelief has been broken, and it's probably not going to come back, and that means they're probably not going to keep reading. Our job as authors of fiction is to entertain, first and foremost - if the reader finds themselves asking why they should even care in the first place, that's a very bad thing, because it means their engagement has dropped like a rock, and if they continue, they're only doing so out of inertia. They're far more likely to open the story, see a big infodump, and go look for something else that's easier to read.
That's why I don't like infodumps, particularly at the beginning of a story - they're one big neon-lit Las Vegas billboard that's basically just begging the reader to ask why they should care.
Please note that this is not limited to just your story in the slightest. In fact, I'd say this is true for all infodumps in pretty much any story. I legitimately do not think there is a good way to do an infodump in any story. These are the parts the audience is going to skim over at best, skip over at worst - don't write something the audience is just going to skip.
Okay, so we've established that infodumps can be counter-productive when it comes to capturing the reader's attention. So what's the fix for that? How do we make infodumps more compelling, and how do we keep the reader from losing engagement with the story while reading the infodump?
Remove it.
Yes, I'm serious. That's what I think the best possible suggestion is here. Not just for you, but for everyone who includes an infodump in their story. I don't care who you are or what story you're writing - that infodump is unnecessary and is distracting from the fact that the rest of your chapter is solid. Get rid of it. Don't give the reader an excuse to start skipping parts of your story, especially early on. I know it's not fun to have to go back and cut out a part of the story that you worked so hard on, but legitimately, I think any story that includes an infodump is better off with the infodump gone.
The rest of your chapter is very good - there are a few little nitpicks I have, but nothing really major. The problem is that the infodump distracts from all of them. If your reader's already started skimming or skipping parts of your story, then what's stopping them from doing the same to the rest of the chapter? After all, they're already asking the Four Deadly Words - at this point, they're looking for an excuse to stop reading. So we're not even going to put the thought into their heads - we're going to cut out that infodump entirely. It's just gone at this point. What does that leave us with? Surprisingly, pretty much the exact same content - the infodump, after all, is just backstory. And backstory is something that can and should be given throughout the entire story. You don't have to give it all to us right at the start - in fact, it's probably better that we go into it not knowing everything about the protagonist until later. I shouldn't need to know everything about your protagonist before getting to like them as a character. In fact, if I have to put in work like that to really appreciate their character, that's probably a bad thing because it means I'm not going to get attached to them as easily, and having to read through a big infodump definitely qualifies as asking the reader to do work on their part.
So, here's my suggestion: Cut out the infodump entirely. Start at the scene where the MC wakes up in the arena. Everything past that point, story-wise, is very good. The infodump is ultimately unnecessary - there's nothing in it that you can't tell us later in bite-sized chunks, and it's distracting from the fact that the rest of your first chapter is a solid start.
Again, I must reiterate - the issue isn't that your specific infodump is distracting from the rest of the story. The issue is that every infodump, as a general rule, is distracting from the rest of the story in which it's included. I legitimately do not believe there's a good way to write an infodump in any story, no matter how skilled of a writer the author may be. If you just start throwing names, descriptions, dates, etc. at the reader right at the start and expect them to not only keep track of it all but also care about it, their eyes are going to glaze over and they're going to skip it. And once the reader has started skipping parts of your story, there's nothing stopping them from skipping other parts. Your primary goal as a writer that's presumably trying to make it big enough to eventually monetize is not just to grow your audience, but also to retain that audience, and retention is very difficult once they've started skipping parts of your story. So with that in mind, don't give them an excuse to start doing so.
Final thoughts - I don't like infodumps in general, I think they take away from what would otherwise be an awesome story. Any story that includes an infodump is almost certainly better off just removing it and instead sprinkling the information it contained throughout the story in some other way that feels more natural.
Thank you again for the story, and I hope this feedback is able to help you in some way. And again, I must apologize pre-emptively if I came off as too forceful or direct in this review - I don't mean anything personally towards you or your story with regards to that, this is just a topic I feel very strongly about.