Editing Repository Reference/Naming conventions
Warning: You are not logged in.
Your IP address will be recorded in this page's edit history.The edit can be undone.
Please check the comparison below to verify that this is what you want to do, and then save the changes below to finish undoing the edit.
| Latest revision | Your text | ||
| Line 1: | Line 1: | ||
{{navigation title|Building a Game}} | {{navigation title|Building a Game}} | ||
| − | |||
Naming conventions are required to keep repository clean and easy to work with. There is some files violating common rules, making them first candidates for the renaming. | Naming conventions are required to keep repository clean and easy to work with. There is some files violating common rules, making them first candidates for the renaming. | ||
| Line 6: | Line 5: | ||
==Texture names== | ==Texture names== | ||
| − | Texture name should be one or two words explaining what this texture is for. | + | Texture name should be one or two words explaining what this texture is for. Special textures (normalmaps, glowmaps etc.) should have suffix according to skinframe rules (see [[texture]]) |
| − | + | If texture is a part of some group, use the following template for naming: '''texturename<group_number>_<texture_number>''' | |
| − | + | ||
| − | + | ||
| − | + | ||
Example: | Example: | ||
| Line 71: | Line 67: | ||
* '''World''' | * '''World''' | ||
** '''Location''' | ** '''Location''' | ||
| − | *** '''Sub-location''' | + | *** '''Sub-location''' |
| − | Name template: | + | Name template: |
| − | + | '''w'''[''worldnum'']'''m'''[''locationnum'']'''''-'''''[''location_name'']'''-'''[''sub-location_name''] | |
| − | If sub-location is grouped (there is several crypts, caves etc.) first one | + | If sub-location is grouped (there is several crypts, caves etc.) first one doesnt contain 1. |
Examples: | Examples: | ||
| Line 96: | Line 92: | ||
{{navigation footer|}} | {{navigation footer|}} | ||
| − | |||
