[SOLVED] What must be in the pk3 order to run the map?

Hi,
I've made a map in netradiant and exported as a .bsp file. Then i put the .map file and the .bsp file in a zip-archive and unnamed to .pk3, but nothing happens. And i never made a map before. Which Files i have to put in the .pk3-archive to?
Sry for my bad english
Thanks for an help

I don't remember and someone will probably answer this shortly, but you can download a random map, unzip it and then simply look how they placed all files. Note that its the root directory that needs to be zipped, sometimes if you zip the map folder itself it creates an redundant folder.

I don't remember and someone will probably answer this shortly, but you can download a random map, unzip it and then simply look how they placed all files. Note that its the root directory that needs to be zipped, sometimes if you zip the map folder itself it creates an redundant folder.

Thx for the answer

Create a folder called "maps", put the bsp and map file into it and zip that folder. That was missing.
Looking at other pk3s is good. You should also include a mapinfo (txt file) file (see in other pk3s) and a picture of your map. Just needs a screenshot with the same name like bsp (mymap. jpg). You can remove the HUD etc. with r_letterbox 1 to get a good picture.

Create a folder called "maps", put the bsp and map file into it and zip that folder. That was missing.
Looking at other pk3s is good. You should also include a mapinfo (txt file) file (see in other pk3s) and a picture of your map. Just needs a screenshot with the same name like bsp (mymap. jpg). You can remove the HUD etc. with r_letterbox 1 to get a good picture.

Thanks

And post your map here in the forums

For clarity, here's the summary (for other newbies like me):

Assuming you are making a map called "test". A useable test.pk3 package should have at least the following files:

Code:

maps/test.bsp
maps/test.jpg
maps/test.mapinfo

It is highly recommend to also include these files:

Code:

maps/test.map
maps/test.readme.txt

Explanation:

• The location and name of the files are specific.
  
• maps/test.bsp is the compiled map
  
• maps/test.jpg (or maps/test.png) is a screenshot of your map, that shows in the map selection screen in the game
  
• maps/test.mapinfo contains map description and game setting
  
• maps/test.map is the source of your map, that can be opened with NetRadiant
  
• maps/test.readem.txt (the name and location is not standardized, but this is not a bad practice) has additional information (license, contact info, URL for future updates, references, acknowledgement, etc.)
  

The other things you may want to plan ahead is the versioning and naming of your files. That's a whole other discussion, but basically, you want to include your version info somewhere -- some just rename their package as "test_1c.pk3", and still has maps/test.* as the content. Some change names of both the pk3 and the contents.

It's highly recommend that you have a single release location for your map (and include that URL in your readme file). Using the forum to be that page, as Mirio suggested, is a good practice.

For clarity, here's the summary (for other newbies like me):

Assuming you are making a map called "test". A useable test.pk3 package should have at least the following files:

Code:

maps/test.bsp
maps/test.jpg
maps/test.mapinfo

It is highly recommend to also include these files:

Code:

maps/test.map
maps/test.readme.txt

Explanation:

• The location and name of the files are specific.
  
• maps/test.bsp is the compiled map
  
• maps/test.jpg (or maps/test.png) is a screenshot of your map, that shows in the map selection screen in the game
  
• maps/test.mapinfo contains map description and game setting
  
• maps/test.map is the source of your map, that can be opened with NetRadiant
  
• maps/test.readem.txt (the name and location is not standardized, but this is not a bad practice) has additional information (license, contact info, URL for future updates, references, acknowledgement, etc.)
  

The other things you may want to plan ahead is the versioning and naming of your files. That's a whole other discussion, but basically, you want to include your version info somewhere -- some just rename their package as "test_1c.pk3", and still has maps/test.* as the content. Some change names of both the pk3 and the contents.

It's highly recommend that you have a single release location for your map (and include that URL in your readme file). Using the forum to be that page, as Mirio suggested, is a good practice.

Thanks.
Now my lolfisch.mapinfo file looks like this

Code:

title Lolfisch    

author Brot

gametype dm
gametype tdm

but nothing happens then i've written gametype cts. And now i can play the map in cts but not in dm or tdm

add the line "has weapons"

Also you can add tdm, kh, ka, ft and ca as they don't need some point of extra support

EDIT: Didn't realize Mirio already answered. What he said.

but nothing happens then i've written gametype cts. And now i can play the map in cts but not in dm or tdm

Try this

Code:

title Lolfisch    
description Medium-sized, fast enclosed map supporting multiple gamemodes.
author Brot

has weapons

gametype ctf
gametype dm
gametype tdm

I'm assuming you have the right entities for DM and CTF (info_player_*, item_flag_*, etc.) in your map.

Please always add description.

You may want to remove "[SOLVED]" in the title when you still have questions.

but nothing happens then i've written gametype cts. And now i can play the map in cts but not in dm or tdm

Try this

Code:

title Lolfisch    
description Medium-sized, fast enclosed map supporting multiple gamemodes.
author Brot

has weapons

gametype ctf
gametype dm
gametype tdm

I'm assuming you have the right entities for DM and CTF (info_player_*, item_flag_*, etc.) in your map.

Please always add description.

You may want to remove "[SOLVED]" in the title when you still have questions.

Thank you so much