-= Gametoast.com =-

I munged EVERYTHING and put checks in the 6 bottom boxes (not the audio boxes), started up BF2, ran my level, etc. Now, when I go running around my map, none of the AI move, except when I run up to them, which then they chase after me until I get to far away from them.

Note that this is in Assault or: What caused this?
How can I prevent this from happening in the future?
How do I fix it in this map?

Also, how do you get the Leaving the Battlefield! message on a mod map?

well, did u add planning? in zero editor you have to set up planning by placing hubs and connections.

So they need connection points to move?

BTW, they do move, but only a little ways which isn't enough to get to the other side where the enemy is.

Yea, you need to add planing, heres a tut.
http://www.gametoast.com/forums/viewtop ... 27&t=10314

The message is associated with boundaries, which you place in ZE.

MercuryNoodles wrote:The message is associated with boundaries, which you place in ZE.

I did place boundries, but I can go past them without the message.

You need to go into your ***.req and add this block:

MasterSaitek009 wrote:You need to go into your ***.req and add this block:

Code: Select all

	REQN
	{
		boundary
		[i]*name of the boundary that you placed in ZE*[/i]
	}

Do I need to put it in a specific spot?

Darn. I can only open it in stupid Microsoft Office. (which I don't have) Otherwise I'd post the .req.

Here, rough version. I have a:

REQN

Then there are the following at the tops of each REQN:

• config
  texture
  path
  congraph
  envfx
  world
  prop
  class
  config
  lvl

Now where do I put the

right below the lvl thingy... that simple

1. Launch ZE and load your WLD file

2. In the base layer click on the Boundary tab

3. Click "New" and place your boundary, move it around and adjust it to fit your needs.
You can have more than 1, and as long as they overlap slightly and you stay inside of them ingame you will still be in the battlefield area.

4. Give your boundary a name. To keep it simple just name them myboundary, myboundary2 and so on.
They can be named whatever you want, boundary names are arbitrary.

5. Save and close ZE.

6. Now go to your world1 folder and find your ABC.req file and open it with Notepad.
Add this code in at the bottom of the list before the last bracket, replacing ABC with your own 3 character modID.
Then save, close, munge and go play!

Gil Grissom wrote:Concentrate on what cannot lie. The evidence.

Notes:

I have done this but it did not work. I munge and run the map, then it is as i havent done anything. I just walk and walk but nothing happens. Any ideas?

ut oh, this topics going to be locked
post ur logs and req in a new topic named boundry prob... ok

This is a FAQ topic. It's immune to locking.

fai222 wrote:I have done this but it did not work. I munge and run the map, then it is as i havent done anything. I just walk and walk but nothing happens. Any ideas?

Prove to me that you followed the instructions, show me your modID.req file located in your world1 folder and a screenshot from ZE.
If you follow the instructions then you'll get something like this:

AceMastermind wrote:

Hidden/Spoiler:

Off topic, but at the reverse grip. It's been done before, but I still love it when I see it.

Ok.
That was the req and here is the ZE pic.

Yep that should work, you did remember to munge, right?
Check your TTS.BND and TTS.PTH files located in your world1 folder to make sure your boundary data was saved, just open it with Notepad and inspect it.
Clean and munge if changes don't appear to be updating ingame.

I checked and it is like it should be. My boundary name ect. This is WIERD.

Your boundary is named "boundary1" and your .req calls for "boundary." "Boundary" in the .req file isn't an identifier of what it's calling, it's an identifier of the name.

You can name your boundary whatever you want, I have one named "ace".
You don't change "boundary" that is being called in the req, that is not the name of your boundary, it's what tells VM to look for when munging, in this case it's going to look for your modID.BND file which holds the names of your boundary or boundaries which in turn directs VM to the modID.PTH file that holds the actual boundary path data which ultimately defines that/those specific path/paths as your boundary/boundaries.

Example:
I have a boundary placed in ZE named "ace"
The code in the req remains as is: Works like a charm.