Staredit Network > Forums > SC1 Mapping Tools > Topic: ProTrig @include function
ProTrig @include function
Aug 10 2010, 7:09 am
By: goobie  

Aug 10 2010, 7:09 am goobie Post #1



I'd like to make a .protrg file which implements common triggers as functions, so that I don't have to write them out for every map.

Here is my current .protrg file
Code
def hyper(x, y):
   
    HyperTrig = Trigger(x, add=False)
   
    Always()
    for Timer in range(63):
        Wait(0)
    PreserveTrigger()
   
    for i in range(y):
        HyperTrig.addTrigger()
       


Now I try using @include to import the Hyper function into another .protrg file
Code
@include ProTrigFunctions.protrg

hyper(8,3)


And this is the resulting file
Code
//------------------------------------------------------\\
// Generated by ProTRG v1.1 on Tue Aug 10 00:53:18 2010 \\
//------------------------------------------------------\\


Traceback (most recent call last):
 File "ProTRG.py", line 1571, in <module>
 File "ProTRG.py", line 1531, in main
IndexError: list index out of range


I've tried saving ProTrigFunctions.protrg in the Notepad++ directory, and also tried listing the full file extension in @include, but this didn't work either.



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

Aug 10 2010, 11:25 am Cinolt Post #2



I reported the same problem but no fix has been made; for now you just have to copy and paste it all into one file. I've written a protrg script that has all the functions I would think a mapper would need here.



None.

Aug 10 2010, 2:45 pm CecilSunkure Post #3



You can use the include keyword and import from a .py module instead of using the @include function. Just save your separate protrg file as a .py file, and keep your protrg code within it.



None.

Options
  Back to forum
Please log in to reply to this topic or to report it.
Members in this topic: None.
[04:56 am]
Ultraviolet -- I suppose we'll likely never know, but my guess would be that they already saw it operating successfully and there was no monetary incentive to finish the original work. And the dev cycle in old school Blizzard was so hectic, it's possible it just got forgotten about after the original game got released. Plus there's an element of existing MPQ files that were packaged with the original discs becoming outdated if they updated it. And it's not like they remade the original MPQs, they just made new ones for BW specifically
[04:26 am]
Oh_Man -- so that makes me think maybe the theory they are unfinished is not true and its a deliberate design decision, coz why not finish them wen ur making brood war?
[04:25 am]
Oh_Man -- the thing is thos buildings are from classic. that means they went ahead and made brood war without ever finishing the 'unfinished' buildings
[06:15 pm]
Ultraviolet -- Yeah he's talked about a lot of that stuff in his casts before. It seems plausible. Especially knowing how Blizzard of yesteryear operated.
[2026-6-20. : 3:47 pm]
NudeRaider -- to clarify: couldn't recall the behavior for every single Protoss building but I was aware the disparity exists.
[2026-6-20. : 3:43 pm]
NudeRaider -- Contained nothing new for me. Didn't know all building's behavior, but very much all unit's. Also Terran balance whine - also nothing new :lol:
[2026-6-19. : 9:57 am]
Oh_Man -- makes me wonder if SEN knows anything about the topic
[2026-6-19. : 9:57 am]
Oh_Man -- artosis dropped pretty interesting vid: https://youtu.be/EqZHB8Blra4
[2026-6-18. : 5:01 pm]
Ultraviolet -- :wob:
[2026-6-17. : 6:15 am]
RexyRex -- :wob:
Please log in to shout.


Members Online: Prankenstein, RIVE