Mantis Bug Tracker

View Revisions: Issue #8140 All Revisions ] Back to Issue ]
Summary 0008140: new Experimental osTeleportObject
Revision 2017-04-15 03:26 by UbitUmarov
Description I added on master, a new experimental function
integer osObjectTeleport(key objectUUID, vector targetPos, rotation rot, int flags)

arguments:
- objectUUID the id of the linkset to teleport
- targetPos target position
- rot a rotation.
- flags

returns a integer error code:
 - negative the teleport failed
 - Zero means that a teleport to another region was started. result needs to be checked by other means (?)
 - 1 did a local teleport

flags:
OSTPOBJ_NONE it is just 0
OSTPOBJ_STOPATTARRGET object is stopped at destination
OSTPOBJ_STOPONFAIL stops at start point if tp fails (still does nothing)
OSTPOBJ_SETROT the rotation is the final object rotation, otherwise is a added rotation

this are can be combined by binary or | as usual

restrictions:
- ThreatLevel(ThreatLevel.Severe, "osTeleportObject")
- if object has scripts, owner must have rights to run scripts on target location
- object owner must have rights to enter ojects on target location
- target location parcel must have enought free prims capacity for the linkset prims
- all avatars siting on the object must have access to target location
- has a cool down time. retries before expire reset it, and tp is ignored with error -2
- the object can not be selected at tp time

note that you need to make sure the object may physical rez on the target position. Any collisions like from rezing inside another object may have ugly results.

teleports to other regions may depend on viewers and may go very wrong.
they can take time, and sitting victims may see ugly things until done

if you have the time to test, let us know the many ways how it does crash your test regions and your prims ;)

code is not final, restrictions are to enforce the normal parcel permissions, to prevent bad use, etc, and are not final.


Revision 2017-04-15 03:24 by UbitUmarov
Description I added on master, a new experimental function
integer osObjectTeleport(key objectUUID, vector targetPos, rotation rot, int flags)

arguments:
- objectUUID the id of the linkset to teleport
- targetPos target position
- rot a rotation.
- flags

returns a integer error code:
 - negative the teleport failed
 - Zero means that a teleport to another region was started. result needs to be checked by other means (?)
 - 1 did a local teleport

flags:
OSTPOBJ_NONE it is just 0
OSTPOBJ_STOPATTARRGET object is stopped at destination
OSTPOBJ_STOPONFAIL stops at start point if tp fails (still does nothing)
OSTPOBJ_SETROT the rotation is the final object rotation, otherwise is a added rotation

this are can be combined by binary or | as usual

restrictions:
- ThreatLevel(ThreatLevel.Severe, "osTeleportObject")
- only does teleport local to region
- if object has scripts, owner must have rights to run scripts on target location
- object owner must have rights to enter ojects on target location
- target location parcel must have enought free prims capacity for the linkset prims
- all avatars siting on the object must have access to target location
- has a cool down time. retries before expire reset it, and tp is ignored
- the object can not be selected at tp time
fail conditions are silent ignored

note that you need to make sure the object may physical rez on the target position. Any collisions like from rezing inside another object may have ugly results.

teleports to other regions may depend on viewers and may go very wrong.
they can take time, and sitting victims may see ugly things until done

if you have the time to test, let us know the many ways how it does crash your test regions and your prims ;)

code is not final, restrictions are to enforce the normal parcel permissions, to prevent bad use, etc, and are not final.


Revision 2017-04-15 03:05 by UbitUmarov
Description I added on master, a new experimental function
integer osObjectTeleport(key objectUUID, vector targetPos, rotation rot, int flags)

arguments:
- objectUUID the id of the linkset to teleport
- targetPos target position
- rot a rotation.
- flags

returns a integer error code:
 - negative the teleport failed
 - Zero means that a teleport to another region was started. result needs to be checked by other means (?)
 - 1 did a local teleport

flags:
OSTPOBJ_NONE it is just 0
OSTPOBJ_STOPATTARRGET object is stopped at destination
OSTPOBJ_STOPONFAIL stops at start point if tp fails (still does nothing)
OSTPOBJ_SETROT the rotation is the final object rotation, otherwise is a added rotation

this are can be combined by binary or | as usual

restrictions:
- ThreatLevel(ThreatLevel.Severe, "osTeleportAgent") ( yes im lazy, will change to its own thing)
- only does teleport local to region
- if object has scripts, owner must have rights to run scripts on target location
- object owner must have rights to enter ojects on target location
- target location parcel must have enought free prims capacity for the linkset prims
- all avatars siting on the object must have access to target location
- has a cool down time. retries before expire reset it, and tp is ignored
- the object can not be selected at tp time
fail conditions are silent ignored

