This is not a BUG, this is a game feature

"Go ahead, this is awesome!"

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

What's going on?

Although the two Abbas look exactly the same,...but the character he plays is not this one!

When he looked back, he saw it was broken.

Aba's identity, the protagonist he initially controlled, is now out of control and begins to move freely.

"Don't go, hey!"

Before he had time to think about why he could control Aba No. 2, Guo Mo quickly got up from the ground, got into a wheelchair and chased after the departing Aba No. 1.

We can't let No. 1 escape.

He hasn't figured out what the mechanism is yet. If Abba No. 1 escapes, can he get it back later?

As a result, an extremely weird and funny scene appeared in the game. Two Abba's who looked exactly the same were chasing each other on the street in the same style of wheelchair.

All the water friends who watched this live broadcast were smiling.

Good guy!

What a long time to see you! This is the first time in my life that I have seen two wheelchair warriors racing on the street.

The most important thing is that not only do these two people look exactly the same, they are both named Aba. They appear in the same scene and no one can tell who is who.

Belongs to the real and fake Monkey King!

Just when Guo Mo was busy chasing Abba and turning the power of the electric wheelchair to the maximum, another unexpected character appeared on the screen.

"Another one?"

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

So far, he has seen two Abbas in the game, not counting the main body. If so, there would be three.

broken!

The real and fake Monkey King are not enough to describe the current situation. Who knows how many Abbas are hidden on such a huge map?

"The shadow clones aren't even that awesome!"

After the third Abba appeared, Guo Mo was no longer interested in chasing the main body, because he was now obviously more interested in Abba No. 3.

The same is true for water friends in the live broadcast room.

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

But everyone saw Abba No. 3 who just passed by. He was not in a wheelchair, but walked like a normal person.

This is so strange!

Let’s not discuss the specific reasons why game bugs cause multiple duplicate buildings and NPCs to appear in the same scene.

His save file starts with "paralysis of the lower limbs". Why is there a protagonist named Abba who has normal legs and can walk?

Hey Hey hey!

Where did you come from?

…

What happened in Guo Mo's live broadcast room quickly spread to the Tianba community through the spread and sharing of water friends.

Tianba Studio also knows.

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

"obviously……"

"This bug is caused by the chain of numerical superposition bugs in the online mode."

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

When troubleshooting game bugs, they found that there was a vicious bug in the online mode that could superimpose game values, so they made targeted modifications and adjustments.

But they forgot one thing.

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

This is also caused by everyone's inertial thinking. After all, bugs in the studio's games in the past were mostly related to the online mode. Over time, everyone has become accustomed to focusing on the online mode.

No one thought that the problem this time was not the online mode, but the single-player story mode!

The "numeric superposition" bug in online mode also exists in stand-alone mode.

So why wasn't it discovered?

Of course, this is because in single-player mode, there is only one player in the game, and the player controls only one character, so there is no prerequisite for triggering the bug.

Who would have thought that when deleting old saves and overwriting new saves in stand-alone mode, the "save overwriting" mechanism could trigger a bug unique to online mode?

"In online mode, this bug will cause the various values ​​of the game character to be superimposed, and eventually exceed the upper limit, resulting in game features such as teleportation."

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

"You mean, it's not just game values ​​that produce superposition effects, but also in-game scene modeling, game NPCs, etc.?" Chen Ba asked rhetorically.

"That's right!"

"We did not find this in the online mode. It may be because in the online mode, the game data and computing levels all rely on the server."

Xiao Lu couldn't laugh or cry: "But in the single-player story mode, because the trigger node of this bug is the new archive overwriting the old archive, it will cause the archive overwrite to fail, and the game file cannot be rewritten, etc."

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

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

In other words.

The old archives that should have been deleted were retained in another form under the influence of this bug and integrated into the new archives.

"But this also has a premise, that is, the new archive and the old archive must have the same start and the same protagonist Aba."

This also explains why others failed to trigger the bug, but Guo Mo succeeded.

Both times he got the start of "paralysis of the lower limbs", which just met the prerequisites for triggering the bug. Without this precondition, old archives will be deleted normally and cannot be retained.

"In our game, different starts have different codes representing the protagonist."

Chen Ba thought thoughtfully: "The blind Abba is a string of codes, and the wheelchair Abba is another string of codes. Can it only be triggered by the same start?"

"That's right!"

Xiao Lu nodded: "As for the first time Guo Mo triggered the bug, the map only doubled in size. The second time it was triggered, the map became very large, and the reason for the emergence of many duplicate NPCs is also very simple. "

At the beginning of the game design, sufficient space and pits will be left for subsequent updates. In other words, the game map has a "double size" preview mode reserved from the beginning.

This is also for the convenience of subsequent updates.

