VS Team Coding Conventions: Difference between revisions

From Vintage Story Wiki
no edit summary
No edit summary
Line 7: Line 7:
== [https://en.wikipedia.org/wiki/Separation_of_concerns SoC] - Separation of concerns ==
== [https://en.wikipedia.org/wiki/Separation_of_concerns SoC] - Separation of concerns ==


Thematically different code/configuration should be placed in different code structures. The game engine should not be concerned with game content - so they are, where practically possible, separated into their own mods. The code that defines the behavior of blocks should not be concerned with the configuration of that block, so the configuration is, where practically possible and meaningful, separated into json files.  
Thematically different code/configuration should be placed in different code structures. The game engine should not be concerned with game content - so they are, where practically possible, separated into their own mods. The code that defines the behavior of blocks should not be concerned with the configuration of that block, so the configuration is, where practically possible and meaningful, separated into json files. Animations, UVs, Models, Textures - none of them should be defined inside source code where practically possible.  


== Subdivide complexity ==
== Subdivide complexity ==
Confirmedusers, Bureaucrats, editor, Administrators
1,779

edits