Editing ZK Map Making Guide
Jump to navigation
Jump to search
Warning: You are not logged in. Your IP address will be publicly visible if you make any edits. If you log in or create an account, your edits will be attributed to your username, along with other benefits.
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 28: | Line 28: | ||
For a 10x10 (TitanDuel-size) map, create the following images with a tool of your choice: | For a 10x10 (TitanDuel-size) map, create the following images with a tool of your choice: | ||
− | * A height map grayscale image with dimensions 641 x 641, saved as an 8-bit | + | * A height map grayscale image with dimensions 641 x 641, saved as an 8-bit .bmp or a 16-bit .png. (The latter is preferred but not all tools offer 16-bit output.) The brighter a pixel is the higher the corresponding part of the map will be. |
− | * A texture map colour image with dimensions 5120 x 5120, saved as a | + | * A texture map colour image with dimensions 5120 x 5120, saved as a .bmp |
For a different size map, multiply the height/width of the map by 64 and add 1 to get the right size for the heightmap; multiply the height/width of the map by 512 to get the right size for the texture map. | For a different size map, multiply the height/width of the map by 64 and add 1 to get the right size for the heightmap; multiply the height/width of the map by 512 to get the right size for the texture map. | ||
Line 110: | Line 110: | ||
* Something on the server has gone wrong. AFTER testing your map locally and finding that it works there, contact an admin. Uploading your map to a file-sharing service so the admin can look at it may help. | * Something on the server has gone wrong. AFTER testing your map locally and finding that it works there, contact an admin. Uploading your map to a file-sharing service so the admin can look at it may help. | ||
− | === | + | === Uploading to Springfiles for use in other Spring communities === |
− | + | The old Springfiles website is defunct and has been replaced by https://springfiles.springrts.com/?type=0 | |
+ | |||
+ | Somebody who knows how the upload process works now should fill this in. Should hopefully be simpler than old Springfiles though. | ||
= Skeleton Of A Map = | = Skeleton Of A Map = | ||
Line 136: | Line 138: | ||
== SpringMapEdit == | == SpringMapEdit == | ||
− | + | === Installation === | |
+ | [https://springfiles.com/spring/development/spring-map-edit Springfiles page] | ||
== Nobiax Texture Pack == | == Nobiax Texture Pack == | ||
Line 157: | Line 160: | ||
* Press Alt-M again to disable the widget and print a list of metal points to the infolog | * Press Alt-M again to disable the widget and print a list of metal points to the infolog | ||
− | Then open your infolog. | + | Then open your infolog.lua (in the main zero-k directory) after you exit to retrieve the startbox information for copying into map_metal_layout.lua. Check that the metal point values for each mex point are as you want them to be. It's probably a good idea to turn the widget off after you are done with it. |
== Upspring == | == Upspring == | ||
Line 169: | Line 172: | ||
This method of placing features requires you to have some s11n gadgets in /LuaRules/Gadgets and some s11n and lcs stuff in the /libs/ folder. If your map doesn't have these then get them from the blueprint or some other map. | This method of placing features requires you to have some s11n gadgets in /LuaRules/Gadgets and some s11n and lcs stuff in the /libs/ folder. If your map doesn't have these then get them from the blueprint or some other map. | ||
− | * Put the files defining the features you want in your map file. This includes a definition in the /features subdirectory, model files in the /objects3d directory, and textures in the /unittextures directory. The easiest way to get these is to borrow them from existing maps | + | * Put the files defining the features you want in your map file. This includes a definition in the /features subdirectory, model files in the /objects3d directory, and textures in the /unittextures directory. The easiest way to get these is to borrow them from existing maps. There is a features library as well... ask around in #zkmap for a link then update this page. |
* Load your map in Springboard | * Load your map in Springboard | ||
* Delete any features you have marking mex locations, otherwise you will end up with two copies of them and that is bad. | * Delete any features you have marking mex locations, otherwise you will end up with two copies of them and that is bad. | ||
Line 205: | Line 208: | ||
Good luck... I'm not sure anybody has come up with an entirely bug-free implementation of this yet. Banana Republic might be your best bet for a reference. | Good luck... I'm not sure anybody has come up with an entirely bug-free implementation of this yet. Banana Republic might be your best bet for a reference. | ||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
{{Navbox manual}} [[Category: Development]] | {{Navbox manual}} [[Category: Development]] |