(script startup test
(ai_allegiance player flood)
(sleep_until (volume_test_objects trigger_1 (players))15)
(ai_place flood_turret)
(sleep_until (volume_test_objects trigger_2 (players))15)
(ai_place flood_citadel_1)
(sleep_until (= (ai_living_count flood_citadel_1) 0) 15)
(game_save)
)

The allegiance doesnt work, nothing of this works.

My script map location is;
C:\Program Files\Microsoft Games\Halo Custom Edition\tags\levels\floodassault\scripts


Any Help? im just a beginner, and this is my first scripts wich i didnt totally copy from a tutorial.

Thanks in advance!

You are moving my script file to this location:


C:\Program Files\Microsoft Games\Halo Custom Edition\data\levels\floodassault\scripts

Go.

Youre name is realistic.

Yes sir :P

Also, don't bunch up your script like that. Makes it confusing. Used to do that, until I couldn't tell which part of my script was which. Change your script to something like:

(script startup test
(ai_allegiance player flood)
) 

(script dormant deadflood 
(sleep_until (= (ai_living_count flood_citadel_1) 0) 15)
(game_save)
)

(script dormant trigger2 
(sleep_until (volume_test_objects trigger_2 (players))15)
(ai_place flood_citadel_1)
(wake deadflood) 
)

(script startup trigger1
(sleep_until (volume_test_objects trigger_1 (players))15)
(ai_place flood_turret)
(wake trigger2) 
) 

Also, never EVER use game_save.

Use game_save_totally_unsafe.
Edited by Polamee on Mar 11, 2009 at 09:51 AM
Edited by Polamee on Mar 11, 2009 at 09:52 AM

I see that you agree with me now :)

Wy not use gamesave? It has some downs?

game_save gives up after 8 seconds.

I prefer game_save_no_timeout myself - the totally_unsafe command has put me in some pretty screwed up situations. It even did it once when I was dead - the checkpoint revert consisted of me dying over and over again.

Being why "game_save_totally_unsafe" is totally unsafe. Unless it is absolutely urgent that you need to save at an exact moment, which I doubt, there's no reason to use that one.

Use "no_timeout" so it never stops checking, and then saves safely.

The conditions to save are that you aren't moving, and that you aren't in danger. I doubt the player will stop moving at a convenient time. If you're planning out the level, and you want the game saved right then and there, use game_save_totally_unsafe. I looked through Bungie's scripts, and they themselves used that. But if you don't enjoy the prospect of saving in the middle of a battle, then go ahead, use game_save_no_timeout.

i would say to use game_save_totally_unsafe if you about to enter a battle of some sort and you wanted it to save before it and not after since if you die during the battle; you would have to not only start it again but you would have to do whatever that was before.
and i would use just game_save after a cutscene that has no enemies right after fore at least 5-10 sec and if you want to save after a fight use game_save_no_timeout. just as a recommendation

Bungie mostly used the game_save_totally_unsafe command when they KNEW that there would be no enemies in the vicinity at the time the command was issued, such as in the hallways in b40/c40.

I once got a checkpoint in mid-air and in the middle of a melee attack. Movement is not one of the factors for saving a checkpoint. If that were the case, then you're right, totally_unsafe would be the best option, because most players move a lot. But like drillinstructor said, Bungie used "totally_unsafe" only when they knew it would be safe to save a checkpoint.