Well, since the core script is tested, too, i can reveal the project a bit, but without much details. The project is actually the sequel of RLV teleporters (thus 'RTP'.) This technology uses the RLV api to move an avatar gridwide most comfortable (locally is also posible.)
Most important extensions: Predefined target lists to scrol through. Extensible architecture via open APIs. The sensor reacts not only on touch and collision, but also on sit, entering scanned area or chat command.
The core script itself performs only the teleport. Scrolling through targets is matter of the target list script. Its job is delivering the target data inclusive global coordinates to the core script. Next image shows the process map of the target list script.
There are two kinds of Teleports: On predefinded targets or via DirectTP. Up to 80 targets can be defined in the configuration, with a landmark or slurl to the target place and preview picture. The target coordinates the script requests from servers and saves for later.
Since sims move sometimes, the coordinates expire (e.g. after a week) and must be requested again. This process is displayed in blue.
In DirectTP, the target coordinates are delivered in the command itself, the core script can start the process immediatelly. For more comfort, the target list offers a resolving service: You give it a slurl and the scrpt builds a command with resolved coordinates. This process is shown in green.
Im both cases, the script uses a sim cache. Here positions of 16 sims are saved that were resolved last. For teleports to sims saved here, the access time decreases and SL servers are discharged.
For teleporters that don't use predefined targets, but run on DirectTP only, there is also a simplified target list script. This script manages no targets and uses only the green part in the picture. The script uses about 20kB less memory and is called '.directTP' while the regular target list is called '.targets'.
The future: Next part are integration tests. Here i will build teleporters for all five triger events, thereunder replaceents for 'TP Sign' and 'TP Mirror' (touch and collision events) and some with scroll buttons and effects like sound and particles. The effects will be realized by open driver scripts.
Greetings and til next time
Hello everyone reading :) This post targets all the people who design and create all the fancy things, be it in hand or on screen. Pleas...
Why a unpacking a box needs a tutorial at all? Before RTS (the newest product by now) the product boxes had a usual unpacker script. That on...
Updating of JFS products is relativelly simple but if you know how. This tutorial should introduce this. First of all, there is only one p...
Hello everyone! It is pretty a while that I posted something last time, but now there are changes about stores and JFS at all (my company...