Var isbigbadmonster1killed =0;

......

Now after the while(health >0) loop put

Isbigbadmonster1killed =1;

Now put this at the Start of the function

If(isbigbadmonster1killed ==1)ent_remove(me);

Game_save will save these vars so that is not a problem but it can't save what was done in a level unless there is something to save.

I don't get your point here, FoxHound. If you load level X and bigbadmonster gets killed and removed, then it will not be there even if you do a savegame, load another level and load the savegame later on. Why making it so complicated with additional variables and script effort?

Siwler is setting his levels up in wed where he also sets up the monsters and attaches the script. So when he kills a monster and leaves a level and comes back then the monster would be back no matter how many times it was killed. My way sets it up to check to see if he was killed before, and now that I am at a computer and not an iphone i can write it out a bit better

var monster_1_alive = 1;

function monster_1_function()
{
//if i am dead then what am i doing here?
if(monster_1_alive == 0)
ent_remove(me);

//i guess im alive so i should have some health
my.health = 100;

//while i have that health i should hang around
while(my.health > 0
{

wait(1);
}

//guess i'm dead now
monster_1_alive = 0;

//goood bye cruel world
ent_remove(me);
}

That is the point I don't understand because from my point of view this is simply not true. If you remove an entity X from a level, do a save game and later on load that savegame entity X will still be gone.

Correct, as long as you do not reload that level. Once you reload that level it will be exactly as it was the first time.

So kill all the monsters in a level, go to the next level and then go back all those monsters will be there because you are loading a level with monsters in them. Now if you had one giant level and never used level_load then you would not have to worry about that.

I still think you didn't my suggestion. For every level you attempt to load first try to load a savegame for that level. If and only if loading a save game for that level fails then load the original level.

When you reload the level it will of cause be in it's initial state. The point is avoiding reloading by doing savegames when leaving the level and doing a game load instead of level loading when reentering the level.

Game_save and game_load its not working for when going back and fort between levels, here is why:

I'm in level 1 right now and I kill 5 main monsters then collect $500. From this point I can go to level 2 so I can kill more monsters collect more money and get better weapons.
So before I leave level 1 I game_save level 1 then load level 2 right? Now I kill 5 monsters collect another $500, now I have $1,000 and I have to go back to level 1, before I leave level 2 I have to save level 2 and then game_load level 1, sense I have to game_save all my progress under same string name and game_load from the same .SAV file I never leave level 2 it sends me to a loop, which is game_save before leaving level 2 then game_load from the same saved file which was last saved in level 2 it always game_loads me back to level 2 again and again?

But when I game_save and game_load under different .SAV name for level 1 and level 2 then I can't bring anything back from level 2 to level 1, because of saving and loading level 1 under different name.

I do appreciate you guys trying to help me out I have learned a lot from this.

The basic idea is to have one save game per level. For instance if you have the levels cave.wmb, dungeon.wmb and town.wmb, then you should do three save games as well. cave0.sav when leaving cave.wmb, dungeon0.sav for dungeon.wmb etc.

Additionally to that you should save things like the player inventory, his stats etc. in an external file. Alternatively you can use info variables for this and use the save game mechanism for that as well.

YOur idea is that it's better to have one save file per level plus one save file per game? That doesnt work on levels that need to change. Such as summer and winter levels or I'd you can enter a level from multiple points on top of the fact of how many levels you could have in game.

If you have different versions of the .wmb files like summer or winter then it gets difficult, yes. Entering a level from several different positions is easy though. First load the game or level, then set the player to the desired position.

The advantage of my solution over yours is that it is generic. Once you realised it is done you don't need to bother about the issue any more. Your approach will generate work for every level and almost every actor inside the game world.

The advantage of your method is of cause the plus on felxibility you gain.