aboutsummaryrefslogtreecommitdiffstatshomepage
path: root/OpenSim/Region/CoreModules/World/Estate/TelehubManager.cs (follow)
Commit message (Collapse)AuthorAgeFilesLines
* Simplify and streamline telehub editing code. Verify rotations and fixMelanie2012-01-241-47/+22
| | | | spwan point positioning on rotated telehubs.
* Change Telehubs to store only the data that is really needed and notMelanie2012-01-241-50/+20
| | | | additional redundant information.
* Add update to Telehub position and rotation before adding SpawnPointsBlueWall2012-01-231-4/+11
|
* Cleanup BlueWall2012-01-231-3/+6
|
* Cleanup unused parts, add some error handlingBlueWall2012-01-231-53/+52
|
* Move Telehub tables and data from EstateSettings to RegionSettings.Melanie2012-01-221-24/+22
| | | | | | | | | | This is damage control es EstateSettings is not the place this can be put. EstateSettings is nt unique to a region and therefore would introduce a hard limit of one telehub per estate, completely shutting off the option of having SL style telehubs, e.g. one per region. Whole estate teleport routing can still be implemented id desiresd, this way all options are open while the other way most options get closed off.
* Telehub Support:BlueWall2012-01-211-49/+62
| | | | Telehub settings now persist to the database and are saved across sim restarts. So-far this only works on MySQL. this is a work in progress, teleport routing is not yet implemented.
* Telehub Support:BlueWall2012-01-201-0/+130
Support for viewer side of telehub management. Can manupulate Telehubs and SpawnPoints from the viewer estate managemnt tools. This is a work in progress and does not yet persist or affect teleport routing.