http://www.battlefieldsingleplayer.com/ … ppack1.zip

Just extract into a temp folder on your computer and then copy the map files into your First strike\levels folders.

languerie's Outpost Hoth.  Each mode (16, 32, 48, 64) has a different layout and vehicles:   Snowspeeders vs ATST, snowspeeder vs Ties, ATST vs infantry, and infantry only.   Nice conversion of the Imp fortress into a Hoth outpost.

languerie's Carbone Hill - Its an infantry only fight across a mountain pass.    Fun scrappy map with lots of crevices to hide behind.

languerie's Carbone Island - Imperial forces have landed on a beach after a pitched battle and brought an ATST.  Can the rebel forces defend themselves?

languerie' s Research in Anchorhead -  Back to the desert, but this time the Imperials have firehawks.   Nice looking map with an orange sky at dusk.  Instead of capturing CPs, your capturing droids.

Tatoone Mos Espa Night  (laguerie)- A nice night version of the daytime map.

Bloodgulch -  Port of the BF2142 map my Jones.   Speederbikes and ATPTs make for a very challeging battle in this small map.  16 player is infantry only and 32 player is with vehicles.

this is my first map and it needs work in parts and none of the objects spawners have been placed(mostlly becuse I can't find the dish turrets). but here are some pics.

command posts:

imperial command:

central wall:

south wall:

east wall:

central fort:

eastern fort:

north wall:

rebel outpost:

canyon:

It will be a work in progress as more questions are asked and more information is released.

Ok, to start with you should know that any change to files will affect your online game play. For this reason it is essential you create a copy of the First Strike folder. To do this:

1) Navigate to your 2142 installation folder, for example C:program files/electronic arts/BF2142/mods/FirstStrike. Notice that it is inside your 2142 folder, specifically the area titled MODS!

2) Copy the FirstStrike folder from inside mods. Yup, the whole thing. Just right click, ctrl C whatever your preferred method and copy that whole folder to your desktop.

3) Ok, so you should now have two folders, one regular FirstStrike in the original destination folder, and your copy one on the desktop. Now, rename that one on the desktop. Just keep it simple, I usually just add a letter on the end, for example FirstStrikeM (m for mine or mod) but you go ahead and use whatever you want.

4) Now, grab that renamed folder and go drop it back in the 2142 mods folder, you know, the same place you copied it from. Now in the Electronic arts/mods folder you should have: BF2142, FirstStrike and FirstStrikeM or whatever you renamed it.

** Because the idea here is that we swap between FirstStrike folders, it becomes very easy for mistakes to happen and for the wrong one to be modified. I reccomend that you keep a seperate copy of FirstStrike on your desktop. Its easier to drop in a copy of it when something goes wrong than have to reinstall the whole mod every time!**

5) When you modify a file, it is done from inside FirstStrikeM (or whatever you called it). When you want to play it and check out your changes you need to rename both FirstStrike folders. What????!! It's easy, basically what you do is use the regular FirstStrike launcher to play either version, BUT, it always looks for the folder named First Strike.

So lets say I made some changes and want to check them out. I rename FirstStrike (which is my regular public folder remember) to FirstStrikeP (P for public!). I then rename my mod folder (remember, FirstStrikeM the one we copied) to FirstStrike. This is why I just use a one letter rename method, its so much easier! Then, just use th elauncher as normal and it will fire up your version. Remember though, your changes wont let you join a server cause you will get kicked.

When you want to play online with folks again, just rename them back, so FirstStrike in this case becomes FirstStrikeM and FirstStrikeP becomes FirstStrike.

EASY!!

Next lesson will be an introduction to the mod file system.
After that, some basic changes you can do such as weapon tweaks, change number of bots, vehicle tweaks and the one everyone wants.....changing kits on maps.

Remember, this is just a guide, I accept no responsibility for damage to your mod folder or even your computers file system as a result of mistakes made while attempting to follow this guide.

I will only cover the basics and do not intend to go too in depth with stuff. By all means ask questions and ask for something specific, but its a side project away from other stuff. If I say no, its because I don't have time or because I feel its beyond the depth I wish to cover here. But, you don't ask you don't get.

And in one of my maps I can't spawn at all, despite there being spawnpoints and whatnot. I compared it to another map of mine that I can spawn in, but I can't pinpoint the problem. Can anyone offer any advice?

