Download LIT Here

Lua Interpreted Triggers(LIT) is a Lua library to generate text triggers. Text triggers are usable by SCMDraft 2, and Chkdraft. Lua code is written, and the LIT library of functions and objects allows a user of LIT to generate triggers en masse. LIT is designed to be very easy to setup and use.

LINK TO DOCUMENATION (PDF)

link to source code

Post has been edited 40 time(s), last time on Nov 9 2015, 12:35 pm by CecilSunkure.

In this thread: please do post any suggestions here, report any bugs, or ask questions if you have any problems. If you can convince me a particular feature request is useful I'll implement it

-Reserved

Post has been edited 2 time(s), last time on May 21 2014, 9:18 am by CecilSunkure.

Since trigger generator is already an abstraction, maybe some can add more of them.
- Automatically detect unused units (maybe CHKDraft API?) & assign them variables.
- More than 16 conditions should be supported. ( Using DC or something )
- More than 64 conditions should be supported. ( Using DC or something )
- Method to attach callback to various exceptions.


LIT should be supported by ChkDraft in form of plugin, not its internal implementation.

Post has been edited 1 time(s), last time on May 21 2014, 10:47 am by trgk.

id like to try this but it seems a bit too intimidating to me, maybe you can post a few examples of how to use it? (including pictures and step by step instructions) I know this would make me much more inclined to try it.

Wellllll okay I'll make a video.

Here it is:



Post has been edited 2 time(s), last time on May 22 2014, 3:20 am by CecilSunkure.

I checked the lua code for actions and couldn't find the one for switches.

Are you not done putting it all together?

Definitely not! This weekend I'll finish more actions

Ha! Patience

All conditions and actions are supported. I've tested them all and should have nearly all bugs found and fixed. Please report any bugs if you do find them. I've decided to host all examples and any LIT tutorial-esque stuff on my own website since it's easier to write and format things there.

There really doesn't need to be much documentation since I've written two huge example files showing how to use each condition and action. If anyone wants to learn to use LIT it's mostly going to be a matter of learning Lua. Luckily learning Lua is a very productive and easy thing to do!

Hopefully I have energy to actually make an example map, and perhaps a short Youtube video of running LIT to generate triggers for a scenario file We'll see how much energy I have tomorrow.

Edit: Oh and the first version of LIT was deleted. I didn't really like how I the code was going, so I started over. So Sacruier will need to redownload the files.

Syntax looks esoteric.



I really had to 'parse' this plaintext. Is there any advantages of using these syntax?

The idea is to separate initialization and trigger generation. Here we see some initialization code just assigning values. The player, unit, location and count (of units) are all set:



After this is done creating a trigger can be done in a readable block of code:



This is nice if you look at the Binary Countoff example I have written:



Since initialization happens in one place, and trigger generation in another, triggers can be generated within a loop in a simple and readable manner.

I hope this makes sense!

OK. Building patterned triggers could be quite easy with those semantics.
But building once-used triggers with those syntax seems like a pain.

ex)

CreateUnit(1, "Boss #1", "test", "Player 1") // only used once.

vs

unit = Unit( )
unit:SetPlayer( Player1 )
unit:SetUnit( "Boss #1" )
unit:SetCount( 1 )
unit:SetLocation( "test" )
unit:Create( ) // 6 lines


Some kind of shortcut, or direct condition/action generators are needed.

ex) CreateUnit(1, "Boss #1", "test", "Player 1")

( CreateUnit may be single lua function )

Post has been edited 1 time(s), last time on Aug 12 2014, 9:19 am by trgk.

Yeah I agree, shorthand functions would be super nice! Thank you for bringing this up so fast.

In order to make good shorthand functions I would have to know which functions to write. I'm not sure which shortcut functions for one-time triggers would actually be useful and worth my time to make. I decided for now to support *only* long-hand semantics becase anyone using LIT can make their own shorthand function like this:



It would be very nice to include these kinds of shortcut functions in LIT, but I just don't know which ones to make. After people use LIT a little bit and share their experiences (like you did last post so quickly!), I can write in some shorthand functions that are useful.

It will take some time and trial-error to figure out which semantics are the nicest.

Started adding in shorthand functions. For now there's only a few, so I've updated LIT with them. The download link in the OP is updated. LIT is now version 1.01.

I also created a demonstration map, download here. It's an implementation of xYoshix style screen-sized rooms with burrowed units. To create the triggers yourself you can just drag and drop ALTTP.lua onto LIT.exe, assuming everything is in the same folder. Alternatively, like the OP says, you can use a proper command line and tell LIT which folder ALTTP.lua resides in.

RoomLogic.lua is the most interesting part, and makes use of the string concatenation operator "..". The .. operator just pastes the strings on the left and right of itself together. Example:

variable = "This is a se" .. "ntence."

The variable will hold the value of "This is a sentence". The nice thing about concatenation is that you can make triggers for multiple players in a loop with this, as shown in RoomLogic.lua.

Some of the new shorthand functions are used in RoomLogic.lua as well.

The download link can't be found

Whoops, fixed it now. Thanks.

I find it really odd that generating is literally impossible. PlayerGroup(0) should produce such a thing. Similarly, it's impossible to generate Forces. (Is this because of considerations of mechanisms in StarCraft's handling of players in triggers or?...)

I got it to work after some trial and error. Feels pretty good.

Hey there, I didn't bother with All Players of Forces because you can just assign any player group yourself. For example, if players 2-4 were in Force 1, you can just make a player group for players 2-4, instead of in forces.

It's just me being a lazy programmer, plus when I make maps I personally never use all-players or forces. Just a preference.

Minor update:
Continued work late into last night, I actually regret how I wrote most of LIT and can see better ways of doing it after the year has passed. Oh well! It looks like there will be two major APIs, the "object oriented" way where you make an object and assign state to it, and short-hand functions that just print out trigger text, but don't store state.

My experience shows the shorthand functions are way nicer in almost every way, so as I go on using LIT over time I'll just write more and more short printing functions whenever a need for one comes up.

Some example code I wrote late last night:

link to code for using bomb from inventory

Here's a good example of why using a trigger generator rocks (any trigger generator!); say we are making some rooms and want to connect them together with two locations. Each location is placed at an entrance/exit of both rooms. Lets name the locations A and B. Lets assume the player has just one hero unit.

When a hero walks onto A we want to move the hero to B. When the hero walks onto B we want to move the hero to A. If either of these triggers occurred we want to keep it from happening again until the hero is not at location A or B (this prevents the hero from jumping from A to B infinitely).

This kind of doorway is very tedious to construct by-hand and takes time. Each doorway needs to be tested to make sure the triggers have no bugs. Instead we can write a function in Lua that LIT turns into triggers. We can test this function once and re-use every time we have a new pair of locations to act as a doorway.

Here's some Lua code I wrote for LIT:



Now each time I need to connect two locations together I use this line:



If I would like to connect many different rooms together, we can do something like this:



Proof: