He did. Look at the very first picture.



Edit: Used url tags instead of img tags. I'm not awake yet -__-
Edited by Gamma927 on Jan 6, 2010 at 11:08 AM

Grab notepad++ SRC, strip the code and include it with the app maybe? I have my own language defined if you decide to use it.

I'm thinking about adding a built in text editor for hsc.. So it has code highlights and stuff.

Edited by jesse on Jan 6, 2010 at 05:08 PM

code library.

This is my goodbye. You can reach me on messengers for further information on this subject.


I must leave now, for reasons in which i must not say. yes this project is still in play, just contact me over messenger or email.


Goodbye halomaps.

(no this is not a scam or me giving up on this application, just it's my time to go. Don't ask why, it's nobody's buisness. I'm still working on this project, and will post updates to anybody who is interested. Just send me an IM.)

Sorry Dennis, I meant no harm.

Wha-?

whuddaboutxfire?

lol drama

Agreed to this aswell

i have an idea, for halo 3 mods or other.
guerrilla need more grenades slots.

That's not Guerilla. That's engine. Talk to Dwood and other OS people.

More than two nades are impossible. NFWOS even with os i believe.

i may have an idea....

in guerrila, you have to delete the vehicle instances of any vehicle before deleting the vehicle type itself from the map, right?
sometimes we delete the vehicle instances, THINK that we have already deleted all of the instances and then we delete the vehicle type from the .scenario file.
when we open the scenario file again and try to add vehicles, we suddenly realise that it exceptions guerrila and sapien because we FORGOT to delete all of the required vehicle instances.
this is an annoying problem that even i have encountered quite a few times before.

so, i suggest that the program warns us when we delete a vehicle type that has instances referencing to it within the scenario file, and give us an option to cancel the action before we do damage to the scenario file itself.

There is a reason why the original HEK was locked up. So you couldn't do that.

so it locked off the ability to place and delete vehicles from being loaded as we please? Some editing kit.

Yeah w/e. The reasons for it being locked are ridiculous imho.

Hey e3p0. Unlock recorded animations and actually make it work. ok bye.

The only reason they don't work is because you can't record them. That's why I asked for him to re-enable recording them.

Bungie/Gearbox or whatever took out the code for it.

They took out the code to move units. You can record fine. But since you can't move the unit, it would be a pretty useless recording.

Can anyone explain this for me?

All will be revealed in good time, my dearest Yak. You must first cross the Edelweiss Bridge and across the Eldridge valley to Fort Hensmenshire, and there you will find a man by the name of Tempest. He will explain everything.

lolwut

You, Sir Greenfuzz, are actually lord of the unknown land of Greensmith, a large island of the coast of Ozte. However, in order to claim your rightful throne, you must go with Yak to Fort Hensmenshire and Tempest may give you information on how to overthrow the current evil ruler of your land.