Staredit Network > Forums > Modding Assistance > Topic: Stasis Field
Stasis Field
Jan 1 2009, 10:09 am
By: Devourer  

Jan 1 2009, 10:09 am Devourer Post #1

Hello

Hi everyone...
I'm currently testing around with scaiedit31 and I want to make a new AI script running at location like Recall, just for Stasis field. Here is what I've got:

Code
; ASC3 File generated by ScAIEdit III
;
; Script name : Stasis Here

script_name Stasis here
script_id SFhe

stasis_field
stop


If I check for errors this error appears:
Code
1 error message

(8) Error! Command 'stasis_field' undeclared.


anyone help me? \:\)

EDIT: Is there an alternative for importing it to the aiscript.bin than StarDraft (It's outdated)

Post has been edited 1 time(s), last time on Jan 1 2009, 12:12 pm by DeVouReR.



Please report errors in the Staredit.Network forum.

Jan 1 2009, 6:50 pm bajadulce Post #2



as for your error, SCAIEdit is in fact the culprit. That particular spell has a "spelling" error. SCAIEdit's unitdef.ini lists Stasis as "STATIS" with a "T". You would need to use the "t" in your scripts. i.e. statis_field or change the unitdef.ini. Another example of why PYAI is far superior to SCAIEdit as it uses stat_txt.tbl labels. In fact, I can't confirm scaiedit's mispelled unitdef.ini. I'm only going on what I remember simply because I no longer have the program installed on my computer anymore. Just as I don't have Arsenal 3 or StarDraft etc, I have axed scaiedit entirely in favor of pyai. The 2 programs are night and day.

As far as creating a "statis here" script that will work similar to the nuke script, I have no clue as to how that would work, but am very curious as to the outcome of your findings. Good luck with your experiments and please report back.

Edit:
Confirmed that SCAIEdit uses "statis_field" .. I just looked at PYAI's external unitdef.ini file.. i.e. importing SCAIEdit commands.



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
[2026-6-20. : 6: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: Cinolt, armitage