Make limits to push

ok theres lots of complaints from pushing for and against so im thinking add push but make a limit to how far they get pushed
itll be crazy if when you wan a battle one shot and you have to wait 50 hours to get back to where you were to fight again instead make push range only 5 metres(metres to scale)
then you wouldnt have to wait so long and then there would be lessened complaints

abuse report people who do this. end of story.

a feature meant for 1.6 that got axed prevented people from being tossed multiple sims. hopefully it'll make its way into 1.7 and this will be moot

But, limiting scripting tools is not good.

yes cut peoples intead of cut scripts

I know there are useful applications for llPushObject(); however, how many of you have actually seen it used other than griefing? There definitely needs to be some thought put into this function. A limitation on it's range does seem to be a plausible solution.

Also, possible a die at border function automatically for items with damage/push? I know that's less likely, but owning land next to a damage sandbox (Rausche) I'd definitely appreciate something that prevents stray bullets, not to mention the troublemakers that thikn because they are standing in a combat sim that gives them the right to shoot anytihng in sight, in any sim.

Yep - my trampoline, my mosh pit, a project I'm working on to let you actually swim in swimming pools, my super jump attachment.

Just about every fireworks display.

Just to name a couple.

I don't like the idea of limiting script functions either.

I am however, in favor of a Land feature to toggle push on/off for the parcel (with a height restriction) - and/or an avatar toggle on/off for push effects.

I'd think that would allow everyone to have what they want.

Check out Prop 244

Yah, I've written somewhere else in forums about maybe a push_object(integer push) event where push = TRUE/FALSE. Though it will only be defeated when every jsut changed their bullets to llTeleportAgentHome() methods (what's the good use for this again?)

Personaly, I'd simply like to see llPushObject be even remotely _PREDICTABLE_!

I use it to push Avs out the side of vehicals so they get out by the doors rather than up through the roof.

I hate that it only works properly maybe 25% of the time and actualy places the AV just outside the vehical in the correct location.

Often, it does absolutely nothing, the rest of the time it fires me 1/2 way across the sim when I stand up...

If there is any other way a scripted prim can affect an Avs position that it is not attached to, I'd LOVE to know how.

Racer P.

I'm working with llPushObject to make a large scale intra (or even inter) sim transportation system. Range restrictions would kill it dead.

I've made some discoveries about the effectiveness of the push, when applied to avatars. IM me in game if you're interested.

it would be better to allow us to have a mode where we can not be effected by other peoples weapoons and mabey to go as far to say just like how the debug menu has a show no paticles option a option to not have certain people particles to show especaly those who like to nuke every thing and use exit paticles that spam every where.

put a end to attention whores

I'd like a pushed(vector impulse) event available. This could:
- make combat systems much easier to create
- enable excellent, if not perfect, antipush.

I'd throw votes at this proposal.

Hmm. How about:
pushed(vector impulse, key object_id)

I think making it work like the touch event could be good for consistency (consistiwha- ? In LSL ? Surely I'm joking, eh ):
-> void pushed(integer count)
with llDetectedImpulse(integer number) for getting the push, llDetectedKey(integer number) for getting the key of pusher, etc...

[Edit] Proposal number is 500