*Added parcel join support
*Made parcel saving and loading much more efficient
*Fixed bug that would not allow joining of parcel locally in the viewer (gives an error before sending to server)
*Known Issue: Restoring parcels from storage is not working correctly. For now, do a 'reset parcels' to regenerate a standard parcel
*Added support for Subdivision (use master avatar to login to try out)
*Added Parcel Border support
*Enabled user account storage, but only when a new account is created
Bug Fixes:
*Fixed crash on startup while in sandbox when "Setting up master avatar"
*Fixed most core functions in ParcelManager and Parcel that where broken
*Fixed Parcel saving to database
Known Issues:
*Dividing parcel fails in viewer (gives an error about needing 2 parcels)
* Now exists MainConsole.Instance.Error/Warn/Notice/Verbose -- use those instead
* Removed some instances of System.Console use - aiming to depreciate this in favour of MainConsole completely.
*Added Configuration option for Master User Avatar name and (in sandbox mode) password
*Added support for Master User in sandbox mode. Support lacks for grid mode still.
**Grid support is possible when remotely fetching avatar data by name and UUID is available
*Currently lacks parcel buying support. For now, in sandbox mode, log into master user information to own the parcel
*Added Parcel Backup Support for DB4. Other storages currently do not save
*Added parcelIDList in ParcelManager to speed up parcel fetching at position
*Added ParcelData.cs and ParcelData class for better storage support
*Documentation for parcel added
*2 Parcel Related bug fixes
*Created Parcel class to handle each parcel
*Created ParcelManager class to handle the Parcel Object
*For now, by default it is assigned to a fake avatar key and set for sale to L$0
* Removed strip2.png - added defaultstripe.png
* World map images are now generated when the terrain is tainted, not yet sent to the grid/asset server.
All you need to do is put .xml files for each region you want to be ran by the single server inside the "bin\Regions" folder (make sure none of the settings in those .xml files conflict with each other) and then startup the server and login, Any neighbouring regions that are being ran in the instance should show up. (However there is still no movement or anything)
Now time to refine the communications interfaces!
mingchen