As the title suggests i'm in need of the entire vanilla campaign scenario tags and the scripts which go along with them.

I've searched my self but usually the scripts I find miss basic events and fail to recognize triggers e.t.c

Does anyone know or have any flawless files I can use so when I compile each scenario tag the campaign levell map plays in a correct manner?

Oh and also how do I extract the scripts used in pre-compiled maps?

I.e lets say I want to extract scripts from one of the H3 campaign maps. How would I go about that?

you can't get scripts from halo 2 or above. Dreams campaign scripts are flawless

I was talking about the halo 1 campaign.

I used the scenerio packs and scripts referenced in this thread:

http://www.modhalo.net/index.php?/topic/28424-anyone-who-has-had-trouble-with-sp-maps-in-ce/

And in-conjunction I used the Single player tag set provided by the ghost and kornmann:

http://hce.halomaps.org/index.cfm?fid=5832

Once I installed everything into a default tagset and compiled the a30 campaign level in tool I noticed alot of inconsistencies.

Such as: Music cutting in and out, Certain voice messages from cortana not playing correctly or at all, Drop ships crash into mountains oh and also the whole a30 level doesn't play. I'm wondering if I need to do a switch bsp or something....because all I get is marines running about randomly and no enemy or checkpoint saving....


SOS :(

Tried this? http://hce.halomaps.org/index.cfm?fid=6690

as best i know that's a custom edition (maybe even a HPC?) issue; I haven't been able to make music always switch to alt loops correctly with any amount of finagling and i did some pretty fancy stuff with music loops in tsce. happy to be proven wrong by somebody else though


that's probaly a corrupted extraction by hek+ (i.e. in the tag packs you downloaded). it messes with the physics on at least pelicans, possibly c_dropships as well



these are (probably) script issues

if you want to learn then the best way would be to try and hunt down these issues and fix them yourself! a small primer on how to navigate:
-(script startup) scripts are run when the map starts
-(script dormant) scripts are woken with (wake my_script) and run concurrently alongside each other
-(script static <type>) scripts are ran with (my_script), and halt execution of the script from which they were called until completed. they are basically functions and can also return a value if you want
-halo updates at 30 ticks a second. each awakened script will execute as many commands as it can before the next frame starts until it hits (sleep <ticks>) or (sleep_until <condition>), where it will wait until the ticks expire or the condition is fulfilled, respectively

from that you should be able to figure out where the mission starts, and then where it leads and what it's doing. if you see something you understand in the stock scripts, add a comment line (semicolon opens a comment line, although for clarity's sake I prefer two, i.e.:)

;; wait until most of the aliens are dead
(sleep_until (< (ai_living_count first_encounter) 3))

at the risk of plugging in the wrong place: the tsce scenario & script source release (i hope it's coming by the end of today !! we'll see) will contain scripts for at least all h1 maps, along with a file on all hsc commands and their usage. we'll see about h2v scripts as well, although be warned those use a lot of more advanced haloscript features that aren't available in hce (I really wouldn't look at any h2+ scripts if you're trying to learn hsc for hce)
Edited by Ifafudafi on Apr 20, 2015 at 11:43 AM

Thanks for the wealth of information Ifa.

It seems I'll need to research scripting protocols for halo which doesn't seem too hard given the amount of tutorials and resources on this site.

Thanks again!