| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
| |
Floating text, Rotation, Texture animation, Particle System
This will make "Eye Candy" scripts work without modification in
XEngine. The use of the CHANGED_REGION_RESTART hack is no longer
needed. Implemented in MySQL only, hovertext also in SQLite.
|
|
|
|
|
|
|
| |
I apparently missed one drop tables statement that was actually needed
when I did the cleaning to make this work for old sqlite versions.
|
|
|
|
|
|
|
|
| |
tables shouldn't exist yet, and the exists keyword is relatively new in
sqlite. This has been breaking a lot of people on Suse Enterprise Linux,
for instance.
|
|
|
|
|
|
|
| |
Plumbs in attachment persistence and adds the tables. Currently MySQL
only, no user functionality yet.
|
| |
|
|
|
|
|
|
|
| |
This will have no effect unless both the UGAI and the region are
this revision or later
|
| |
|
|
|
|
| |
dlls. Fix issue 1876.
|
|
|
|
|
|
|
|
|
| |
Adds the new access semantics and the new flag (allow only age verified)
Plumbs in the abuse email address from sim to viewer. The other way around,
libomv appears to be lacking support for the data field in the packet.
Includes a migration, run prebuild!
|
| |
|
|
|
|
|
|
| |
of the issue.
|
|
|
|
|
|
| |
help much, but it might.
|
|
|
|
|
|
|
|
| |
put some drop table if exist clauses in here to hopefully let this
migration work for people that are in an intermediary broken state
right now.
|
|
|
|
|
|
| |
Makes the estate dialog fully functional. Implements all client facing functionality. Moves estate data from estate_settings.xml, which is used to provide defaults, to the region data store. Creates one estate for each region, and places the region in it. Converts all region bans to estate bans.
|
|
|
|
|
|
|
|
| |
Patch 5 in the region settings series. Adds a migration to ensure corrupted
data is purged and re-read from defaults. Some changes. Still no full
functionality
|
| |
|
|
|
|
|
|
|
|
| |
* Migration should be automatic on sqlite and mysql
* Migration is not automatic on mssql, you will need to drop the invType column manually
* Migration should be fine, but as for any db change, I would recommend making sure you have backups before moving past this revision
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|