I've been working on this map on and off for almost two years. I almost gave up on it since the layout isn't that great for large playercounts (I was quite new to mapping when I started it, in fact it was the second map I've ever created for FS).

However, the BI folk liked the map and urged me to finish it for the Inter-Clan Wars, so after months of testing (big 'thank you' to all who helped) I'm proud to present you the finalized map.

Backstory
A Rebel troop transport escaping from an Imperial ambush is running fast out of fuel and has to land to the nearest habitable planet, a small planet on the outer rim.
Unfortunately for the Rebels there is a small Imperial outpost on the planet, and Rebels get under heavy turbolaser fire under landing.
The escorting A-wings manage to disable the turbolaser and shoot down one of the outpost's Lambda-class shuttles.
Having lost last of their fuel in the battle, the rebels make an emergency landing nearby.
They now have to quickly capture the outpost and liberate their fuel supplies before Imperial reinforcements arrive.

Setting:
This map is set under the cover of darkness, with light snow constantly falling.  There are multiple routes to almost every control point, meaning the defending imperials will have to constantly watch their flanks to make sure no sneaky rebels have managed to get past.
This map contains a lot of custom never-seen-before content, including custom statics, textures and music (thanks to everyone who contributed!), as well as some previously unseen game-play elements which I'm going to let you find out for yourselves.

Minimap:

Screenshots:

DOWNLOAD LINK
Just unzip and follow the instructions in the readme. If you have any problems contact me or Gwynzer.

1. 3ds Max? XSI?
2. Is there a way to get them out of the FS mods folder into 3ds Max (if that is what you guys use).

My problem is not wondering how to model and texture, I can manage that on my own. My problem is that I want to get existing FS objects back into their original editor and I don't know where to get them. I believe a "*.con" file stores a static object. I don't believe I can import that. Or can I?

I have a wall and a wall support and I want to stick them together to make sections so I don't have to keep fiddling.

I've tried adding

ObjectTemplate.addTemplate large_support
ObjectTemplate.setPosition 0/0/0

to the Large_Wall Tweak file but when I place Large_Wall on the map the Large_Support is not there

Any ideas?

This is the first in a planned series of illustrated First Strike modding guides, written in co-operation with the rest of the FS testers and, of course, the development team itself. The series will cover simple "getting started" topics as well as more advanced stuff. It's not 100% complete, but should be useful in getting you started.

This first article is a simple guide that will help you install and set up the powerful, albeit clunky, BF2 Editor we all so love to hate. First of all, we need to get it installed. You've got two choices here: you can either use the Battlefield 2 version, in which case you'll need Battlefield 2, or you can get a modded version that will make use of 2142. If you want the BF2 version, you can get it here.

If you only have BF2142 installed, you need to go through the steps outlined in this thread.

Once you have the thing downloaded, just run the exe installer and you're all set. Start it up to make sure it works. You may have to run BF2 and play a round or two beforehand to create the BF2 folder in My Documents {can anyone verify this?}. {does bf2 editor support the 1.50 patch?}

Once the editor starts, it'll ask you if you want to use the 'bf2' mod or create a new mod from scratch. Choose bf2, after which it will load the bf2 material (which will take a while and produce lots of error messages - those are unimportant and you can pretty much just close the window containing them anyhow, as it's pretty much useless 99% of the time). Once it's done, you know you've installed it correctly and that you're ready to import First Strike.

Now, although this is a bit of a tedious process, at least it's everything but difficult. What you need to do, in short, is extract the zip folders containing the FS materials and put them in new folders, for then to move them to the BF2 mods folder. I'll walk you through the process of one pair of zip archives - the rest are handled the same way.

First of all, open a browsing program and go to C:\Program Files\Electronic Arts\Battlefield 2142\mods\FirstStrike. There will be two zip folders called common_client and common_server, which we will get around to copy over, but for now we will focus on the static objects. Open the Objects folder, in which you will find a number of zip files organized into pairs in the same manner as the Common files mentioned above. We're looking for Staticobjects_client and Staticobjects_server. Select both and extract them anywhere on your hard drive - just dumping the content to the desktop works just fine unless it's full of stuff already. If you're asked to confirm if you want to overwrite files, choose "Yes to all".

