Sword Script

I been looking for a sword script that allows you to use your mouse instead of your keyboard and/or "timed attacks" eg that of a RPG game. If both are possible add changeable modes with hopefully changeable channels and settable attack time, that also work with any combat meter safe zone compatible. With blood splat upon contact with "oozing" blood if I’m killed, with a working shield that deflects damage with on/off and settable damage deflection commands all legal gor combat and low lag scripts hopefully with sword sheath and shield linked together with two unsheathe commands. One with sword unsheathe the other for sword/shield unsheathe with a dark blue handle, and gold grip with dark blue sheath with gold strap slung over right shoulder going under left arm, sword with a blue sheen with leather shield. If you need My measurements IM Me

1)
Learn what a comma is
2)
Learn what a period is

Hey, Jeremy,

Let's go through your request point by point. Unfortunately I don't have time to script this for you as I am already working on a similar project, but perhaps I can assist you in helping to map out the concepts a little. Of course, my suggestions are only that-- suggestions.

In order for your sword to use the mouse instead of the keyboard, you'll want the script in the sword to take control of the user's mouseclicks.

Both mouse-driven and timer-driven models are feasible. To be able to switch modes between them, your scripter might consider putting each one within its own state. To toggle between states, you could either use a touch handler or a listen handler keyed to your UUID. Personally, though, I tend to think that a dialog-based interface is much more elegant when done properly.

Changing the period between attack times is a great way to add depth to combat. You could do this by declaring a time_until_next_attack global variable, then various functions could update the period between attacks based on damage you take, commands you issue, or whatever.

Now, since you want the system to be safe-zone compatible (a design decision that I completely agree with), you'll probably not worry too much about declaring damage. Instead, you would probably want to have the sword script communicate via chat on a nonzero chat channel so that it doesn't spam other users into weeping-and-gnashing-of-teeth-mode. Let's be honest, our world is a better place with less chat spam. In order to keep those chat communications secure so that users can't hack your sword system (pun intended), you may want to periodically randomize the channel you use to make things a little harder. Unfortunately, we're stuck with using chat until LL provides secure object-2-object communication. Until then, one does what one must, ne?

The blood spattering is viscerally satisfying entertainment. Hey it worked for the Romans and for ECW fans alike. To accomplish that, many developers turn to using particles. Please don't forget to turn OFF the particles by passing llParticleSystem([]) ! Otherwise, you'll look like a hemophiliac in a mosh pit. Not good. Personally, I find that adding flinch, double-over, or collapse animations really adds a lot to the experience.

Implementing the shield will depend a whole lot on how the rest of the system is defined. If players are getting hit by physical objects, then shielding is a vast and complex artform. If, however, the damage is being passed via chat, you can simply tell the script that receives the damage information to set an accept_damage_notification integer variable to FALSE, and then have it simply ignore incoming damage when FALSE is indeed the case.

I don't know much about Gor and what passes for legal combat scripting there. Based on my decidedly limited understanding of how female characters are treated in those settings, I'm not sure I WANT to know. But that is another discussion for another forum and time. Back to the matter at hand!

Making the scripting implementation low lag comes down to two matters in this case: how much chat data are you passing, and how hard are you using sensor data to help the script know about its environment? An elegant implementation, I would suggest, needs only a single permanent listen on a nonzero channel and no sensor events. Your mileage is guaranteed to vary on this one and depends a lot on the particulars of how you get it done.

As for sword drawing and sheathing, the typical solution is to change the alpha (transparency) on concurrent drawn and sheathed sword attachments. Inelegant, perhaps, but effective enough when slaved to a decent animation.

As for the specific colors and measurements of your weapons and accoutrements, I commend your fashion taste, as I have none myself.

Good luck with your project!

thank you for the help but I know nothing about scripting, but, what you said sounded cool lol. It sounds like a lot of work though.

It is a lot of work, yeah. And I think it is important to be upfront about that. On the other hand, it can be really, REALLY rewarding to enjoy the fruit of your labor in learning to script.

Start simple and work your way to your goal. You can do it! And as questions arise, I think you'll find lots of nice folks here on the forums willing to help answer those questions for you.