Chapter 307 Playing games? Mining!

"Oh my god, this is amazing!"

Guo Mo's eyes widened when he unexpectedly discovered that he could control the second Aba.

What's going on? Although these two Aba look exactly the same, but...but the character he plays is not this one!

When he looked back, it was broken.

Aba's real body, the protagonist Aba that he controlled at the beginning, is now out of control and starts to move freely.

"Don't go, hey!"

Without having time to think about why he could control Aba No. 2, Guo Mo quickly got up from the ground, got on the wheelchair and chased after the departing Aba No. 1.

We can’t let number one get away.

He hasn't figured out what the mechanism is yet. If Aba No. 1 runs away, will he be able to get it back later?

As a result, an extremely strange and funny scene appeared in the game. Two Abas who looked exactly the same, sitting in the same style of wheelchairs, were chasing each other on the street.

All the viewers who watched the live broadcast were grinning.

Wow! I've never seen anything like this before! This is the first time I've seen two wheelchair riders racing on the street.

The most important thing is that these two people not only look exactly the same, but their names are both Aba. When they appear in the same scene, no one can tell who is who.

It's the real Monkey King or the fake Monkey King! Just as Guo Mo was busy chasing after the real Aba and turning on the power of the electric wheelchair to the maximum, an unexpected person appeared on the screen.

"Another one?"

Seeing Aba with the same face walking slowly across the street, Guo Mo was really speechless.

So far, he has seen two Abas in the game, not counting the real body. If he counts it, there will be three.

broken!

The real or fake Monkey King is not enough to describe the current situation. Who knows how many Abas are hidden on such a huge map? "Even the shadow clones are not this awesome!"

With the appearance of the third Aba, Guo Mo was no longer interested in chasing the original body, because he was obviously more interested in Aba No. 3.

The same is true for the viewers in the live broadcast room.

Because both Aba himself and Aba No. 2 move around in wheelchairs, this is why everyone can't tell who is the real one and who is the fake one.

But everyone saw that Aba No. 3 who just flashed by was not in a wheelchair, but was walking like a normal person.

This is so weird!

Let’s not discuss for now the specific reasons why the game bug causes multiple duplicate buildings and NPCs to appear in the same scene.

The game he started with in this save file was "paralyzed in the lower limbs", so why did a protagonist named Aba appear with normal legs and could walk?

Hey, hey, hey! Where did you come from? ...

What happened in Guo Mo’s live broadcast room was quickly shared by netizens and spread to the Tianba community.

Tianba Studio also knew about it.

Chen Ba and Xiao Lu replicated the phenomenon as soon as possible, trying to find out the reasons and crux behind it.

"Obviously..."

“This bug is caused by a chain of bugs in the online mode.”

Xiao Lu analyzed: "Because in the game, in order to curb the value stacking bug, we set up a so-called upper limit lock."

When investigating game bugs, they discovered a serious bug in the online mode that could stack game values, so they made targeted modifications and adjustments.

But they forgot one thing.

To be precise, it's not that they forgot, but from the very beginning, the focus of the entire studio's testing and troubleshooting was not on the stand-alone mode.

This is also due to everyone's habitual thinking. After all, most of the bugs in the studio's games in the past were related to the online mode. Over time, everyone is used to focusing on the online mode.

No one expected that the problem this time was not in the online mode, but in the stand-alone story mode!

The "numerical stacking" bug in online mode also exists in stand-alone mode.

Then why wasn’t it discovered?

Of course, it is because, in stand-alone mode, there is only one player in the game, and the player only controls one character, so it does not constitute the prerequisite for triggering the bug.

Who would have thought that deleting the old save file and overwriting the new one in stand-alone mode could trigger a bug unique to online mode through the "save overwrite" mechanism? "In online mode, this bug causes the various values ​​of the game character to be superimposed, and eventually exceed the upper limit to form game features such as instant movement."

Xiao Lu continued, "In the stand-alone story mode, because there is no second player and there is an upper limit lock, the values ​​cannot be added..."

"What you mean is that it is not only the game values ​​that produce the superposition effect, but also the in-game scene modeling and game NPCs, etc.?" Chen Ba asked back.

“That’s right!”

"We did not find this in online mode, probably because in online mode, game data and calculations are all dependent on the server."

Xiao Lu said with a smile: "But in the single-player story mode, since the triggering node of this bug is that the new save file overwrites the old save file, it will cause the save file to fail to overwrite and the game file cannot be rewritten."

Under normal circumstances, the new archive will overwrite the old archive. Before overwriting, the game files of the old archive will be deleted, and then the new game files will be written to the hard disk.

However, during this "overwriting" process, the game overlay bug was triggered, causing the overlay instruction to become invalid, and the original "overwriting" became "overlay".

In other words.

The old archive that should have been deleted was retained in another form due to this bug and integrated into the new archive.

"But there is a prerequisite for this, that is, the new save and the old save must have the same start and the same protagonist, Aba."

This also explains why no one else was able to trigger the bug, but Guo Mo succeeded.

He got the "lower limb paralysis" start twice, which just met the prerequisite for the bug to be triggered. Without this prerequisite, the old save file will be deleted normally and cannot be retained.

"In our game, the codes representing the protagonists are different at different starts."

Chen Ba said thoughtfully: "Blind Aba is one string of code, and wheelchair Aba is another string of code. Only the same start can trigger it?"

“That’s right!”

Xiao Lu nodded. "As for the reason why Guo Mo triggered the bug for the first time and the map only doubled in size, but the second time it was triggered, the map became very large and many duplicate NPCs appeared, it's also very simple."

When the game was first designed, enough space and slots were reserved for subsequent updates. In other words, the game map was reserved for a "double-sized" preview mode from the beginning.

This is also for the convenience of subsequent updates.

