Quote:
|
Originally Posted by Stefan
You can also do ("Complex-Name").omg(stuff). findweapon() and findnpc() have the advantage though that they are not case-sensitive.
The possibility to call code of other Weapon/GUI scripts is good for separating functionality into smaller scripts, instead of having one huge system-script.
|
Yea, it was in my movement script that I'm hoping master storm will help me on. It separates into a lot of weapons. Complete list now is: -system_moving, -system_sidemoving, -system_action, -system_gani, -system_keys, -system_extra.
Moving handles the default dir/dx/dy handling (pretty simple).
Sidemoving handles the sliding off of corners (not as simple).
Action handles grab/push/pull/jump all on the same counter.
Gani handles the default moving ganis.
Keys handles sword and extra commands like whistle and hug
Extra does the extra simple stuff, like bed movement, handling all movement related scripts, etc. The main goal is to have them work mostly independently of eachother. But, seeing that that could lead to a bit of redundant code, it would be better in some cases to have the systems interact with eachother. The action system and the gani system still need a little bit of work before this new movement is released for Classic, as well as a new carry system created. I also would like to document and post this movement on graal.net. I'm just hoping that Master Storm will actually help out a little bit. I've done it all on my own so far.