When I write a bug it becomes the core gameplay.

Chapter 275 What shit mountain code!
Gu Fan continued to explain: "The first time you enter the game and choose a profession, the system will not only give the player a basic attack skill of this profession, but also give the player a 'professional label' in the background. This professional label is related to The underlying code doesn't have much to do with it, but in some special cases, related functions will detect this tag.

“For example, when a player goes to a trainer to learn skills.

"But the problem now is... because the unique mechanism of the boss Nefalor also gives players professional labels! This has caused the double restrictions in the original game to be broken!"

Lilith's brain was a little overloaded: "Wait a minute! Why does Nephalor give players professional labels? Please explain clearly!"

Gu Fan sighed softly: "This starts with the roll call mechanism of Nephalor's third stage.

"It can be seen that the "roll call" mechanism is a unique mechanism that the producer thought of when designing the boss Nephalor. It can even be said that it was made just for this dish of vinegar.

“But Nephalor, as the final boss in the first raid, was designed earlier than the major career changes.

"So at the beginning, Nephalor couldn't directly name professions. Because at that time, players didn't have professions yet.

“In order to complete the roll call effect, the producer designed the mechanism so that ‘Nephalol will roll call based on the last skill the player released on him’.

"For example, the last player who used shield-blow skills on him will give up using his shield; the last player who used totems to cause damage to him will insert various totems to buff him.

"But then the career setting was changed, so Nephalor's mechanism must also be modified to some extent. After some minor repairs, the original producer discovered a somewhat annoying problem, which was the naming of professions. Sometimes, some bizarre BUGs often appear, causing the game to crash.

"And in order to avoid possible bugs in the future of the game, if skills conflict with career labels during roll call, the skills will prevail, and the corresponding career labels will be given to the player by default in the background of the system to prevent the player from reading the wrong one. Player tags are inconsistent and lead to bugs.

Obviously, in the process of challenging Nephalor, the player not only deceived Nephalor, but also confused the system.

“In this way, at least when players fight the boss Nephalor, they won’t get errors or game crashes due to roll call and career issues.

Lilith was almost dumbfounded.

“This adds another tactic and trade-off for players.

"In addition, there may be some extreme special situations, 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 0. As long as there are many players, No matter how unlikely the problem is, it will eventually occur.

“This design also has a unique design intention. It encourages players not to use Sheep Transformation in the previous process of opening up the wasteland. Although it will greatly increase the difficulty when fighting mobs, it will lose a group-killing skill when fighting the final boss.

"This mechanism can cause certain difficulties for players, but it actually also provides players with sufficient countermeasures: as long as the player learns a specific, insignificant skill in advance and touches the boss before taking the roll, the boss can be deceived. , crack this mechanism.

"For example, the original design was that the player who had used the shield bash skill against the boss would give up using the shield; but now shield bash has become a skill for both warriors and knights, and the paladin corresponds to other roll call effects. It must be taken out.

"I just didn't expect...that some players happened to be offline and went to talk to trainers from other professions."

“And this is what the original producers allowed and even encouraged.

"In order to solve these problems, especially in order to solve the situation of missed judgments, the original producer made another patch, that is, when Nephalor calls his name, the player's last attack skill against him will be judged first.

"But now it's divided by profession, and it can only be changed to 'name the mage player to use the Sheep Transformation Technique on his teammates.' But the problem is that many mage players have never used the Sheep Transformation Technique at all. They may not even have learned the Sheep Transformation Technique. This is This will cause the system to miss judgments when judging mage players through the Sheep Transformation skill.

“For another example, the original design was that players who had used the Sheep Transformation Technique to control mobs in the raid would release the Sheep Transformation Technique to random teammates after being named.

What kind of ultimate sparse code is this?
The original design is one situation, and the modified design is another situation. In order to make the modified design run normally, the programmer added a layer of code on it, although on the surface it barely completed the original design. Function, but the devil knows how this function is implemented!
Take Nephalor as an example. The original design was very good, but because of the modification of "Professional Settings", the original design had to be adjusted, and this adjustment would cause bugs. In order to fix the bugs, Causing more bugs...

"Then after the player goes offline, the system will clean up the player's professional tag again, and it will return to the starting point next time he goes online.

The roll call effect is released through player skills. This is the original design, and it is related to too many underlying codes, so it cannot be changed. If it is changed, big problems may occur.

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

The roll call skill may conflict with the occupation code added later. In this case, the roll call skill can only be used as the criterion and an additional occupation code is forcibly given to the player to allow the function to run smoothly. At least it prevents players from having the game report an error, crash, or have similar serious consequences during the group play process.

After the player goes offline, clean up the extra mess.

Unexpectedly, after layer upon layer of modifications, although the code barely ran, it created even bigger loopholes.

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

But this unlocking can no longer be stopped.

As long as the player learns the skills of any profession, he will be given the corresponding system label by default according to the system functions. This system label is not unique, and multiple ones can exist at the same time.

That’s why there are so many “full-professional players” appearing...

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

The point is, this explanation is really reasonable!
It's well-founded and even the cause and effect are clear.

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

Gu Fan was shocked: "Mr. Li, listen to what you are saying!
"How do we have this time?

“Since the game was purchased, we have been developing new features non-stop, including two additional large-scale raids, a comprehensive replacement of art resources, and various bug fixes for the game...

"Vicious bugs are just barely corrected, so how can we possibly delve into this seemingly normal function?

“To find this vulnerability, it will require a lot of testing, and we don’t even know how deep we have to dig into the original shit mountain code. Do you think our development time is enough?

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

"But back to the original question, Mr. Li, didn't you decide to buy the game "Clash of Demons" just to save time?
"If the underlying code is overturned and rewritten, what's the point of buying it?"

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

What went wrong with World of Shadows?

Because "Disputes in the Demon Realm" itself is a semi-finished product, its functions have been greatly improved, and there are all kinds of weird little bugs.

But buying "Disputes in the Demon Realm" was originally Lilith's decision. She had to be the successor in order to meet the deadline.

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

At present, there is only such a bug in "Clash of Demons", and there are no vicious bugs such as game crashes, repeated error reports, huge gold grinding loopholes, etc. This is already a miracle.

If it were any other game company, they would have opened the champagne long ago.

Where can I find top programmers of this level?
But this is where Lilith feels uncomfortable.

If there were really bugs such as game crashes, repeated error reports, gold farming loopholes, etc., she would actually feel better. After all, dissuading players to quit can also generate a lot of negative emotions.

But now this bug not only does not dissuade players, but also makes them happy!

(End of this chapter)