Everyone’s comments weren’t exactly wrong, but they were pretty much useless. These were all just embellishments that couldn’t change the overall situation.

Moreover, some people only pointed out the problems—how to solve them? They didn’t know themselves.

Jason Foster was the project manager, having worked his way up from lead designer. He understood the current issues with the project better than most people present, but he was also at a loss.

If Jason Foster had a solution, he would have already assigned someone else to handle it. Why bother holding a brainstorming meeting?

Not getting any answers that really impressed him, Jason Foster felt a bit disappointed.

At this moment, Jason Foster noticed that William Carter, who was sitting by the door, hadn’t said a word.

Actually, Eric Turner hadn’t planned to let William Carter speak, since he’d only just joined a few days ago and wasn’t very familiar with the game. There was a good chance he’d miss the point and make a fool of himself.

But Jason Foster didn’t see it that way. He looked at William Carter: “Little William, why don’t you share your thoughts? Didn’t I ask you to try drafting the version plan for the next update? How’s that coming along?”

Brian Clark quickly chimed in, “Oh, Manager Foster, the version plan is part of William Carter’s work schedule for this week and next. He’s probably just gotten familiar with the game and hasn’t started on it yet…”

He glanced at William Carter again: “Um, I haven’t had a chance to mention this before, but even though our project doesn’t have strict rules, we still need to put in some overtime when there’s a lot of work. The project went live yesterday and you weren’t around—that’s not really appropriate…”

“We’ll talk about that later.” Jason Foster waved his hand, also a bit disappointed. “Since you haven’t had enough time to work on the version plan, just share whatever thoughts you have.”

Jason Foster had already heard from Brian Clark that William Carter always left work on time and was a newcomer, so he didn’t expect much—just wanted to hear something, anything.

Surely he could say something, right?

Everyone looked at William Carter, thinking this newbie was really unlucky, running into something like this just a few days in…

Judging by Brian Clark’s attitude, it was clear he had issues with William Carter, but in this setting, no one could really speak up for William Carter. After all, he was always the first to leave work, which many people didn’t see as a good thing.

Everyone waited for William Carter to speak.

“I think the main problem right now is that players have lost the sense of novelty in the gameplay itself. Without new players coming in, it’s hard to maintain the existing player base,” William Carter said calmly.

Brian Clark was a bit surprised—he hadn’t expected William Carter to actually hit the nail on the head.

But Brian Clark wasn’t worried, because most people were aware of this issue. The real question was, how do you fix it? That’s not something you can explain in a few words.

Brian Clark’s idea was to make new mechs and new features, but it seemed players weren’t interested anymore.

“Yeah, that’s right.” Jason Foster nodded. “So, do you have any ideas?”

William Carter said, “Create a new gameplay mode.”

“Oh? A new gameplay mode?” Jason Foster was intrigued. “Do you have any good ideas?”

Brian Clark sneered inwardly. Typical newbie—doesn’t know his limits!

Create a new gameplay mode? You think you can just say it and it’s done? If you could really do that, what would we need system designers for?

Taking charge of new features is something only designers with at least six months to a year of experience can handle. For major features, you need one to two years of experience.

As for William Carter’s suggestion to create a new gameplay mode to save the game? That would have to be a very complex mode, something that would take system designers a week or two just to design. What could a newcomer like William Carter possibly come up with?

Unfazed, William Carter said, “Actually, the new version plan is already finished.”

Manager Foster was pleasantly surprised. “Oh? It’s done? Send it over!”

Everyone else immediately looked at Brian Clark, who was instantly dumbfounded.

Just a moment ago, Brian Clark had said William Carter never worked overtime and hadn’t done any work. So what was this?

The new version plan was already finished?

William Carter had completed all of next week’s work in just two days??

Brian Clark felt his face burning. This William Carter was really stirring things up!

Chapter 14: New Version, Starsea Battlefield!

William Carter opened his virtual wristband, found the completed new version plan, and sent it directly to the design team’s group chat on the internal messaging app.

Jason Foster, as the manager, was also in the design group chat and immediately opened the new version plan.

Everyone else did the same, including Brian Clark, though their eyes were filled with disbelief and skepticism.

A fresh graduate, only on the job for a couple of days, managed to write a new version plan in such a short time?

How was that possible?

Jason Foster opened the new version plan and was pleasantly surprised at first glance—the table was very well-organized!

The new version plan was a big table with many different elements, such as new feature names, descriptions, feature details, breakdown of art resources, design, programming, art leads, estimated work hours, progress, and so on. Of course, the leads and work hours for each group weren’t filled in yet—those would be assigned and estimated after the features were finalized—but at least the format of the entire table was flawless.