After all, if a DLC is added later and the map becomes larger, but because there is not enough space reserved before, the map cannot be zoomed and previewed normally, and even the texture modeling cannot be rendered and loaded normally, wouldn't that be a bad thing?

Guo Mo triggered this bug for the first time and everything in the game was normal. After all, this is equivalent to what it will look like after "one round of updates".

But when the bug is triggered for the second time, the superimposed game materials, texture modeling and game resources are too large and have exceeded the pits left in advance, which will lead to the situation Guo Mo encountered.

This is actually very common.

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

There is also a similar situation when the computer fails and the timestamp is reset back to 1970.1.1.

This bug in "Abba" is actually similar to other games where the values ​​suddenly change to 99999.

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

But this bug is superimposed on not only game values, but also all game data files such as modeling, textures, NPCs, etc. in the game.

This also leads to the fact that when the new archive overwrites the old archive, and the protagonist "Abba" of the two archives has the same start, and the underlying code is exactly the same, the two archives will be merged together, the map will be expanded, and the texture will be modeled. Waiting for repeat question.

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

"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, it seems that only you have the permission to change some of the codes involved."

Chen Ba: "..."

It's come around again, right?

Thinking of this, he couldn't help but rub his eyebrows: "Then don't worry about it for now. Anyway, from the current point of view, this bug has no too bad impact other than fixing the problem."

This can be considered a blessing among misfortunes!

According to Guo Mo's live broadcast content, the consequences of this bug are not big problems except that the map is expanded many times, NPCs appear repeatedly, and multiple protagonists Abba exist at the same time.

That's right!

As long as it doesn't affect the game experience, these are minor things. You can't do anything with this bug, and it's still a stand-alone mode, so there's no need to take it to heart.

This is what Chen Ba thought and did.

Not only did he fail to react, he even allowed players to spread the bug in community forums and other places.

Out of sight!

Anyway, it's a stand-alone mode, you can create whatever you want, let alone bugs, even if you turn on the modifier and cheat device, he can pretend that he didn't see any cheat codes as long as you don't go too far.

Moreover.

What’s the use of this bug? It feels better to join the Wind Spirit Moon Shadow Sect. It is really refreshing to turn on the modifier.

Just when Chen Ba thought that this turmoil was just a small fight and was about to end, not long after, a post was posted on the Tianba community, which once again aroused heated discussion among the players.

A netizen from Chengdu, while playing a game, got stuck on a bug out of curiosity and found two other "Abba" on the map.

He was curious, why were there only two solitary Aba on a map as big as his own when the same bug was stuck?

"yes!"

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

Isn't the number of Abba constant?

It stands to reason that since everyone is stuck with the same bug, the number of "shadow clones" produced due to the bug should be the same.

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

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

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

The larger the map, the greater the amount of game resources contained in the map scene, and the more "Abba" 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 performance of the computer, the stronger the computing power of the GPU and CPU. Combined with the game algorithm, the larger the game map that can be obtained after the bug is stuck, and the greater the amount of resources in the map scene."

This summary made everyone confused.

After working on it for a long time, everyone found out that the number of "shadow clones" that are stuck out of a bug is inconsistent. Is it actually because the performance of their computers is different?

But this thing has...

Wait a minute!

Chen Ba, who was just about to complain that this Chengdu player had done a lot of useless work and that the research results were meaningless, suddenly had an astonishing idea pop up in his mind.

He looked at Xiao Lu, and it was obvious that Xiao Lu also thought of it.

"That's right!"

"This generation logic is actually consistent with the Internet virtual currency that everyone is familiar with, and the most ridiculous thing is that if you open the game file and find Archive, open the abba file in text browsing mode, you will see a series of keys."

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

"The answer is that your Abba has been transferred to someone else's game!"

Chen Ba \u0026 Xiao Lu: "..."

What's going on?

Isn’t what they are making a game? And the goal is to go for the TGA annual award for a charity game, why did it suddenly become like this?

This seemingly inconspicuous game bug, combined with the game algorithm, can actually produce the same effect of "mining"?

What’s even more outrageous is…

Because the underlying code of the Tianba game comes from Tiehanhan System, it is impossible to crack it with the current level of human technology.

In other words, to a certain extent, this thing really meets the standards that a virtual currency should have.

The only difference is.

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

How many Abba coins do you have? Just open your game and see how many "Abba" there are on the map. That's it.

At the end of the post, this Rongcheng netizen also said that he did not know the specific algorithm of "Abba", but judging from his actual operation, the output quantity of "Abba" is gradually declining.

In other words, now is the perfect time!

As time goes by, the birth of Abba will only become more and more difficult in the future. Even if you use the highest-end graphics card and CPU to block game bugs for a day, you may not be able to create an Abba...