So I've been working on some scripts, however none of them are actually showing up in-game once I build the map. Initially I thought I was just doing something wrong in the script, but I figured something was wrong when I set up a very simple cutscene, and it didn't play out when I started the game. At that point I figured I'd do something a lot more simple by just having the server say something when you join the game.

Here's the script, just in case I am indeed missing something:

(script startup derp
	(sv_say "sup")
	(sv_say "huehuehue")
)

Sapien does tell me the script compiled successfully, and even if my syntax is wrong, I've literally copy and pasted scripts from well-known tutorials just to see if they would work, and they haven't.

I am running Sapien in administrator mode, and I'm on Windows 7 64 bit. I remember a while back Sapien had a hard time running on multi-core processors (at least I think I remember that being the case), so I dunno if that has anything to do with it. Is there anything I'm missing?

Further proof that my scripts aren't even making it into the game is with the fact that they don't even show up in my map files when I open them with the Halo Script Extractor. So far, everything I've read has just said "click compile scripts, save the scenario, build the map in tool", which is what I've done.

Edit: I put 'tag' in the topic title instead of 'script'. My mistake.
Edited by Prototape on Aug 12, 2013 at 03:15 AM

Try putting this before the sv_say
(sleep_until (= (list_count (players)) player_spawn_count) 15)

That should wait until the player actually spawns.

Here's an idea, I had a similar issue at one point.
Check if in the Halo Custom Edition folder the option for showing Compatibility Files shows up on your windows explorer bar. One annoying thing I noticed about HEK is that if I change a tag in Guerilla and save it, it puts the new save as a compatibility file, leaving the original untouched, and since tool only recognises the tag in the file and not the good new one that is pretending to be in the file, it uses the wrong one.

Looks like this:

Except in your Halo directory.

when you click on there, it takes you to a temperary files location, where the newest version of the scenario file is. Cut and paste over the version in the proper Halo folder.
Don't ask me WHY it happens, but Guerilla and Sapien both do it to me.

Didn't work, unfortunately. My scripts still aren't showing up in my .map file when I look at them with the script extractor. I'm wondering if this is something on Sapien's end. I have looked at the debug.txt, but I don't see anything in relation to my problem appearing there.



Well that solves one problem I was having a while ago, unfortunately it didn't solve the problem I'm currently having. My script files are showing up just fine in the 'scripts' folder within the level's root directory, but for some reason Sapien isn't building them into my maps.

To completely resolve that compatibility problem, right-click your Halo Custom Edition folder, go to Security, and set the permissions for the Users group for Full Control.

If your scripts are not showing up in your map, make sure the directory is correct.
data/levels/mapname/scripts/scripthere

Also, you have to File>Compile scripts in Sapien

Cool, that'll save me some time down the line.

Anywho, so my directory looks like this:
data/levels/test/tutorial/scripts/derp.hsc

Sapien tells me the scripts compiled successfully, and the map builds without any problems. I'm not quite sure what's going wrong in the process.