No: By default, all you can do is switch the map, and then the engine will discard your current map and load the specified map and execute it's Verge C file, starting with the autoexec function you've chosen in Maped.

The Autoexec function will need to create a new entity and hand control of it to the player.

You'll need to add at least three global variables to your system VC.

int plr; // this is used to store the current player entity
int plrx;
int plry;

These will be used to store the position you want to create the entity at when you leave the current map (you can't use local variables, because they're attached to the map VC, and they'll be lost after you perform a map(); command.

Then, instead of calling the usual map command, you use mapswitch( <mapname>, <x>, <y> );

Add this function to your SYSTEM.VC

void mapswitch( string mapname, int x, int y)
{
plrx=x;
plry=y;
Map(mapname);
}

This takes a string, for the mapname, and the x and y co-ordinates you want to create the new player entity at. It then copies the X+Y co-ordinates into the global plrx, plry variables, for safekeeping, then executes the new map.

Then you add lines like the following to every MAP.VC that you create:

plr = EntitySpawn( plrx, plry, "art/chr/alex.chr");
SetPlayer(plr);



...Questions?

would this work then?

void mapswitch( string mapname, int x, int y)

{

plrx=5;

plry=5;

Map(tutorial2.map); 

}

??????

Sorry, that was one of my retarded friends!
sorry!
would that work?????

Thanks Overkill!!

Do this instead:

void MapSwitch(string mapname, int x, int y)

{

	plrx = x;

	plry = y;

	Map(mapname); 

}



void NextMap()

{

	MapSwitch("tutorial2.map", 5, 5);

}

And in your MAP file, create a zone that will activate NextMap when you touch it.

it sez plrx isn't a recognised commeand

Don't get fed up because he doesn't know basic scripting, Overkill. He obviously needs to have a beginner's tutorial to cover the basics in easy-to-understand language and intuitive examples!

...ahem.

I'd just like to say that although that was quite along time ago, by that point I had read all the manuals and a large amount of the documents and if i still didn't get it surely it was allright to ask?

Another good trick is, rather than starting out from scratch, is to build off a base like Sully. Infact, I'd go so far as to say that's exactly what people should do first.

In some ways, it seems like cheating to use other people's work like that, but some of the most fondly remembered demos are V1 work, and Sully doesn't provide much more functionality than V1 used to (though it does do it so much better and more flashily, Grue)

The thing is, by building off Sully, you gain a decent understanding of the dev-tools and a basic understanding of Verge C, before you start out to create your own monster-RPG from scratch.