Viewpoint: about the planning, design and implementation of the game system.
1. Most of the picture of the game software is directly written. Its maximum benefit is that the platform is independent, not considering the complicated Window interface specification, do not consider a lot of API or MFC related to the interface. On these unnecessary platform features, the designer can be very freely architectural game interface system and the form of expression. If you use the current mainstream OOD design, the design level of designers after the experience can be greatly improved. Therefore, the game system design is very suitable for learning software design cases. 2. If you want to find a series of modes to summarize the game system design system to form a unique engineering law, it is actually unnecessary. From the perspective of the software system, the game software system and ordinary application are the same, its kernel is data, this data describes a state, which is the current state of the entire software system. The game is in operation, the application software is also controlled, the essence of these phenomena is the development and update of the system state ---- Data is changing and updated. What is triggered by the state (data), is a unique software law, that is, each software has different system status update laws (such as user input, event trigger, system behavior or state development), and this It is the so-called system law. Each application has its own system law, and each game software has its own system law, and this is the basis for software system design, it needs to be abstract, planned, packaged. Therefore, you can take the game software system with other other software systems, they are as simple or complex. ^ _ ^ Supplement: In fact, many game systems can be summarized, such as elves management, map management, and more. I think these are all local design and algorithms, have not yet to the height of the system law. 3. About the architecture software system, especially in an object-oriented manner.
I briefly talk about some of my experience: #. Try to make the software demand detailed and complete in advance. #. First plan the entire system from globally. Especially to consider variables and system reuse, scalability. #. The function and distribution of the module of the system is then constructed. Note that relatively stable system states and system regularities and system changes, abstract changes and links will be packaged, making changes in a certain aspect of the system can be independent. MVC / View / Control mode is a simple and typical example, and 3 can be developed independently and reuse. For the examples of your appearance, the act of monsters and the behavior between the monsters, the former describes the appearance of the object, the latter may describe the interaction between the objects - there may be variables here. If the interactive action between monsters (such as "bite") (can construct a PacmanAction class that identifies the Pacman class), so that it is independently developed with the monster itself, believes that the changes in the system will be much flexible, such as you can Fill in various behaviors such as Talk, Kiss or FakeDead ^ _ ^, etc., without having to modify the Pacman class or class level, let these movements are freely combined with the appearance behavior of the monsters, and believe that their music is endless. Abstract changes will be packaged. After the block diagram, it will refine its details, and the communication between the class's inheritance system and the class must be very clear. After some exquisite part, it is believed that the current system will be very Reasonable, elegant and energy. #. Then ... probably being happy or painful, anyway, it is physical activation ~~ The benefit is you can also chat with MM. * _ * #. Then it is painful debugging L, but I believe that there is a systematic system, all behaviors and changes are very clear, you can also chat with multiple MMs. : J Architecture, some views are more abstract, I hope everyone can correct it. % _ #
