Reply to Re: Strange glitch
If you don't have an account, just leave the password field blank.
Tyrsis is absolutely correct - I've tested the module and the bug is introduced by the sword script, from the moment you equip it. It tries to load the sword frames over the unequipped frames, doesn't find enough frame slots and for some unfathomable reason places the extra frames over the top of the next created sequence.
In this case, you should be able to fix the problem by going in to dink.ini and having it load dink/sword/idle instead of sword/idle. That way the higher frame limit will be set, and the unequipped graphics will be loaded anyway as you start the game with the fist.
Note that it's the idle sequence - 18 - that's the issue, not the attack sequence.
In this case, you should be able to fix the problem by going in to dink.ini and having it load dink/sword/idle instead of sword/idle. That way the higher frame limit will be set, and the unequipped graphics will be loaded anyway as you start the game with the fist.
Note that it's the idle sequence - 18 - that's the issue, not the attack sequence.
