Chapter 275 What a Shit Mountain Code!

Gu Fan continued to explain: "When entering the game and choosing a profession, the system will not only force players to have a basic attack skill for the profession, but will also give players a 'professional tag' in the background. This professional tag is not very related to the underlying code, but in some special cases, the relevant functions will detect this tag.

"For example, when players find a trainer to learn skills.

"But the problem now is... because of the unique mechanism of the boss Nefalor, the player is also given a professional tag! This has led to the original double restrictions in the game being broken!"

Lilith's brain was a little overloaded: "Wait a minute! Why does Nefalor give players a professional tag? Explain it clearly!"

Gu Fan sighed softly: "This has to start with the naming mechanism of Nefalor in the third stage.

"It can be seen that the 'naming' mechanism is a unique mechanism that the producer thought of when designing the boss Nefalor. It can even be said that it was made for this dish of vinegar.

"But as the final boss in the first raid, Nefalor was designed earlier than the major class changes.

"So at the beginning, Nefalor could not directly name the class. Because at that time, players did not have a class.

"In order to achieve the effect of naming, the producer designed the mechanism so that 'Nefalor will name the player according to the skills he used last time.'

"For example, the last player who used a shield attack skill on him will give up using a shield; the last player who used a totem to damage him will insert various totems to buff him in turn.

"This mechanism can cause certain difficulties for players, but it also provides players with enough countermeasures: as long as the player learns a specific, insignificant skill in advance and touches the boss before naming, he can deceive the boss and crack this mechanism.

"And this is the gameplay that the original producer allowed and even encouraged.

"But later, the profession settings were changed, so Nefalor's mechanism must also be modified to some extent. After some minor repairs by the original producer, a somewhat annoying problem was discovered, that is, when calling out professions, some bizarre bugs often occurred, causing the game to crash.

"For example, the original design was that the last player who had used the shield slam skill on the boss would give up using the shield; but now the shield slam has become a skill that both warriors and knights have, and the paladin corresponds to other named effects, which must be removed.

"For example, the original design was that players who used the sheep transformation skill to control the monsters in the group would use the sheep transformation skill on random teammates after being named.

"This design also has a unique design intention. It encourages players not to use the sheep transformation skill in the previous development process. Although it will greatly increase the difficulty when fighting monsters, it will reduce a team-destroying skill when fighting the final boss.

"For players, this adds a tactic and trade-off."

"But now it is divided by profession, so it can only be changed to "name the mage player to use the sheep transformation on teammates", but the problem is that many mage players have never used the sheep transformation. It is even possible that they have not learned the sheep transformation, which will cause the system to miss the judgment when judging the mage player through the sheep transformation skill.

"In addition, there may be some extreme special cases, such as the boss reading the skill but reading the wrong player tag. Although the probability of this situation is extremely low, program bugs cannot be said to be zero. As long as there are many players, problems with low probability will eventually appear.

"In order to solve these problems, especially to solve the missed judgment, the original producer made another patch, that is, when Nefarol calls out, the player's last attack skill against him will be prioritized.

"And in order to avoid possible bugs in the game later, when calling the roll, if the skill and the occupation label conflict, the skill will prevail, and the system will give the player the corresponding occupation label by default again in the background to prevent contradictions and bugs caused by reading the wrong player label.

"In this way, at least when players fight the boss Nefalor, they will not get errors and cause the game to crash due to problems with the roll call and occupation.

"Then when the player goes offline, the system will clear the player's occupation label again, and it will return to the starting point the next time it goes online.

"Just didn't expect...some players happened to be online, and went to talk to the trainers of other professions. "

Lilith was almost dumbfounded.

What a pile of shitty code!

The original design is one situation, the modified design is another situation, and in order to make the modified design run normally, the programmers pasted another layer of code on it. Although the original designed function was barely completed on the surface, who knows how this function was implemented in detail!

Take Nefalor as an example. The original design was originally good, but because of the modification of "professional setting", the original design had to be adjusted, and this adjustment would cause bugs. In order to fix the bugs, more bugs were caused...

Obviously, in the process of challenging Nefalor, the player not only deceived Nefalor, but also messed up the system.

The original design is to release the naming effect through player skills. It is related to too many underlying codes, so it cannot be changed. If it is changed, there may be big problems.

On the surface, it is naming professions, but in fact it is still naming skills.

The named skill may conflict with the profession code added later. In this case, we can only take the named skill as the standard and force the player to be given an additional profession code to make the function run smoothly.

At least, the game will not report errors, crash or have similar serious consequences during the group dungeon.

After the player goes offline, clean up these extra messes.

Unexpectedly, after layers of modifications, the code barely runs, but it has a bigger loophole.

This led to the player accidentally bypassing the two restrictions of "skills" and "professional tags" and unlocking the skills and talents of other professions!

And this unlocking can no longer be stopped.

As long as the player learns the skills of any profession, then according to the system function, he will be labeled with the corresponding system tag by default. This system tag is not unique, and multiple can exist at the same time.

Therefore, there are so many "all-professional players"...

Lilith felt that her brain was about to explode. The complexity of this problem was far beyond her imagination.

The key is that this explanation is really reasonable!

It's well-reasoned, and even the cause and effect are clear.

"But, Gu Fan! Why didn't we fix this legacy problem?" Lilith asked angrily.

Gu Fan was shocked: "Boss Li, listen to what you are saying!

"How can we have the time!

"Since we bought the game, we have been developing new features non-stop, including two other large group books, as well as the comprehensive replacement of art resources, and various bug fixes for the game...

"The malicious bugs have only been barely fixed, how can we delve into this seemingly normal function?

"To find this vulnerability, it requires a lot of testing, and I don't even know how deep we have to dig in the original shit mountain code. Do you think our development time is enough?

"Of course, if you are willing to give us one or two years of development time, we can overturn and redo this game.

"But back to the original question, Boss Li, didn't you decide to buy the game "Demon World Dispute" to save time?

"Overthrow the underlying code and rewrite it, what's the point of buying it? "

Lilith was stunned. What Gu Fan said made a lot of sense and she couldn't refute it at all!

Why did "Shadow World" have problems?

Because "Demon World Conflict" itself is a semi-finished product, the functions have been greatly changed, and there are all kinds of strange little bugs.

It was Lilith's decision to buy "Demon World Conflict". She had to take over in order to meet the deadline.

Strictly speaking, the development efficiency of the team of Against Heaven is already terrible. In such a short period of time, not only did they develop two new group books, but they also completed a series of work such as game optimization and system repair.

Currently, "Demon World Conflict" 》There was only one bug, and no malicious bugs such as game crashes, repeated errors, huge gold-brushing loopholes, etc. This is already a miracle.

If it were another game company, they would have opened champagne long ago.

Where can you find a top programmer of this level?

But Lilith was upset because of this.

If it was really a bug such as game crashes, repeated errors, and gold-brushing loopholes, she would feel better. After all, it would discourage players and generate a lot of negative emotions.

But now this bug not only did not discourage players, but made them happy!