After all, if a DLC is added later, causing the map to become larger, but because there was not enough space reserved before, the map cannot be scaled and previewed normally, and even the texture modeling cannot be rendered and loaded normally, wouldn’t that be a bad thing? The first time Guo Mo triggered the bug, the game was normal. After all, this is equivalent to the appearance after "an update".

But when the bug is triggered a second time, the superimposed game materials, texture modeling and game resources are so large that they exceed the pre-reserved slots, and the situation Guo Mo encountered will occur.

This is actually very common.

For example, in some games, when encountering lag or network fluctuations, you will be surprised to find that the number of points, gold coins, stamina, character attributes, etc. in the game have all become 9999999.

Another similar situation is when a computer malfunctions and the timestamp is reset to 1970.1.1.

This bug in "Abba's Story" is actually similar to the situation in other games where all values ​​suddenly become 99999.

However, because a "value limit lock" patch was applied during the testing phase, the values ​​in the game did not become 99999.

But what this bug adds up to is not just game values, but also all game data files such as modeling, textures, NPCs, etc.

This also results in that when the new save file overwrites the old save file, and the protagonist "Abba" of the two save files has the same start and the underlying code is exactly the same, the two save files will be merged together, the map will be expanded, and there will be duplication problems such as texture modeling.

After figuring out the cause of the problem, Chen Ba then asked: "Is there any way to solve this situation?"

There is no mistake in the poem, post, content, and read the book on 6, 9, and bar!

“Yes, but it’s very troublesome!”

Xiao Lu said with a headache: "To fix this bug, we need to change a lot of code, and most importantly, some of the code involved seems to be something that only you have the authority to change."

Chen Ba: “…”

We are back to the same place again, right? Thinking of this, he couldn't help but rub his brows and said, "Let's just ignore it for now. Anyway, from the current point of view, this bug has no serious impact other than making trouble."

This is a blessing in disguise! According to Guo Mo's live broadcast, the consequences of this bug, apart from the map expanding many times, NPCs appearing repeatedly, and the existence of multiple protagonists Aba, are not too serious.

That’s right!

As long as it does not affect the gaming experience, these are all minor matters. There is nothing you can do if this bug occurs, and it is still a stand-alone mode, so there is no need to take it to heart.

This is what Chen Ba thought and did.

Not only did he not respond, he even condoned players' behavior of spreading the bug in community forums and other places.

Out of sight, out of mind!

Anyway, it's a stand-alone mode, you can do whatever you want, let alone bugs. Even if you use a modifier or a cheat, and use cheat codes, as long as it's not too excessive, he can pretend not to see it.

Besides.

What's the point of using this bug? I think it's better to join the Wind Spirit Moon Shadow Sect. After all, it's really fun to open the modifier.

Just when Chen Ba thought that this incident was just a minor incident and would soon be over, not long after, a post published in the Tianba community once again aroused heated discussions among the players.

A netizen from Chengdu, while playing the game, found two other "Abbas" on the map due to curiosity.

He was very curious. Why was there only two lonely Abbas on such a large map when the same bug occurred?

"yes!"

Many players who saw this post, including Chen Ba himself, instantly realized the problem.

The number of Abbas is not constant?

Logically speaking, since everyone is stuck with the same bug, the number of "shadow clones" generated by the bug should be the same.

But in the actual game experience, many people have found that the number of Abbas is not consistent, some people have more, and some people have less.

Then, this netizen from Chengdu conducted some investigation and visits based on this question, and finally came to a conclusion.

The number of "Abbas" born due to the bug depends on the size of the game map after the bug and the amount of game resources.

The larger the map, the more game resources it contains, and the more "Abbas" will be born!

So the question is, what determines the size of the game map and the amount of game scene resources caused by this bug? "The answer is: computing power!"

"The higher the computer performance, the stronger the GPU and CPU computing power. Combined with the game algorithm, the larger the game map that can be obtained after the bug is fixed, the greater the amount of resources in the map scene."

This summary left everyone confused.

After all this trouble, it turns out that the reason why the number of "shadow clones" that appear when everyone encounters the bug is different is actually because of the different performance of their computers?

But this thing has...

Wait a minute! Just as Chen Ba was about to complain that this Rongcheng player had done a lot of useless work and that this research result was meaningless, a surprising idea suddenly popped up in his mind.

He looked at Xiao Lu, and it was obvious that Xiao Lu had made the same connection.

“That’s right!”

"The logic of this generation is actually the same as the virtual currency on the Internet that everyone is familiar with. And the most interesting thing is that when you open the game file and find Archive, open the abba file in text browsing mode, you will see a string of keys."

"Copy this key and add it to someone else's game file, guess what happens?"

"The answer is, your Aba was transferred to someone else's game!"

Chen Ba & Xiao Lu: "..."

What is going on? Isn't it a game they made? And the goal is to win the TGA annual award for charity games, how did it suddenly become like this? This seemingly insignificant game bug, combined with the game algorithm, can actually produce the same effect as "mining"?

Even more outrageous is...

Because the underlying codes of Tianba games are all created by the Tiehanhan system, the current level of human technology cannot crack it at all.

In other words, this thing, to some extent, really meets the standards of virtual currency.

The only difference is.

Other virtual currencies exist in an "abstract" digital form, but this "Aba Coin" is much more figurative.

You have a few Aba coins, open your game, and see how many "Aba" there are on the map.

At the end of the post, the Chengdu netizen also said that he did not know the specific algorithm of "The True Story of Aba", but from his actual operation, the output of "Aba" was gradually decreasing.

In other words, now is the best time!

As time goes by, it will become more and more difficult to create an Abba. Even if you use the most advanced graphics card and CPU to debug the game bug for a day, you may not be able to create an Abba...

(End of this chapter)