Staredit Network > Forums > SC1 Mapping Tools > Topic: LIT - Lua Interpreted Triggers
LIT - Lua Interpreted Triggers
May 21 2014, 7:14 am
By: CecilSunkure  

Oct 31 2015, 3:07 am CecilSunkure Post #21

To add onto my previous post:

Lets say next we want to add a greet message whenever we go in the direction of location A to location B that looks like this:

To do so we can add a parameter to the ConnectRooms function. It's a good time to make use of a trick in Lua for optional parameters, this lets us add in a greet message from A to B, from B to A, or neither. Here's an example:

ConnectRooms( "link's house a", "link's house b", "<13><1C>:: <4>Link's House <1C>::" )

The above line will generate triggers that displays a greet only going from A to B. We can add in another parameter for a message going from B to A (maybe saying that we are back in Hyrule):

ConnectRooms( "link's house a", "link's house b", "<13><1C>:: <4>Link's House <1C>::", "<13><1C>:: <4>Hyrule <1C>::" )

It is easy to see the greet messages that I am using have some redundant text formatting. I can hide the text formatting inside of the ConnectRooms function, so long as I want the formatting to be the same for all greets (which I do):

ConnectRooms( "link's house a", "link's house b", "Link's House", "Hyrule" )

The finished ConnectRooms function looks like:

-- create the deathcounter variable with LIT
local roomDC = Deaths( )
roomDC:SetUnit( "Terran Physics Lab" )
roomDC:SetPlayer( 8 )

-- function that generates triggers to connect two locations
-- together to act as a doorway for a "hero unit" called LINK
function ConnectRooms( a, b, greetA, greetB )
   -- move from a to b
   p8:Conditions( )
   roomDC:SetCount( 0 )
   roomDC:Exactly( )
   BringExactly( 1, LINK, a, 1 )
   p8:Actions( )
   roomDC:SetCount( 1 )
   roomDC:SetTo( )
   MoveUnit( 1, LINK, 1, a, b )
   if greetA then Text( "<13><1C>:: <4>" .. greetA .. " <1C>::" ) end
   Preserve( )
   -- move from b to a
   p8:Conditions( )
   roomDC:SetCount( 0 )
   roomDC:Exactly( )
   BringExactly( 1, LINK, b, 1 )
   p8:Actions( )
   roomDC:SetCount( 1 )
   roomDC:SetTo( )
   MoveUnit( 1, LINK, 1, b, a )
   if greetB then Text( "<13><1C>:: <4>" .. greetB .. " <1C>::" ) end
   Preserve( )
   -- turn off the DC when not present at a or b
   p8:Conditions( )
   BringExactly( 1, LINK, a, 0 )
   BringExactly( 1, LINK, b, 0 )
   roomDC:SetCount( 1 )
   roomDC:Exactly( )
   p8:Actions( )
   roomDC:SetCount( 1 )
   roomDC:SetTo( )
   Preserve( )


Nov 9 2015, 9:53 am CecilSunkure Post #22

v1.10 released (link in OP)

-Automated allocation of death counters/switches
-More fully featured "shorthand notation" functions
-Made a docs pdf (in OP)
-Updated command line slightly to let users place their source wherever they like
-#if #then #end for nesting triggers together in arbitrary #if control structures
-better error reporting (stack trace)
-WINDOWS ONLY: triggers copied to clipboard upon completion
-Integrated to chkdraft (still need to send jj this latest version)


Jan 9 2018, 3:30 am jjf28 Post #23

Cartography Artisan

Converting the memory condition to use memory addresses as the first parameter by default, Chkdraft users will have the option to change a setting to use playerId in the memory condition/actions, let me know if LIT should have it set to use playerId by default or if you want to update LIT or what not.

Rs_yes-im4real - Clan Aura -

Reached the top of StarCraft theory crafting 2:12 AM CST, August 2nd, 2014.

Sep 8 2018, 7:31 pm goobie Post #24

First off, this is fantastic!

I would request that death counters are allocated for units that cannot be killed first, such as "Goliath Turret" or "Nuclear Missile". After the list of unkillable units is exhausted, then LIT could generate a warning when it's finished compiling.

As it stands the first death counter allocated is "Protoss Gateway", and the first several at least are units that can be killed during play, depending on the map. I'll probably implement this change to a local copy of LIT for a map I'm working on, if you want the changes.


P.S. Also, allowing allocation of death counters by playergroup! So each player in the playergroup gets a dc, and when a playergroup dc is used in a trigger, it generates triggers for players using their specific death counter. Kind of like "Current Player" behaves.

Post has been edited 1 time(s), last time on Sep 8 2018, 7:36 pm by goobie.

There's got to be something more to life than being really, really, ridiculously good looking...

Sep 9 2018, 4:53 am goobie Post #25

Ok, I've looked at Lock.lua pretty closely. I did find a couple issues. First, it seems that some unit names available for death counters include several spaces in a row, such as "Duke Turret type 1". It seems whatever you used to pull the strings killed the extra spaces, so Lock.lua has "Duke Turret type 1", which won't compile in trigedit.

The good news is, this always happens after the string "type", so a find-replace should fix all instances. The bad news is, some valid units with this space typo look like they've been removed to make the triggers compile. I have a modified Lock.lua with the complete unit list, with both problems fixed if you'd like it.

Finally, I don't believe we want to allocate death counters for "Any unit", "Buildings", "Factories", or "Men", which appear at the end of the list in Lock.lua


Edit: I made the changes to Lock.lua, let me know if you'd like the file!

Post has been edited 4 time(s), last time on Sep 23 2018, 7:38 pm by goobie.

There's got to be something more to life than being really, really, ridiculously good looking...

  Back to forum
Please log in to reply to this topic or to report it.
Members in this topic: None.
[09:10 am]
Zycorax -- You can buy little things like name colours.
[07:52 am]
IlyaSnopchenko -- What do the minerals do, anyway :)
[06:47 am]
O)FaRTy1billion[MM] -- I think I still have a couple dat files to finish, and people have complained about save games being broken with it D:
[06:46 am]
O)FaRTy1billion[MM] -- not as big of a pain as updating the static arrays in SC's code, I imagine
[06:14 am]
Suicidal Insanity -- FaRTy1billion
FaRTy1billion shouted: Suicidal Insanity dat files are easy though :( datext just scales the file to the new number of dat entries, and then gets rid of silly things like restricting only certain IDs having certain properties (mostly to make it easier for scaling)
Well I have static arrays and consts for the lengths that are used in dozens of places, just a pain to update. And many dat files have like 3 or 4 different lengths that they use
[06:03 am]
Corbo -- i am gonna sue you!
[06:02 am]
O)FaRTy1billion[MM] -- my minerals have been as low as like 200, so who knows lol
[06:02 am]
O)FaRTy1billion[MM] -- or maybe it was when I bought the name glwo
[06:01 am]
O)FaRTy1billion[MM] -- no i probably gave them to somebody else
[06:00 am]
Corbo -- You fell into your gambling addiction again, didn't you? :mad:
Please log in to shout.

Members Online: Roy