Now available from the beta section of the Mintor store.     SECOND BETA 27 Feb. 2023

This box contains the components to set up weather (clouds, rain, fog, fine) for your farm. The system has options to allow for adjusting the environment over a parcel or the entire region. It also allows for generating fog, rain, lightning and clouds.

Note that this is the first beta release and is intended for people to test and give feedback. Please give feedback on the group discussion here...

Contents

• SF Water Tower

• SF Umbrella

• SF Weather Board

• SF Weather Repeater

• SF Weather HUD

Setting up

First, you need to put out one copy of the SF Water Tower. This is an updated version of the original weather based water tower (the ‘droplet’) and so if you have one of these you should replace it with this new version. This water tower is the main weather controller and generates the main clouds, so it can look based placed roughly centre of your farm.

The config notecard has some new settings at the end, and you can adjust these to suit your needs. Note that PRIM_RAIN, PRIM_SIZE, PRIM_LIGHTNING and FOG_AGE settings relate to this object, and you can adjust separately for the repeaters as described later.

## New weather related settings ##
#
# Set to 1 to change the environment values for parcel or region as per below setting
CONTROL_ENVIRONMENT=1
#
# Can be parcel or region, not case sensitive
EXTENT=parcel
#
# Not sure this is implemented in browsers yet?
TRANSITION=30
#
# Chance of rain. Can be 0=Never, 1=low, 2=medium or 3=high
RAIN_CHANCE=2            
#
# Set to 1 for prim based rain, 0 for particle rain
PRIM_RAIN=1
#
# Set size of the weather prim if prim rain is active (length, width, height)
PRIM_SIZE=<25, 25, 30>
#
# Set to 1 for prim based lightning flashes or 0 for just light flashes
PRIM_LIGHTNING=1
#
# Set to 1 to have a foggy environment set every now and then
DO_FOG=0
#
# If weather system will produce fog this adjusts the extent of generated particle fog coverage from this prim - larger value makes larger area
FOG_AGE=12

If you choose to have the environment controlled, you must have the correct access permissions for the region or parcel.

The water tower comes with three day cycles assets that will be used for normal (fine) weather, rain and fog. You can replace these with your own if you already have customised your EEP settings. You must make sure that they are named exactly as the originals e.g.

DayCycle_Fine
DayCycle_Rain
DayCycle_Fog

You can ‘add’ the SF Umbrella to wear it. This is hidden away normally, but automatically opens when it starts to rain. It then closes when the rain ends, plus you can touch it at any time to close it.

The SF Weather board can be placed somewhere, so you can see a record of the weather.

Once you have set up this water tower, it will control the weather for the entire parcel or region, but you will only get prim rain around this object. If you wish to have prim rain over your entire parcel/region, you will need to use the weather repeater.

You can place multiple “SF Weather Repeater” objects around the area you are covering. Each repeater can be configured separately via the config notecard

# Set to 1 for prim based lightning flashes or 0 for just light flashes
PRIM_LIGHTNING=1
#
# Set to 1 for prim based rain, 0 for particle rain
PRIM_RAIN=1
#
# Set size of the weather prim if prim rain is active (length, width, height)
PRIM_SIZE=<30, 30, 30>
#
# If weather system will produce fog this adjusts the extent of generated particle fog coverage from this prim - larger value makes larger area
FOG_AGE=120
#
# Set transparency (alpha) integer value from 0=Solid to 10=Clear
ALPHA=8

Note that for the prim size, as you increase the size the rain spacing can start to have gaps in it, so it’s a compromise between how dense you wish the rain to be verses how many repeaters you need to put out to cover your required area. A range of between 15 and 30 seems to give good results, but feel free to experiment.

One way to line up your repeaters is to use the SF Weather HUD. With this you can click on the ‘debug’ button and that should get all the repeaters to start raining. When done, you can click on it again to turn off rain.

Tips & Tricks

Advantages and disadvantages of prim verses particle rain

Prim rain looks great, but you should be aware that when it is raining, the rain prim covers everything so if you try and click on a plant, for example, you may just click the rain prim. This may make harvesting in the rain a bit tricky!

Particle rain doesn’t have this issue, but depending upon your viewer settings and other things in your region, you may find that particle rain isn't always visible, or only appears in some parts of the area you have covered.

