Oh? I didnt know i could mod halo 3 that way. links or something i can use to look into it?
Oh? I didnt know i could mod halo 3 that way. links or something i can use to look into it?
the '' was suppose to mark the fact that it was a joke/sarcasm ;x
Sadly, no, can't mod h3 that way (without a dev kit). Not until/unless they make a PC port.
They should dub it H3V7: Halo3 Vista/7!
e: the single quote marks make it looks like the downer has downer arms. ha.
Yeah im posting from my craptacular phone. i cant see emotes on it.
d-d-d-double post!
I would like to expound on my idea with the adding arrays to halo script..
What if you just did it like this:
(global array bool4a (0, 1, 1, 0))
and would be used, in halo script, like the following:
bool4a(1)?
Then when compiling, or pre-compiling, the interpreter or w/e we call it takes the bool and creates 4 separate globals of type boolean, replacing all occurences of bool4a(#) with the corresponding bool...? oh but that wouldn't be advantageous b/c if you introduce randomness, yeah just forget that idea. Might as well do that with an external script interpreter.
Edit coming up with an idea for the 2nd one... Even though it might work better with a separate interpreter outside of Halo.
I'm curious about something, how close was this feature to being finished?Originally Posted by Kornman00
What's the point? I don't see any reason why arrays need to be added to the Halo scripting language. Unless you change the way the engine handles the scripts, you would have to create a new script compiler to replace the current one, which will put the new "array feature" into a format the engine can understand.
Actually you're misreading what I said.
Was meant to seal up the array idea.
I was talking about the script arguments, to which Korn suggested I write my own higher-level language for Halo script (lol)
That is what I was referring to when I mentioned making a higher level language. I originally made up the rough draft (along with how to translate it into usable HS) of PSL during lunch in high school. However, I diverted from the Prom team before any work went into the actual program itself. Rec0 may have worked on it some before he started gathering exception data, but I believe it (in that picture) may have just been an example script of what could be.
I never gave up on crafting it myself in my own tools, but I never really drifted too far from the design phase. For me, implementing something like that is a 2.0 (if I ever released a all-in-one version of my tool) feature as there are tonnes more things which would have been more useful (must of them tag management related).
Is that new scripting language to the point where someone just needs to integrate it into a tool or are there still things that need to be designed?
I wouldn't call it a new scripting language, because it doesn't add anything to the Halo Script Language, it's just Halo scripts in a different form.
Sounds to me like he finished the design phase for the most part. But designing it isn't the only hard part, you will need quite a bit of programming experience to do this.
My question was asking more specifically what needs to be done in order for the language to be considered 'complete'. It probably wasn't that obvious however that was the intent. I don't want to assume that he finished the design phase, and then think that he only needs to implement it.
-> If it were at that stage I would simply request him to send someone the designs for it and let them complete it.
Last edited by Dwood; October 27th, 2009 at 05:57 PM.
There are currently 1 users browsing this thread. (0 members and 1 guests)
Posting Permissions
Bookmarks