Salted Fish’s Self-help Strategy

There are three situations in this book that make me relatively bald. The first is the content that I think the readers may not like, so I speed up the past, and the result is ridiculed by the crowd, and the readers are quite welcome.

The second is the content that I think is not bad, but it was collectively boycotted.

The third kind is a plot similar to this paragraph. I know it is boring and the reading experience is indeed a bit worse, but I have to write, because the pursuit of this book is largely based on the existing technical and social resources. Let's imagine some modes that are still vacant. For example, the PVP combat mode of "Wu Dao Fajun".

The readers may feel that I have a chapter, but this kind of content is actually very laborious, more laborious than driving, and writing is very slow. I have seen some people say that writing games and writing so finely is the word count. I rely on this word count and I will lose money... The most suitable thing for me to write word count is the exploration of the business model, and how to brag, that is quick to write... …

Because, I need to repeatedly deduct the implementation logic of the game many times, and then confirm that such a mechanism can be made by programmers and can be implemented as a product. The key is to do a thought experiment. In the actual development process, many effects are made by the programmer in full according to the needs of the planning plan, but the effect is completely different, because there are many places game designers did not expect, but the program is cold, and it is on any design model. Defects will be manifested.

As far as the physical collision distance I wrote, it is not complete. The more boring logical argumentation process has been deleted. That is, both sides of the battle must first define three states: attack, standby, and defense. It appears that one party is being beaten by fat and suddenly turned into an attack state. Then, when side A starts to attack, side B checks whether it is in the standby state at the same time. If so, both sides enter the mobile state at the same time. The direction of movement is a random angle from the direction of A to B. The relative distance remains unchanged, and B enters defense.

After A's attack, B counterattacks, so that the visual performance of the fierce battle between the two sides will appear. These are all written out and become a thesis, in fact I have deleted most of them. And we have to consider the trade-offs from the developer's perspective, not from the author's perspective alone. For example, this mechanism abandons the posture of death and cannot attack at the same time. From the developer's point of view, the development of the first online version must be based on stability and balance between the playability of functions and the time to go online.

So even if you can add the mechanism of the same death, such as judging the kill line by the defender's blood volume, and the special mechanism of the kill line; or just pursuing a visual effect of an end-game state, both sides attack at the same time, which is more gorgeous and powerful. But in terms of functional rationality, the logic of this implementation has become super complicated, so general developers dare not do this except for glass **** that has the right to infinitely bounce tickets. I would rather develop a stable and playable version first, and then slowly iterate the product after it goes online.

Otherwise, this very high-end function is made with a very poor price/performance ratio, and the performance is indeed very good, but after it went online, the effort was wasted. The key is that the rush to the street may be caused by other factors, even operating and issuing factors, this function is impeccable, and died of non-war crime. Experienced developers must balance development costs and risks, no matter how rich the company is.

These thoughts cannot be written in the book, because it is really explanatory.

So this third article is what I'm most entangled in. Let's not write it at all. The readability of this book has indeed increased, but it is no different from other people's articles. It is only interesting but not wise. Write too much, you must be scolded.

For example, the difference between the forced displacement caused by the skill and the active displacement caused by the collision volume and the conflict handling in the implementation, etc., should be the content that most readers do not care about, but it reflects my stance Contempt for chop. And the 1v1 battle is still standing output, the visual performance is particularly boring, what should I do?

So after losing a few precious hairs, it was written like this...

By the way, I really grew up looking at the book "The Resurrection of China in Another Time", and it is estimated that many new readers have never heard of it. This is the first novel in the entire history of online novels to be sold on the shelves for VIP sales. Before that, there was no paid reading, and there was no concept of so-called genuine. It belongs to the XXX level in history.

Then, Chief Yang, he, opened a new book... The title of the book is "Rebirth: Pretend to be a Smart Man". Rebirth went back to 1979. Looking at the introduction is a bit like "Leaping Thirty Years" as a rebirth of the country.

https://

Please remember the domain name of this book's first publication:. Apex novel mobile version reading URL: