Reply to Re: DinkC Reference Guide Now Available
If you don't have an account, just leave the password field blank.
A few more things...
On the "Graphics" page, authors are advised to use "load_sequence_now" in init lines for weapon scripts, when in fact load_sequence_now and load_sequence are interpreted the same when used in init lines.
The warning on the scripting entry for init() regarding replacing sequences with a different number of frames might only apply to <=1.07 as well.
Also "HD" is incapable of parsing anything other than load_sequence(_now) in init lines. This means no set_frame_frame or whatever else.
For disable/enable_all_sprites, it's fixed now, however for freedink and 1.08 etc, it would be worth mentioning that it will fail to affect the most recent sprite created.
On the "Graphics" page, authors are advised to use "load_sequence_now" in init lines for weapon scripts, when in fact load_sequence_now and load_sequence are interpreted the same when used in init lines.
The warning on the scripting entry for init() regarding replacing sequences with a different number of frames might only apply to <=1.07 as well.
Also "HD" is incapable of parsing anything other than load_sequence(_now) in init lines. This means no set_frame_frame or whatever else.
For disable/enable_all_sprites, it's fixed now, however for freedink and 1.08 etc, it would be worth mentioning that it will fail to affect the most recent sprite created.
