Important note:

As noted by sninksnoodle on Oct 27, 2020, Yandex does not provide free API keys anymore (#1). The main goal of this fork was to provide an free alternative to Google Translate, so the project is now obolete.

However, this code also fixed a couple of bugs in the available version of Hank Hamos Universal Translator (which dates 2015), so it might be worth to catch and bring these fixes to the Google Translate version.

Original readme

• Authors: ©2016 Gudule Lapointe gudule@speculoos.world
• Based on Universal Translator 1.9.0 (Google) ©2006-2009 Hank Ramos
• License: AGPLv3
• Source: https://git.magiiic.com/opensimulator/Universal-Translator-Yandex

It is based on the excellent Universal Translator by Hank Ramos. However, the initial version was using Google translation engine API and Google decided to switch to a paid license. So I rewrote some parts of the code to use Yandex engine instead.

Get the latest version in Speculoos’ grid speculoos.world:8002:Lab or on the git repository https://git.magiiic.com/opensimulator/Universal-Translator-Yandex (and if you make improvements, please share them there)

New features

• It’s working! No kidding: the version available on LSL scripts wiki and on other sites like Outworldz is incomplete and not ready to work, even taking apart the Google license issue.
• Use Yandex translation API. It is not only free (while Google isn’t anymore), but it is easy to get an API key (while it’s quite complicate with Google or Microsoft API’s).
• The API key is not hardcoded but instead stored in a notecard. This avoids a single key being spread everywhere and causing "maximum allowed requests reached" kind of messages.

DO NOT DISTRIBUTE THE TRANSLATOR WITH THE API KEY. It could end up being used by dozens of users, and becoming useless.

Main (and not so new) features

• Multiplex mode: if several translators are in the same area, one becomes the master and makes actual translation requests for the other ones. This avoid overload when lot of people are present and using it.
• Speaker language auto detection (though users can also choose their language manually)
• Translations sent by instant messages, no spam on the public channel
• Can be used as an object in the parcel or as a HUD.
• Can use both an object in the parcel and people wearing HUD, without spamming public channel, nor overloading the servers and the API key limits.

To do

• Get an updated list of available languages ✓ A (beautiful) texture and logo
• Detect the most used languages and show them at beginning of the list
• Allow to set a fixed list of preferred languages to show first (probably before the auto-detected mostly used ones).

Notes

We use a dedicated function json2List instead of llJson2List (not compatible with 0.8). It’s a little bit rough, but it works.

An update ecosystem to allow OpenSimulator scripts to self-update. It should also work in Second Life with a small tweak (see below).

Installation

• ScrupServer: the lsl server script, to put inside an in-world object. The object will also contain non-running copies of the latest versions of the scripts to update.
• ScrupClient: The portions of code to include own script. It is intended to be lightweight, we don’t want it to get bigger than the script itself.
• Web application: the rest of this repository. It will allow both client and server to register an exchange the needed information for updates.
• Database: scrup use a sqlite database for efficiency only. It will be created automatically in PHP tmp_dir (or upload_tmp_dir). It stores only runtime data sent by server and client, so it can get deleted or lost without real harm.

In the client script:

• copy the variables and the scrup() function as is in your script (also include debug() function if you don’t have one)
• please include a credit line at the beginning, after yours
• insert scrup(ACTIVE) at beginning of default state_entry() and on_rez() (the latter only if you don’t use llResetScript)
• use scrup(FALSE) to stop updates at any time in your script (for example, while executing a task that should not be interrupted). The authorization pin will be revoked and a new one will be generated on scrup(ACTIVE) or scrup(TRUE)
• use scrup(TRUE) or scrup(ACTIVE) to resume normal operations (value of scrupAllowUpdates is still honored)

Status

This is a work in progress and more like a proof of concept. Updates are functional, but…

• only if the server and the object are in the same region (you can wear the object and TP to the region hosting the server, though, and even wear the server and visit the regions where objects need update)
• only one client can be present in a prim (several can if each one is in a different prim of the same object, though)
• there are no verifications (allowed grids, owners, creators), so it should probably not be used at a wide scale. Yet.

Second Life

The only OSSL function used in scripts is osGetGridLoginURI(), in , which is useless in SL. So to make the script work in SL, replace the function by a fixed value "secondlife://" (detailed explanation in the scripts comments).

Roadmap

• Let ScrupServer script update itself too
• Let two ScrupServers exchange their latest versions
• If there are no updater in the same region, send a message notification to the owner
• Or better: send an updater box to the owner as a workaround to region limitations (wear to update)
• Allow bundles (all scripts in an object + other inventory items), mix with updater box concept
• Find a f* way to send updates to other regions (let’s forget other grids for now)

OpenSim script to let NPCs be attracted when someone sits on an object Made

by Gudule Lapointe @ speculoos.world:8002

This is not my best achivement, but I find it quite funny. If you use NPCs in your region, put this script in one of the animated objects, and NPCs passing by will one by one come together to watch when someone sits on it.

You can fix the scan radius, the distance they keep from the watched avatar, the occuppied angle (360 for all around, smaller to get them more in front), adjust rotation (to get them on the side, on front or rear), and make them change dress when they watch.

Sometimes, an NPC is too far and cancel its move right before being in place so it disappear and go back to its initial position. It’s a bug, but it adds some randomness, so it sounds fair to me.

Requirement

It uses only standard LSL functions, but rely on an NPC server, which means it’s only relevant in a region where OSLL NPC functions are enabled.

Installation

1. Have already an NPC rezzer box, "OSW NPC" or "ActiveNPCs"
2. If you want custom dresses, add correspondig notecards in the NPC box, as

  APP_Npcname_Dressname

3. Put the script in any object where visitor sit, alongside the original script. You can put custom settings in the object description, in the form:

  searchRadius, minRadius, maxRadius, spreading, orientation, changeDress

The script is auto-updating (in limited conditions). So either don’t change anything in the script, either disable auto-update to avoid losing your changes.

Foot notes

• If you setup a custom dress, ensure that you have a matching NPC notecard for each one in your NPC rezzer, otherwise you will get annoying system errors.
• This script is intended to work with "OSW NPC" or "ActiveNPCs" (the latter being an enhanced version of the original). I made a fix for the error messages issue mentioned above, its available on https://github.com/GuduleLapointe/active-npcs-ef-Gudz-mods
• If you distribute this script, include this README and credits
• If you make changes, please share with me so I can improve the original

Have fun! (and let me know about it)

This script acts as an AI assistant, powered by OpenAI’s GPT-3.5 Turbo language model, designed to interact with users in an OpenSimulator virtual world. It listens to chat messages, processes user queries, and responds with appropriate answers.

The script is intended for OpenSimulator and requires the following OSSL functions to be enabled:

• osGetNotecard()
• osIsNpc()
• osNpcSay()

Usage

1. Include this script in an object in your OpenSimulator virtual world.
2. Create a notecard named "~api_key" in the same object containing the API key to access OpenAI’s GPT-3.5 Turbo.
3. Create a notecard named "~context" in the same object containing your world specific context for the assistant.
4. After initialization, the assistant will listen to user messages containing its name and respond accordingly.
5. Users can interact with the assistant by addressing it with its name and asking questions or giving commands.

Special Commands (to be interpreted and handled by the AI)

The script utilizes the AI to recognize certain requests and instructs the AI to include specific keywords in the answers. These keywords enable the script to process the responses differently.

• %not_for_me% will inform the script that the message is not intended for it and the answer should not be processed.
• %quit% will instruct the script to end the chat and respond with a farewell message.
• %sit% or %follow% will instruct the script to answer accordingly, assuming the user typed the commands with the appropriate syntax for a third-party script ("use" and "follow me" for NPC Manager). In a future release, the script will forward the appropriate command to an external script (NPC Manager) which will handle the requested NPC actions.

Notes

• This script requires an API key to access OpenAI’s GPT-3.5 Turbo API. Make sure to keep the key secure and to not include it in the version you might reditribute.
• The script keeps a log of user and assistant interactions, limited to the number of messages set by LOG_LIMIT.
• The assistant will listen to chat messages until 180 seconds of inactivity or a request to end talking, after which it will stop listening until it is called by its name again.
• Any message starting with a slash ("/") is ignored as it may indicate a command for other purposes.
• The assistant’s responses are subject to the capabilities and limitations of the GPT-3.5 Turbo language model.
• This version is an early release, and improvements or bug fixes may be needed based on user feedback.

Feedback and Issues

For feedback or issues, please see GitHub Repository.

Get the latest version: https://git.magiiic.com/opensimulator/Gudz-Teleport-Board-2

• Authors: Gudule Lapointe gudule@speculoos.world, Olivier van Helden olivier@van-helden.net,
  Portions of code by the owner of Avatar Jeff Kelley, 2010
• Source: https://git.magiiic.com/opensimulator/Gudz-Teleport-Board-2
• Website: https://speculoos.world/lab
• Licence: AGPLv3 (Affero GPL)

Features:

• Single or Multi-columns teleport buttons
• Destinations statuses are checked at start and every hour to avoid TP to inactive regions
• Local destinations can be written as HG links and are automatically converted to local links for teleport, so the same board works inside and outside your grid
• Destination source can be set from a notecard or from a web server
• Immediate TP or map (change USE_MAP in config)
• Different colors for current region (green) or offline regions (red), customizable
• Optional background texture
• Can be formatted with titles (text without url), spacer (|) and column jump (-)
• Configuration in a separate notecard to allow easy upgrades
• Long click by the owner to force a full reload

Setup

The destination list can be set by 3 ways

• from an external website: put the URL in prim description (only the first 2048 bytes will be loaded)
• from a specific notecard: put "card://CardName" in the description
• fallback if none of the two first method: read the first notecard found.

In previous versions, the destination list used 5 values. We accept this old format for backward compatibility but we recommend the simplified format:

• Displayed Name|your.grid:port
• or Displayed Name|your.grid:port:Region Name
• or Displayed Name|your.grid:port:Region Name|x,y,z

Comments and formatting:

• Empty lines are ignored
• Lines beginning wish "#" are ignored
• Lines commented with "//" are sent as message to the owner during initializaton
• Lines containing only a string (and no url) are drawn as simple text (section titles)
• Lines containing only a separator ("|") are drawn as an empty line (spacer)

Although commenting lines is useful to disable them temporarily (#) or display help messages (//), it slows down the initialization, so it is better to avoid it as much as possible.

Required OSSL Functions:

• osGetGridGatekeeperURI
• osGetNotecard
• osTeleportAgent
• osSetDynamicTextureDataBlendFace and related (osDrawFilledRectangle, osDrawRectangle, osDrawText, osGetDrawStringSize, osMovePen, osSetFontName, osSetFontSize, osSetPenColor, osSetPenSize)

This script is designed for managing free land rentals in OpenSimulator, ensuring tenants maintain a regular presence to prevent users from making land unavailable without actually using it.

In the future, this script will be adjusted to also handle paid rentals.

Features

• Free Land Rentals: Allows users to rent land for free, requiring them to click regularly on the rental panel to keep the parcel.
• Full Ownership: The land is technically sold to the user, giving them full ownership and control over their parcel without needing group tricks.
• Automatic Reclaim: Expired or abandoned land is sold back to the vendor owner.

Requirements

The script requires these functions to be enabled for Estate Owners in OpenSimulator configuration:

• osDrawText
• osGetDrawStringSize
• osGetGridGatekeeperURI
• osGetGridLoginURI
• osGetNotecard
• osInviteToGroup
• osKey2Name
• osMovePen
• osSetDynamicTextureDataBlendFace
• osSetFontName
• osSetFontSize
• osSetParcelDetails
• osSetPenColor

Usage

For Tenants

1. Initial Rental: Click on the sign, read the rental conditions, and confirm the rental.
2. Renewal: Before the end of each term, click on the sign to renew the rental.

For Region Owners

1. Estate Settings: Make sure to disable land join, split, and resell in your Estate settings.
2. Placement: Place the terminal outside the rented land, around 1 meter from the parcel border and adjust until the positioning beacon is inside the parcel and appears green.
3. Confirmation: A confirmation message appears. Check the rental conditions (see configuration below) and start renting.

Configuration

Do not modify the script directly, any change would be overriden on next update. Use the notecard or a web URL config file instead.

Using a Notecard

Create a notecard named .config including these settings:

configURL = https://yourgrid.org/rental/example.txt
// If set, the config will be read from the URL and the rest of the notecard will be ignored.

// Base config (required)

duration = 30 // number of days, can be decimal for shorter periods maxDuration = 365 // number of days, can be decimal for shorter periods renewable = TRUE maxDuration = 3650 expireReminder = 7 expireGrace = 7

// Optional

fontname = fontSize = lineHeight = margin = textColor = textBackgroundColor = position = cropToFit = textureWidth = textureHeight = textureSides =

Using Object Description (deprecated)

Put these values, in this order, in the main prim description, separated by commas. Duration, max duration, expire reminder, and expire grace are in number of days.

DURATION,MAX_DURATION,,RENEWABLE,EXPIRE_REMINDER,EXPIRE_GRACE

The empty third field used to be set to MAX_PRIMS, but it is now calculated from the parcel data. It can be left empty to save space (keeping two commas for backwards compatibility).

To Do

1. Fix current functionalities:
   • √ Fix rental not restored after updates (fixed in 1.6.5)
   • √ Fix messages not sent to HG avatars when offline (added notification queue)
   • √ Fix position not saved in rent data, causing new check triggered on reset
   • Keep notification queue after script reset
   • Clear rent data (object desc) if owner changed
   • Clear rental status if parcel changed
   • Shorter rental data format (only save in object desc the live rental data, not settings that are now handled by config file)
   • Also notify owner to clean terrain when abandoned (currently only on rental expiration)

2. Add new functionalities:
   • √ New feature: restore rental, based on prims found in the parcel (1.6.6)
   • Use different prims for sign and renter name, hide and show accordingly, to avoid resizing single prim and allow more creative designs
   • allow setting times in years, months, days, hours
   • Option to limit to local grid avatars
   • Option for maximum number of parcels per user, or maximum area
   • Check that the owner has estate rights before activating
   • Centralized management
     • List available terrains
     • Centralized rental via in-world board
     • Centralized rental via web page
   • Advanced features (requires grid-side API)
     • Option to update terrain for sale status
     • Option to set objects auto return after rental end

3. Add payment system:
   • With local currency
   • On website (via w4os or WooCommerce)

License

This script is provided under the GNU Affero General Public License version 3. See the LICENSE file for more details.