Strategy by Design
https://forums.wz2100.net/
No, they work in Windows, Mac, and Linux. The default Mac OS X package doesn't compress the game data into .wz files like Windows does, but it still loads external maps and mods from .wz files just fine.heatwave wrote:So apparently, .wz files are Windows only?
Hmm, search your HD for folders called "screendumps", "savegames", "maps", "multiplay", "music", and files, "config", "keymap.map" in that directory that has these folders, stick the new .wz maps in the maps folder.heatwave wrote:Ah, I see. So, if I were to unzip a .wz file (which I can't) I would find all the files displayed in my picture?
And Warzone is smart enough that it doesn't need you to unzip your .wz files. It reads the zipped files just fine. That makes sense.
Warzone still isn't recognizing my maps (even after a fresh install), whether I put them along with the bundled maps or in the maps folder in the Application Support file.
So, I guess adding custom maps on Mac OS X is broken? Where/how do you guys put/place your custom maps?
Also, I stumbled across a file inside Warzone with the extension .win32. Call me crazy, but that seems out of place on a Mac...
Hey Zarel, you could help me out here. I'm sure you could figure out the right place to put my .wz maps just by looking through Warzone's file structure, right? I'm pretty sure you can't run Warzone on a MacBook (unless you overclock the GMA) but if you could give me a definite answer as to where custom maps belong, and thing still don't work after I place them there, then I'd say there's a pretty good chance that all Mac users are having this problem.Zarel wrote:(MacBook, bought Jun 2008)
CPU: 2.1GHz Intel Core 2 Duo T8100
RAM: 2 GB
Video Card: Intel GMA X3100
OS: Mac OS X 10.5 Leopard / Windows XP Professional
The folder with those files/folders is called "Warzone 2.2", found in ~/Library/Application Support/. Placing .wz files in the maps folder like you said does nothing. Would a more recent .wz file be different than one from a few months ago?Hmm, search your HD for folders called "screendumps", "savegames", "maps", "multiplay", "music", and files, "config", "keymap.map" in that directory that has these folders, stick the new .wz maps in the maps folder.
Nope.heatwave wrote: The folder with those files/folders is called "Warzone 2.2", found in ~/Library/Application Support/. Placing .wz files in the maps folder like you said does nothing. Would a more recent .wz file be different than one from a few months ago?
Yes, custom maps belong in ~/Library/Application Support/Warzone 2100 2.2/maps/ (Just check the FAQ if you don't believe me). I just tested it on my MacBook, it doesn't work for me, either... One of us should file a bug. I nominate you.heatwave wrote:Hey Zarel, you could help me out here. I'm sure you could figure out the right place to put my .wz maps just by looking through Warzone's file structure, right? I'm pretty sure you can't run Warzone on a MacBook (unless you overclock the GMA) but if you could give me a definite answer as to where custom maps belong, and thing still don't work after I place them there, then I'd say there's a pretty good chance that all Mac users are having this problem.
Here, I've attached it. I can't see any information about maps at all.Buginator wrote:I wish we can get the --debug all --debugfile whatever.txt output from you, since that tells us where it is reading everything from, and we can check that way.
http://macapper.com/2007/03/08/the-term ... roduction/
Maybe that will help you on how to get what we need from within the terminal?
Well, when I tried to run Warzone on one of the Macbooks at school, it just sat there in the dock bouncing. must be something other than the graphics card or the processor. I'll have to try that again.Zarel wrote:And of course I can run Warzone on a MacBook - no overclocking required. It makes the MacBook pretty loud, but it works. Come on, Warzone isn't that resource intensive. -_-
I beg to differ, the debug info DOES give clues.heatwave wrote:So we've agreed that adding custom Maps on a Mac is broken. I'll start a ticket if you'd like. Too bad the debug info doesn't have any clues.
Well, when I tried to run Warzone on one of the Macbooks at school, it just sat there in the dock bouncing. must be something other than the graphics card or the processor. I'll have to try that again.
Code: Select all
never |09:52:16: [removeSubdirs] removeSubdirs: Examining subdir: [2c-c3col100.wz]You'll have to remember - there are a whole bunch of different laptops called the "MacBook". Your school may have a significantly older one than the one I have.heatwave wrote:Well, when I tried to run Warzone on one of the Macbooks at school, it just sat there in the dock bouncing. must be something other than the graphics card or the processor. I'll have to try that again.
Both these logs are from debug mode builds, or release mode builds? In either case, can you stick in 1 map.wz file in the maps directory, and then do the logs again?Vermithrax wrote:I'm late to this thread, so let me sum up a few things.
1) In order to use custom maps on a Mac, the .wz file should be copied into the /maps directory. This is located in <user name>/Library/Application Support/Warzone 2100 2.2/maps
2) Unfortunately, this only seems to work in code compiled in debug mode. In order to get that, you need to download the source code and compile it. Running --debug all --debugfile whatever.txt from the command line does not count.
3) Fortunately, there is a work-around. Take your .wz file and rename it to a .zip file. Then you can extract the folder inside, and copy it into the location above.
4) Unfortunately, this has only been tested in single player mode. I haven't been able to see what happens in multiplayer.
5) A debug file of what happens when attempting to use the file 4c-river_canyon.wz is attached.
Edited to add...
The second debug file is what happens when I've extracted the maps from the .wz files.