-Release-
This little tool will extract scripts from a map or yelo and spit them out on the screen, with the option to save to .hsc so you can compile with your scenario.
There is also a little Easter egg, find it and post a screenshot for cookies :P.

Download:
Google Code: http://halosenox.googlecode.com/files/HS%20Script%20Extractor.zip
Halomaps: [Pending]

Virus Scan:
https://www.virustotal.com/file/372fa74392519d9c97976ce1ef1988fd437099128bf594b90c9f7471226fd080/analysis/1346552453/

Enjoy!
Edited by haloextreme117 on Sep 1, 2012 at 10:23 PM

I hope it isn't the one I already have(the scripts that it spits out are freakin' messed up).
E:Very similar.Not sure if they're the same.
Edited by Dumb AI on Sep 1, 2012 at 10:39 PM

Nope, this is my own. Every map I've tested it with has worked fine, and the scripts are identical to those compiled with the map.

Well,they look the same.Not sure who made it.

I wouldn't imagine it does formatting, does it?

It shows the script exactly as sapien compressed it; the app just processes the compressed script, adds parentheses and so on.
Generally, the script extracted will be exactly the same, just formatted differently.

Not identical.Lots of differences here and there.
Extractor:
(script continuous void halo
(begin
(sleep_until
(<=
(ai_living_count red) 0))
(sv_say incoming reinforcements)
(ai_place red)))

(script continuous void cod
(begin
(sleep_until
(<=
(ai_living_count blue) 0))
(sv_say incoming rangers)
(ai_place blue)
(ai_command_list blue cod)))

(script startup void greeting
(begin
(sv_say welcome!)))
Mostly likely just differences made by Tool.
Source:
(script continuous halo
(sleep_until (<= (ai_living_count red) 0))
(sv_say "Incoming reinforcements")
(ai_place red)
)

(script continuous cod
(sleep_until (<= (ai_living_count blue) 0))
(sv_say "Incoming rangers")
(ai_place blue)
(ai_command_list blue cod)
)

(script startup greeting
(sv_say "Welcome!")
)
Bunch of useless junk like extra parentheses.
Edited by Dumb AI on Sep 1, 2012 at 10:56 PM

Extra parentheses? I can't see any. They match up as far as I can see.

None of this would actually be a problem but editing scripts might be a bit harder due to the formatting.
Edited by Dumb AI on Sep 1, 2012 at 11:24 PM

Might want to use the {code} and {/code} (replace { with [ )tags, they allow formatting.

Thanks for releasing, what a great evolution for halomaps coders!!

The formatting makes it easier to edit scripts the way it is now and I don't see any useless junk or extra parentheses. However, I do see a major problem with something...

(script continuous void halo
(begin
(sleep_until
(<=
(ai_living_count red) 0))
(sv_say incoming reinforcements)
(ai_place red)))

(script continuous void cod
(begin
(sleep_until
(<=
(ai_living_count blue) 0))
(sv_say incoming rangers)
(ai_place blue)
(ai_command_list blue cod)))

Source:
(script continuous halo
(sleep_until (<= (ai_living_count red) 0))
(sv_say "Incoming reinforcements")
(ai_place red)
)

(script continuous cod
(sleep_until (<= (ai_living_count blue) 0))
(sv_say "Incoming rangers")
(ai_place blue)
(ai_command_list blue cod) 
)

I'm pretty sure the lack of ""s will cause problems, because I think that (sv_say incoming rangers) will be treated as if "incoming" and "rangers" were two different arguements due to the space whereas the normal sv_say demands only 1 arguement