1. Once scripts for a map are written, how do you actually get them to work in the map?
2. Is there a Halo PC to Custom Edition map conversion tool? I know there's one that works the other way around, but that's not what I'm looking for. I want to play this map, but am currently too lazy to reinstall Halo PC: http://www.mytoptrailer.com/show.php?game=halo4&vid=WqOArhM3IcM

1. Put the script in the map's data folder and create a folder named scripts. Place your script in there. For example, for bloodgulch: Halo Custom Edition\data\levels\test\bloodgulch

1. what he said, but open sapien and press ctrl + shift + c to compile it into your map

2. reinstall halo pc

I tried compiling the scripts in Sapien, and it didn't work. Could it be a problem with the scripts themselves, or is there another step I haven't done? Here are the scripts for reference (this map is a mod of Extinction, so I used the script extractor from http://forum.halomaps.org/index.cfm%3Fpage=topic&topicID=41477 to get scripts I knew would probably work): https://dl.dropbox.com/u/55579636/scripts.hsc

Still no luck.

When saving the file, make sure the Save as type box is set to "All files", then save your script as <scriptnamehere>.hsc

Still no good. I think CE hates me.

Is the script file in the proper folder?

What are you trying to get the script to do?

The directory should be "data/levels/mapnamehere/scripts," shouldn't it? That's where it is right now. Does it need to be in the "test" folder if it's a multiplayer map? Anyway, the script is supposed to make additional vehicles spawn so I can have more than 6 different kinds. In case you didn't read this earlier, this map is a mod of Extinction, so I used a recently released script extractor to obtain the original map's scripts (since they obviously work). I made sure the object names matched those in the scripts so they theoretically would be compatible.

the directory should point toward the folder that your scenario is in ill use one of my maps for example
scenario location:
tags\kzcm\firefight\beachside
scripts folder location:
data\kzcm\firefight\beachside\scripts

my scenario was in the folder called beachside, so you make a folder called scripts inside the same directory but in data instead of tags.

hope that helps

I read it but I've never used the script extractor, or even knew of its existence for that matter.
Edited by Ermac on Oct 17, 2012 at 07:53 PM

Hey, I'm getting somewhere. I fixed a problem with my directory, but now I get this error in Tool.

Hm. Does the debug tell you which line it was? I'm looking through the script now to see if I can see the error.

If not, that error should also show up when you attempt to compile it in Sapien, and I know for a fact that Sapien will tell you which line it is.

EDIT: Tried this suggestion I had here, did not work. Will continue working with it.
Edited by Ermac on Oct 20, 2012 at 01:29 AM

check that your variables and/or dormant(scripts that wait for wakeing) scripts are correctly set. I.E. all used variables and dormant scripts must exsist. (E.G. foo + 7, will fail if you do NOT have variable called "foo"). in Blam! Script variables are called "globals". also it would help a lot if you would post your script... you can't *always* use extracted scripts, without editing them first.
edit0:*is in green*
Edited by afD2345 on Oct 20, 2012 at 09:13 AM

dropbox/links seem to be having problems, you're link doesn't work and nor did goldkillers in his release thread. although his is fixed :)

dropbox links will work if you remove "https://" or "http://" from beginning E.G. dl.dropbox.com/u/55579636/scripts.hsc

good stuff, i hadn't tried. ty

So, does anybody see any problems?

Guize.

We need halp.