Once you have extracted the zips, you should have a number of new folders, labelled by content, on your desktop. These will be labelled by content, such as "Bimmiel", "Destroyables", "Interiors", and so on. Put each of these in a new folder you call "staticobjects" (without the 'client' or 'server').

At this point, you may want to import this folder to BF2 Editor. This will let you know if you've gotten the process down right: if you're doing this wrong somehow, you'll want to know *before* you do the same thing for the remaining folders . So what you want to do is open BF2 Editor and, when prompted, create a new mod you call FirstStrike (you'll probably only be able to choose "Battlefield2" for mod version - don't worry about that).

The editor will get to work, spewing out more error messages as it goes. Once it's finished, shut it down and copy the staticobjects folder you just created to C:\Program Files\EA Games\Battlefield 2\Mods\FirstStrike\Objects. This folder will most likely already contain some editor-default folders and data files. Those can be safely ignored for the most part, and overwritten as necessary. {or is it better to just delete these? It's not as if they're necessary.}

Once you've moved staticobjects over, open up the editor again and tell it to load FirstStrike. Once it's done, go to the Mod drop-down menu and choose Mod Manager..., then go to the Editor Content bar and highlight all the available checkboxes, then hit OK.

Once the editor stops working, close and restart the editor, and you should be able to select static objects from the resource browser. The below pic shows the resource tree with staticobjects and common loaded in:

Go ahead and do this for the remaining content folders. Note that there are two sets of folders named 'common' - just lump these together, overwriting files as necessary. It should be noted that you strictly speaking don't have to copy over every single folder - you can get a lot done with just common, vegitation, staticobjects and vehicles, and you can always copy over and load the rest of the folders as you need them. Having only the material you need imported and loaded saves time and makes the editor start faster. At the end of the article I'll detail what each folder contains.

Once you have every folder in Objects extracted, put into new folders, and copied to their new home in Battlefield 2/mods/FirstStrike, open the editor again and use the Editor Content window to enable all of the new content. This will take a while, but once it's done, you're all set to start making maps!

Couple of notes:

1.  The editor is incredibly crash-prone - save and make backups often!
2.  Only use Backspace to clear numerical fields - using Delete crashes the editor (see #1).
3.  Play around with the various windows, closing, resizing and moving them as you need them. The ConsoleUI and "Red error messages window" can both be closed and then re-opened when you need them.
4.  Be careful with the Soldier feature (available from the Camera drop-down menu). It will crash the editor if you do not have the necessary features loaded, and it will may move things around on your map. Always save your work before going into Soldier mode!
5.  Do not place vehicles or gun emplacements by simply dragging them onto the map, or they won't be there when you return to the editor. To place a non-static object, right-click the map and choose "Create ControlPoint", then "Create

Called at tgw has done some cracking work making bf2 maps playable via 2142 see link: http://www.tournamentgamingworld.com/on … y.php?f=72

What i will suggest is having acouple of billboard textures promoting first strike and where the map originally came from.

Now, for Solomon Showdown the custom objects need to be seperated into static_objects and vegitation client and server zip files. What I did was to copy all the static objects into both the staticobjects_client and staticobject_server zip files and copy all the vegitation into both the vegitation_client and vegitation_server zip files. Then I removed the texture folders from the _server zip files since they take up a lot of space and are not needed in the _server zip files. Now, in the BF2 custom object file, it has a folder for static_objects and another one for Vegitation, but for BF2142 since the veigitation and static_objects are in their own zip files, I copied over the subfolders under vegitation and static objects into their respective zip files. Be careful to maintain the same file structure format when seperating the objects, because if you don't you may have missing textures and see Uncle Sam. At least BF2142 will not crash like BF2 if textures are missing. To verify the correct location of the textures, look at the staticmesh file using Rexman's texture viewer (Anyone have a link? - I can't find this tool) or a hexeditor. When using a hexeditor, scroll down to the bottom of the screen, and look for reference to a file ending in '.dds' - that is where the object is linked to the texture.

Then in the map's server.zip file, I changed both the client_archives and server_archives to this:

fileManager.mountArchive Levels/Solomon_Showdown/objects/StaticObjects_client.zip Objects\StaticObjects
fileManager.mountArchive Levels/Solomon_Showdown/objects/Vegitation_client.zip Objects\Vegitation

This is Solomon Showdown converted for use with the FS_SP mod:

http://www.battlefieldsingleplayer.com/ … own_v2.zip