Report, edit, etc...Posted by IsaT on 2006-08-27 at 21:43:53
Where can I go to actually LEARN iscript? The tutorials are no help since they just tell you what to fill in and dont teach you what your doing.
Also, I did one of the tutorials (with little understanding of what was doing..), but when i play sc on the mod nothing is changed. How are you supposed to put Iscripts into the mod?
Also, I did one of the tutorials (with little understanding of what was doing..), but when i play sc on the mod nothing is changed. How are you supposed to put Iscripts into the mod?
Report, edit, etc...Posted by Voyager7456(MM) on 2006-08-27 at 21:53:37
A good place to learn what the different iscript commands do is the IceCC manual. http://scu.logicalknot.org/ also has a good iscript section.
You have to add the iscript.bin file into your MPQ under scripts\iscript.bin.
You have to add the iscript.bin file into your MPQ under scripts\iscript.bin.
Report, edit, etc...Posted by Lord_Agamemnon(MM) on 2006-08-27 at 22:45:54
Actually, just looking at the iscript can be a good lesson in how some things work. Together with the manual, you should be able to learn quite a bit...also, browsing this forum will probably give you a few examples of good scripts.
Report, edit, etc...Posted by TERRAINFIGHTER on 2006-08-27 at 22:49:01
The Iscript is a command-line programming language, the default headers are used for certain unit commands/controls,
you can create as many extra headers as you want, but the script won't use them unless it's linked by a default header.
when the graphic loads, it starts at the Init header, whenever the graphic is sent a command (move, attack, etc)
or the goto opcode is used, the graphic will move to the new header specified and read the commands from that header,
when the graphic reads the header, it reads them in order from top to bottom, meaning that you'd need to add wait commands in order for it to function correctly, and to prevent crashes.
now as for the commands, here's a textfile I made that should help you out with it.
That explains everything I know about iscripting in a few simple sentences (unlike the manual
),
if you ever have any questions feel free to ask.
you can create as many extra headers as you want, but the script won't use them unless it's linked by a default header.
when the graphic loads, it starts at the Init header, whenever the graphic is sent a command (move, attack, etc)
or the goto opcode is used, the graphic will move to the new header specified and read the commands from that header,
when the graphic reads the header, it reads them in order from top to bottom, meaning that you'd need to add wait commands in order for it to function correctly, and to prevent crashes.
now as for the commands, here's a textfile I made that should help you out with it.
That explains everything I know about iscripting in a few simple sentences (unlike the manual
),if you ever have any questions feel free to ask.
Report, edit, etc...Posted by www.com.au on 2006-08-28 at 05:27:05
It was actually tutorials which explained nothing which taught me..
I just did the mover and voer, then changed little things and slowly understood more and more.
A few things i had to ask though (as in the assistance forum =/ )
I just did the mover and voer, then changed little things and slowly understood more and more.
A few things i had to ask though (as in the assistance forum =/ )
Report, edit, etc...Posted by Syphon on 2006-08-29 at 13:13:24
Always have the command referance handy.
http://scu.logicalknot.org/index.php?title...pt.bin_Commands
http://scu.logicalknot.org/index.php?title...pt.bin_Commands