Set up more regions in the Regions.ini

When you first start OpenSim, a file “Regions.ini” was created automatically. This includes the following information, which of course depend on one’s own responses to the questions on startup. Here, then, according to the example:

RegionUUID = 8cd612e1-afb4-41f1-8bc2-9e46996378c3
Location = 1234,4321
InternalAddress =
InternalPort = 9000
AllowAlternatePorts = False
ExternalHostName = 10.345.67.89

To create another region, copy the above section, and paste it to the same file. Then the data must be adapted to the new region, here shown again in bold.

RegionUUID = e6e694b4-c5a1-443b-a046-edcd82dece64
Location = 1235,4321
InternalAddress =
InternalPort = 9001
AllowAlternatePorts = False
ExternalHostName = 10.345.67.89

1) The names of all regions must not exist in the selected grid.

2) Each new UUID must not exist in the grid. The UUID is a very large random hexadecimal number. If you generate a UUID with tools on the Internet, this number is almost certainly unique in the world: a UUID-Generator

3) The position of each region must be free on the grid map. In this example, the second region is located to the right of the first region.

4) Each region need to have its own port number assigned. The best thing is to just count up, so port 9001 for the second region, etc.

The settings will take effect on the next start of OpenSim. Start OpenSim manually, because you will have to answer questions again! Unlike the first start though you will only be asked for the Estate. If you now give the existing estate (in the example “TestImmoServices”), then you’re done. If you specify a new estate, you need to enter a new Owner. Of course, this may be the same avatar as before, or for example a tenant.

Note: The computing power of the server will be distributed to all regions, so don’t overdo it!

Option “ExternalHostName = SYSTEMIP”

Using this option OpenSim automatically determines the IP address assigned to the computer by the router. On a rented server in a data center, this is usually the IP address visible from the Internet. In private homes or school networks, however, the router usually assigns a local IP address that is not accessible from the Internet. In such cases, the SYSTEMIP option may not be used, but the IP address (or domain name) of the home connection visible from the Internet must be specified.

ExternalHostName in standalone mode

Unfortunately it does not work in the Regions.ini file to adopt the constant defined in OpenSim.ini. Also for standalone operation, the domain or IP address must be explicitly specified for ExternalHostName in all regions. If the computer itself has an externally visible IP address, alternatively SYSTEMIP can be specified.

VAR regions (optional)

VAR regions are a multiple of 256 meters in size, they must also be square. As coordinate, you must specify the position that would have the tile at the bottom left when in mind you dismantle the region to standard size. To avoid problems, it makes sense for the time being that direct neighboring regions have the same size. The bigger the region, the higher the hardware requirements for the visitors, because at least the terrain has to be completely loaded. Example:

RegionUUID = f52b07b9-3799-49c0-b3e3-00430f179eea
Location = 3456,6543
SizeX = 768
SizeY = 768
MaxPrims = 45000
InternalAddress =
InternalPort = 9050
AllowAlternatePorts = False
ExternalHostName = 10.345.67.89

Here a 3×3 region was chosen, with 768 meters of edge length. Since it is nine times larger, the allowed number for Prims has been increased (the default value is 15,000). The potential Prim count, of course, depends on the performance of the server, the number of regions on it, and not least the traffic and the complexity of the objects.

Note: Without additional configuration in the OpenSim.ini, only a warning is displayed when the allowed Prim count is exceeded, but nothing is deleted.

Additional features

There are several other optional configuration settings for the regions, which are well explained in the comment lines in the “Regions.ini.example” file. To be not too confusing for beginners, this guide does not take into account every single optional detail. What else can be configured in the Regions.ini:

  • Set a specific region landing point, used when no teleport coords are specified.
  • Set allowed prim sizes and counts (needs additional configuration in OpenSim.ini).
  • Allowed simultaneous Avatar count.
  • Allowed prims per user and parcel.
  • “Region Type”, that string is used to show “Mainland” or “Private Estate” in SL, here it can show whatever.
  • Show a static maptile from an inworld UUID or from a self created image file.

Continued: Tuning of OpenSim.ini

Scroll to Top