Small Triggers/Scripting Preview

[null]

Code: Select all

function testOnEnter(trigger, ent)
    trigger:setMaterial("red")
end

function testOnExit(trigger, ent)
    trigger:setMaterial("green")
end


Scripting is done via Lua. The possibilities are endless The above is only a small test with triggers

[Eriksrocks]

Very nice. Will all the custom LUA be saved in a file that goes along with the level?

[Gran PC]

That's pretty awesome! When can we expect a release? Also, can the Lua files be compiled?

[null]

Very nice. Will all the custom LUA be saved in a file that goes along with the level?

Yeah, each level will have it's own Lua script for all the triggers/events/etc.

That's pretty awesome! When can we expect a release? Also, can the Lua files be compiled?

Release: look around on the forums and the main site, we've mentioned it about 10^10000000 times by now. And the Lua files are currently not compiled, makes things a lot easier. Perhaps later on we can add support for compiled Lua files.

[Gran PC]

That's pretty awesome! When can we expect a release? Also, can the Lua files be compiled?

Release: look around on the forums and the main site, we've mentioned it about 10^10000000 times by now.

I was asking if there's a closer estimate other than "before the end of summer".

[ColeScheffler]

That's pretty awesome! When can we expect a release? Also, can the Lua files be compiled?

Release: look around on the forums and the main site, we've mentioned it about 10^10000000 times by now.

I was asking if there's a closer estimate other than "before the end of summer".

I'm guessing it will probably be in the first half of September, unless they decide that they should postpone the release as far as possible, on September 22nd...lol

Anyways, this looks like pretty much anyone will be able to do this kind of simple stuff, but I'm sure you can go super-advanced if you know the Lua.

But wait, what do the OnEnter and OnExit boxes in the properties window do? Owait, whenever something is touching it, onEnter is activated?

[Eriksrocks]

But wait, what do the OnEnter and OnExit boxes in the properties window do? Owait, whenever something is touching it, onEnter is activated?

onEnter is triggered when something collides with the trigger, onExit is triggered when that object stops colliding with the trigger. Basically, when something enters the collision box of the trigger, and when it leaves the collision box of the trigger.

[Frizi]

oh! i love triggers
anybody maybe known jass from warcraft 3?

what features have this implementation? You can change entity properties, how about bulid-in collision detection (or something like that)?

@edit:
oh... nice

[null]

what features have this implementation? You can change entity properties, how about bulid-in collision detection (or something like that)?

You can do anything from the trigger callback. The most common operations would probably be modifying the entity that caused the trigger to activate, doing something in the scene based on a specific entity entering a specific trigger, etc.

[Frizi]

it is possible to affect all entities matching specific condition (or just all) on trigger executing?

[null]

it is possible to affect all entities matching specific condition (or just all) on trigger executing?

Well right now the only way to fetch a specific entity is to get it from the game world via gameWorld:get("someEntity").

[Frizi]

then if you can add (:D) gameWorld:get("EntityType".All), only for events ofc, for actions maybe loops like foreach on all/selected/manipulated/activated or something else objects
or just method GetAllEntities (list or array).

[null]

I can add something like that, but the question is when you would need to grab all of the entities (even of a specific type)? I can think of a million reasons to want to grab some specific entity(s) when an event is trigger, but I can't think of any reason you'd want to do something to all the entities.

[BionicCryonic]

it is possible to affect all entities matching specific condition (or just all) on trigger executing?

This could provide some badass timing events. Imagine two blocks, fixated to the air, or something. They can't move. They are sloped, and one is perpendicular to the other, a short distance away. They have special collide triggers, and link to a whole other bunch of world stuff. Anyways, a ball rolls from the first one on to the next, goes through a portal, and back onto the first one. Infinate loop, lus pulsating trigger-age.

Could be cool.

[FlyingHonda]

Nice, I check this from my iPod at the airport... IM'A THINKIN OF THE POSSIBILITIES!

[Frizi]

hmm...
i dont know lua (currently ;P), then it is python like pseudocode:

for object in (all object in map of type sphere):
   if object.x >= 0:
      object.setMaterial("red")
   else:
      object.setMaterial("green")

this is really easy example, you may need get count of all object on whole map or specific area (ex. -10 < x < 10, -5 < y < 7, 1 < x 112).

you may create new data structure "objectgroup" for loops and returns specific object on every iteration

[TiagoTiago]

what about somthing kinda like sending a message and having the intended group of object each be listening for that message and run their own code when they hear it?


btw, is Lua capable of polymorphism? (code that modify itself or can replace itself with a modified version of itself)

[Frizi]

polymorphism is not self-modificated code :O
http://en.wikipedia.org/wiki/Polymorphi ... rogramming

[TiagoTiago]

really? erm....oops

edit:I oculd swear I had heard someone use "polymorphism" to describe viruses that mutate themselves, oh well, the meaning I waws going for is "being able to modify itself"

[Svenstaro]

LUA is able to do all the fancy object orientation stuff of any other scripting language and as such it supports polymorphism. As Frizi pointed out, polymorphism is not self-modyfing code, polymorphism is overriding methods on inherited objects.

[TiagoTiago]

ok, it wasn't exactly what I was thinking, but somewhat close: http://en.wikipedia.org/wiki/Polymorphic_code

[deathlord]

very nice and easy
partially easier and better than some editors of commercial games

[Phosfor]

I hate the triggers in hammer becouse they are so complicated for some advanced mapping (switching lights is easy but then...)

this is a good idea(scriptinglanguage + triggers) which solves the problems in a good way i think.

only "non-programmers" could get problems

[ColeScheffler]

I hate the triggers in hammer becouse they are so complicated for some advanced mapping (switching lights is easy but then...)

this is a good idea(scriptinglanguage + triggers) which solves the problems in a good way i think.

only "non-programmers" could get problems

Luckily Lua is a very easy scripting language to learn, and doesn't take long to get all of the basics down.

[Frizi]

partially easier and better than some editors of commercial games

see jass: http://www.wc3jass.com/index.php?scripts=1
jass is compilated to bytecode on map loading, what about LUA in Portalized?