Preventing fog in your house

If you have set the weather system to change the environment in your parcel, you will find that it gets foggy even inside your house! You can overcome this by creating a parcel around your house. You can then set that parcel to use the region settings.

Creating your own environments

For more information on creating EEP day cycles, this may be of use:

https://modemworld.me/2020/04/21/tutorial-environment-enhancements-project-eep

This work by Buzzy Cnayl is licensed under a Creative Commons Attribution-NonCommercial-ShareAlike 4.0 International License.
Based on a work at https://satyrfarm.github.io/

Now available from the beta section of the Mintor store.     19 April 2023

This is a rental box that can be set to charge people (with Vivo's)   it can be used to rent houses, land etc

This is the first part of the system with links to the website and rental display boards planned.

Note that this is the first beta release and is intended for people to test and give feedback. Please give feedback on the discussion here...

Setting up

Just rez the rental sign on the parcel to be rented. When someone rents, the sign will add them to the same group it is set to, so it is recomended to set the sign to the same group as the land and also make that group a 'residents' type group.  

Config notecard

The config notecard has the settings you can adjust for the rental conditions.  If you set the cost to something other than 0 then the person renting will need to have enough coins (Vivo's) to rent and then later to renew. Payments of Vivo's are deducted from them and credited to you.

If you set IS_RENEWABLE to 0 then at the end of the rental period the rental box will switch back to 'disabled' and will require you to touch it to reset it ready to make it available again.

; Number of days per rental period
PERIOD=7

; Rental cost in Vivo's for each PERIOD
COST=500

; Can they renew?  1=yes, 0=no
IS_RENEWABLE=1

; Maximum number of total prims on the parcel
PRIMMAX=2000

; Number of days before this claim expires, when a message is sent to ask them to reclaim (if IS_RENEWABLE=1)
RENTWARNING=2

; Number of days allowed to miss claiming before it expires
GRACEPERIOD=2

; Name of the rental terms notecard
TERMS_NC=Lease info

; Default language to use LANG=en-GB

; Set to face to display lease image on
FACE=1

; Add avatar UUID if you wish to only allow one avatar to activate the rental
RESERVED=a123456-abcd-abcd-deff-123123123123

Note:  If a user selects to renew, they are charged for the number of days since they last renewed, even if they are only 1 minute into the 'day'.

Lease info

The lease/rental information is stored on a notecard in the rental box.  By default it is called Lease info and there is an example supplied that you will probably want to tweak for your own situation.

Images

The system uses three texture files which you can replace with your own designs if you prefer, however you must keep the same names:

renewal      Displayed when the renewal becomes due.

available    Displayed when the plot is available for rent.

rented        Displayed when the plot is  rented.

Display board

You will also find a display board. This shows you VivoSim messages such as when someone rents from you and so on.  The VivoSim HUD will also have a built in screen as well.

This work by Buzzy Cnayl is licensed under a Creative Commons Attribution-NonCommercial-ShareAlike 4.0 International License.
Based on a work at https://satyrfarm.github.io/

14.2 Common code

(a) language_plugin

Coming soon...

(b) prod_rez_plugin

Coming soon...

(b) prod_get_plugin

Coming soon...

14.3 addons

(a) kitchen addons

Coming soon...

(b) health system addons

Coming soon...

(b) other addons

Coming soon...

This work by Buzzy Cnayl is licensed under a Creative Commons Attribution-NonCommercial-ShareAlike 4.0 International License.
Based on a work at https://satyrfarm.github.io/

14.1 Concepts

The farming system code has been created in an attempt to make expansion as easy as possible. The main building blocks are:

Plants (plant.lsl)

The plant script is used in all plants, trees, fields etc.  A plant is something that requires a 'water' source in order to grow through the stages of 'new', 'growing' and 'ripe'. When ripe the plant allows for harvest of one item (which can of course be a coalesced object) and then repeats the above stages.  Plants can also produce various by-products such as roots, leaves etc. Plants can repeat the various stages indefinitely if supplied with sufficient water. Plants do not move around (although can be animated).

Animals (animal.lsl)

The animal script is used in all animals. An animal requires both a 'water' source and a 'food' source and grows through the stages of waiting to be born (either in pregnant mother or out in egg form), then baby then adult. Adult animals can give various products such as manure, eggs, feathers, milk etc.  Animals have the option of moving around and can be made to mate. Animals have a finite lifespan and will eventually die of old age even if sufficient water and food are always available to them.  Animals can, however, be turned into 'pets' which are 'low maintenance animals that can be set to not need food/water. Pets do not age so can be kept indefinitely.

Products (product.lsl)

The product script is used in all 'products', that is items that are rezzed as part of another process (such as from an animal or plant, from storage, or from a machine) Products do not contain the product script until they are rezzed, at which point the item doing the rezzing gives the product script to it. This makes it easy to ensure that rezzed products always contain the latest scripts. Products generally have a 'shelf life' but can be stored indefinitely in storage units (putting an item into a store and then taking it out will reset the shelf life to the product's maximum value.)

Storage (storage.lsl)

The storage script is used in all items that have a place to store products. Storage units can be set to store any number of products (i.e 1 or more).  By default, storage units show how full they are in terms of a percentage, but they can also be set to use 'units' e.g. 150/300 if it is desired to store a large number of items in one store. 

Machines (machine.lsl)

The machine script is used in all items that take in one or more products as 'ingredients' and give back a different product after a defined period of time. Machines can be set to run autonomously or require an avatar to be 'seated' all the time the process is running.

Feeders (feeder.lsl  &  feeder_grass.lsl)

There are two feeder scripts, the first allows you to create a simple feeder that only requires a 'water' source for it to work. The second version requires the feeder to hold both water and food. A feeder can automatically top up water and food levels from nearby water sources and storage.  Animals take water and food from feeders as and when they require it.

Storage Wells (storage_well.lsl)

A storage-well is an item that fills up with a selected product over time. As an example, water towers fill up with water. Storage wells can be set to either work independently or to require a source of power such as wind or electricity. Storage wells allow you to take out the product at any time (assuming the level is sufficient for at least one portion). 

Converters (converter.lsl)

Converters take in one or more products and convert them to another. You can only take out the converted product when the conversion process is 100% complete. 

Insects (insects.lsl)

Insects are similar to storage-wells in that they produce a product over time, however, you can only take out 100% of the product. Insects can be set to require something be close to them for them to work. They also can be set with various handling conditions that are required to create the product.

Surfaces (surface.lsl)

The surface code is used to allow products to neatly sit in a certain place. When a product is first rezzed it can be set to look for a particular surface to head to (e.g. food items may look for a table to go to). Note that products on surfaces continue to age in the normal way.

Electricity system

The electricity system uses region messages to collect, distribute and utilize power over an entire region. The various scripts are covered later.

HUD 

The HUD allows for avatars to interact with the farm system such as through eating, washing, resting etc. This is covered later.

This work by Buzzy Cnayl is licensed under a Creative Commons Attribution-NonCommercial-ShareAlike 4.0 International License.
Based on a work at https://satyrfarm.github.io/

Worlds:   R = Regular   G = Gorean

Worlds:
  R = Regular
  G = Gorean

This work by Buzzy Cnayl is licensed under a Creative Commons Attribution-NonCommercial-ShareAlike 4.0 International License.
Based on a work at https://satyrfarm.github.io/

This is a list showing the various ideas that are on the development to-do list for growing and improving the Quintopia system.

Exchange

• Add a Search box on the Buy menu  [released Ver 5.7]
• Have a description shown for your farm on the exchange  [released Ver 5.7]
• Version checking so you know you have the latest exchange [released Ver 5.7]
• See exchanges on the Quintopia website [in alpha]

Hud

• Option to allow saving and restoring settings  [released Ver 5.5]
• Allow saving food/drink items that are less than 100% to provisions  [released Ver 5.5]
• Add further (optional) levels such as having to do chores, dealing with pests 

Interaction

• Add things to make that you can interact with (such as wearing clothes and jewelry, washing and ironing clothes, sitting on chairs etc)   

Spells and Medicine

• Add items that let you create medicine & healing spells
• Add optional system to allow people to interact casting good or troublesome spells on others

Weapons/Combat

• Add items that let you create weapons
• Add optional system to allow people to interact using weapons (and also spells/medicine as above)

Storage

• Create a larder/pantry type item where products that are less than 100% can be saved (and/or have the option in existing storage to allow storing less than 100% items)

Animals

• Modify animal rezzer so you can rez animals directly as 'pets'  [released Ver 5.9]
• Create various 'creep crawlies' and cave-dwelling animals 
• Add 'troublesome' animals such as snakes, mice, bugs, rats, spiders, (groundhogs, gophers/moles?) - they all come with living on a farm & add more reality to the farming system as well.
• Create 'pests' such as greenflies, caterpillars (that can become butterflies) along with ways to control them (natural and chemical). This will be an optional setting.
• Add Birds (extends walk on to include 'air')
• Create a 'bulk feeder' that supports many more animals than existing ones.

Fishing

• Add fish and other water animals
• Create an improved fishing system

Baby

• Replace baby with a Quintopia designed one (as suspect current baby is 'acquired' from Second Life!)
• General improvements to interface and user interface
• Allow baby to have more than one 'parent' 
• Allow parents to specify avatars that can be carers for the baby

Plants

• Add a 'by products' feature (for things like leaves, roots etc) [released: Version 4.7]

Electricity

• Look at ways to support electrical driven items in 'old world' style farms (such as perhaps adding steam power )  [in beta]

NPC Farmer

• Allow the NPC farmer to top up animal feeders
• Allow farmer to clean  up dead crops  [released Ver 5.3]

Central control

• To overcome limitations of current updater system (uses llSensor so max 16 items can be updated and range 96m) - will allow updating all items no matter how many/how big the farm
• Provide a 'storage hub' so you can do things like store in one storage location and then take out from another (even in a different region)
• Show statistics around your animals, crops etc

YouTube channel

• Add more videos around developing your own items
• Add video guides/tutorials

This work by Buzzy Cnayl is licensed under a Creative Commons Attribution-NonCommercial-ShareAlike 4.0 International License.
Based on a work at https://satyrfarm.github.io/

Select the REF link on the right for the full recipe information.

This work by Buzzy Cnayl is licensed under a Creative Commons Attribution-NonCommercial-ShareAlike 4.0 International License.
Based on a work at https://satyrfarm.github.io/

13.6 SURFACES

(a) Overview

Surfaces are places that products can be set to go to when they are rezzed and also when you put them down. For instance, most food items that you cook will look for the SF Table, soap will look for the SF Soap dish and so on. The target surface for a product is defined in the products config notecard, eg:

TARGET=SF Table

You can find more information on customising products in section 13.3

So in this example, when the product is rezzed it will search for the closest SF Table and send a request to it for a landing spot. If there isn’t any available spots or if there isn’t an SF Table within range (approximately 20m) then the product will just settle where it is rezzed.

Surface objects consist of one or more prims names as follows:

Root prim – This will be set to the name from the NAME= line in the config notecard e.g. SF Table. If none of the other prims below are used, the root prim should be set to be the ‘surface’ prim by setting ROOT_SURFACE=1 in the config notecard. If you use the additional EMPTY prims below, you can choose if you wish the root prim to also be a surface.

EMPTY – These are optional prims that are used as extra surfaces for products to land on. The more you have, the more landing spots are available for products. These prims are simply a single prim without any scripts or content. The surface script automatically changes their name from EMPTY to FULL and back again to match with if a product is resting on it or not.

RESERVED – This optional prim is reserved for items that contain the addon-seek_reserved.lsl script (such as the SF Baby). It allows you to keep one prim available for a particular object. As an example, the SF High Chair is a surface object that the baby food will seek out, but the reserved prim allows the baby to always land sitting. This prim is simply a single prim without any scripts or content. The surface script automatically changes the name from RESERVED to R-FULL and back again to match with if something is resting on it or not.

Decor – This optional prim is normally hidden and then shown whenever one or more products are on the surface. An example is the table cloth on the SF Table

(b) How it works

When a product is rezzed, if it has a TARGET= entry in its config file, it searches for the closest object with that name and if it finds one it sends it a message asking if it can land there. If the object is running the surface script it will reply with either the landing location information (the coordinates and rotation of the next available empty prim) if a space is available, or else a message that it is full.

Next, when the product is touched it will move away from the object and send it another message to saying it has left that space. That way the surface object keeps a track of which prims are currently in use or vacant.

Note that sometimes objects may be removed but not notify the surface (such as if you directly deleted the product without first touching it) and so the owner of the surface object has a Reset option shown on the menu which clears all surfaces to the empty state.

When there are no products on the surface, the décor prim is set to transparent. It is shown again when the first product lands.

When a product requests a landing point, the surface script scans through all the prims in the object until it finds the first one named EMPTY (or if set to use the root prim it picks that first) and then send the location and rotation of the prim to the product.

(c) Configuration options

# Name of object
NAME=SF Table
#
# Is the root object a surface, 1=yes  0=no
ROOT_SURFACE=0
#
# Set to 0 if this is a stand-alone item (vase etc) or 1 if part of another item that handles touch events
EMBEDDED=0
#
# Does item have to be made  for it to work 0=no, 1=yes
MANUFACTURED=0
#
# (Optional) How many days until item wears out
#EXPIRES=60
#
# (Optional)  Set table cloth colour as vector, eg. <0.0, 0,5, 0,1>   or use word random for random colours
CLOTHCOLOR=random
#
# Default language (if EMBEDDED=1, otherwise ignored)
LANG=en-GB

NAME – This is the full name of the surface object e.g. SF Table

ROOT_SURFACE – Set to 1 to have the root prim be counted as one of the available surfaces. Set to 0 to only use the prims named EMPTY

EMBEDDED – If set to 1 the surface script will not respond to touch events. This is used when there is another script in the object handling touch events, e.g. you could use the surface script on the SF Bed to have a surface where the SF Duvet will land but touching the bed calls up the main script for interacting with the bed (sleep etc)

MANUFACTURED – If this is set to 1 the object will only work if it has been made (with the machine script) rather than being taken out of inventory or/and copied. As an example you can set the SF Vase so it has to be made with the pottery parts of the system before you can use it to put flowers in.

EXPIRES – You can set how long a surface object will last before expiring (wearing out!) Note that this value can be set for both manufactured and non-manufactured items.

CLOTHCOLOR – This will set the colour of the Decor prim to the specified colour vector (such as <1.0, 0.3, 1.0>) or you if you use the word random it will be a different colour every time the prim is shown.

This work by Buzzy Cnayl is licensed under a Creative Commons Attribution-NonCommercial-ShareAlike 4.0 International License.
Based on a work at https://satyrfarm.github.io/

12.1 SHOP

Quintopia items, along with just released and beta test versions all at the farm shop in Mintor region.

To get there, on your map, just type in worlds.quintopia.org:8002:mintor to the 'find' box:

You will also find a growing community for support, sharing and discussion on the Quintopia website at https://quintopia.org

This is also the place to check for the latest information on items in the system such as:

Recipes

https://quintopia.org/forum/recipes

Nutrition values

https://quintopia.org/forum/recipes/267-nutrition-values

List of animals

https://quintopia.org/information/user-guide/animals

List of platforms / boxes

https://quintopia.org/information/user-guide/boxes

This work by Buzzy Cnayl is licensed under a Creative Commons Attribution-NonCommercial-ShareAlike 4.0 International License.
Based on a work at https://satyrfarm.github.io/

11.1 UPGRADE INFORMATION

The Quintopia system is continuously being extended and updated and so it is best if you can to make sure all items you are using are at the same version level.

Whenever possible an updater will be made available that allows you to run it and it will scan for and update all items of a particular type. Note that you must be the owner of the items to be able to update them this way. Updater's can be found in the main store on Mintor (see chapter 12)

For storage, there may be a ‘migrator’ that will take all the stock from your existing storage and transfer it into the new version of that storage unit for you.

When a major release is made it often is not possible to make something to automatically update items and in that case it is recommanded to replace items.

One way to do that is to ‘paint everything red’ so you know what are old items, then work through gradually replacing them.

To ‘paint’ things, right click one item and select Edit, then you can ‘shift click’ on more items to select them as well. Next click on the Texturetab and here click on the Coloroption. Pick a nice bright red! You may also want to click on Full Brightand also set some Glowto help you see what are the old items.