note that you need to make sure the object may physical rez on the target position. Any collisions like from rezing inside another object may have ugly results.

teleports to other regions may depend on viewers and may go very wrong.
they can take time, and sitting victims may see ugly things until done

if you have the time to test, let us know the many ways how it does crash your test regions and your prims ;)

code is not final, restrictions are to enforce the normal parcel permissions, to prevent bad use, etc, and are not final.


Revision 2017-04-04 06:46 by UbitUmarov
Description I added on master, a new experimental function
osObjectTeleport(key objectUUID, vector targetPos, rotation rot, int flags)

arguments:
- objectUUID the id of the linkset to teleport
- targetPostarget position
- rot a rotation.
- flags

flags:
OSTPOBJ_NONE it is just 0
OSTPOBJ_STOPATTARRGET object is stopped at destination
OSTPOBJ_STOPONFAIL stops at start point if tp fails (still does nothing)
OSTPOBJ_SETROT the rotation is the final object rotation, otherwise is a added rotation

this are can be combined by binary or | as usual

restrictions:
- ThreatLevel(ThreatLevel.Severe, "osTeleportAgent") ( yes im lazy, will change to its own thing)
- only does teleport local to region
- if object has scripts, owner must have rights to run scripts on target location
- object owner must have rights to enter ojects on target location
- target location parcel must have enought free prims capacity for the linkset prims
- all avatars siting on the object must have access to target location
- has a cool down time. retries before expire reset it, and tp is ignored
- the object can not be selected at tp time
fail conditions are silent ignored

note that you need to make sure the object may physical rez on the target position. Any collisions like from rezing inside another object may have ugly results.

Possible in future the target position maybe on a near region.
Eventually a form may be added for full teleport on same grid.
HG... see a few issues to solve first.

if you have the time to test, let us know the many ways how it does crash your test regions and your prims ;)

code is not final, restrictions are to enforce the normal parcel permissions, to prevent bad use, etc, and are not final.


Revision 2017-04-03 19:05 by UbitUmarov
Description I added on master, a new experimental function
osObjectTeleport(key objectUUID, vector targetPos, rotation rot, int stop)

arguments:
- objectUUID the id of the linkset to teleport
- targetPostarget position
- rot a rotation to apply during tp, including to velocity, etc
- stop if TRUE (!=0) stop at destination

restrictions:
- ThreatLevel(ThreatLevel.Severe, "osTeleportAgent") ( yes im lazy, will change to its own thing)
- only does teleport local to region
- object owner must have rights to run scripts on target location
- object owner must have rights to enter ojects on target location
- target location parcel must have enought free prims capacity for the linkset prims
- all avatars siting on the object must have access to target location
- has a cool down time. retries before expire reset it, and tp is ignored
- the object can not be selected
fail conditions are silent ignored

note that you need to make sure the object may physical rez on the target position. Any collisions like from rezing inside another object may have ugly results.

Possible in future the target position maybe on a near region.
Eventually a form may be added for full teleport on same grid.
HG... see a few issues to solve first.

if you have the time to test, let us know the many ways how it does crash your test regions and your prims ;)

code is not final, restrictions are to enforce the normal parcel permissions, to prevent bad use, etc, and are not final.
Revision 2017-04-03 19:02 by UbitUmarov
Description I added on master, a new experimental function
osObjectTeleport(key objectUUID, vector targetPos, rotation rot, int stop)

arguments:
- objectUUID the id of the linkset to teleport
- targetPostarget position
- rot a rotation to apply during tp, including to velocity, etc
- stop if TRUE (!=0) stop at destination

restrictions:
- ThreatLevel(ThreatLevel.Severe, "osTeleportAgent") ( yes im lazy, will change to its own thing)
- only does teleport local to region
- object owner must have rights to run scripts on target location
- object owner must have rights to enter ojects on target location
- target location parcel must have enought free prims capacity for the linkset prims
- all avatars siting on the object must have access to target location
- has a cool down time. retries before expire reset it
fail conditions are silent ignored

note that you need to make sure the object may physical rez on the target position. Any collisions like from rezing inside another object may have ugly results.

Possible in future the target position maybe on a near region.
Eventually a form may be added for full teleport on same grid.
HG... see a few issues to solve first.

if you have the time to test, let us know the many ways how it does crash your test regions and your prims ;)

code is not final, restrictions are to enforce the normal parcel permissions, to prevent bad use, etc, and are not final.


Copyright © 2000 - 2012 MantisBT Group
Powered by Mantis Bugtracker