CasperLet/Migration Tool: Difference between revisions
m (→Migration Tool) |
|||
| Line 19: | Line 19: | ||
However, the HippoRent units '''themselves''' will usually need to contact the website in order to retrieve data to feed to the migration script. Thus, on occasions when the HippoRent website is not contactable (such as if they have a site outage), getting data FOR migration is not guaranteed to happen either. | However, the HippoRent units '''themselves''' will usually need to contact the website in order to retrieve data to feed to the migration script. Thus, on occasions when the HippoRent website is not contactable (such as if they have a site outage), getting data FOR migration is not guaranteed to happen either. | ||
== '''<span style="color:#00528c">Migration Tool</span>''' == | == '''<span style="color:#00528c">Migration Tool Configuration</span>''' == | ||
At the time of this writing, this tool supports both web-enabled and non-web-enabled HippoRent boxes. | At the time of this writing, this tool supports both web-enabled and non-web-enabled HippoRent boxes. | ||
Revision as of 14:38, 26 September 2015
Supported Migrations
Currently this tool only supports migration from HippoRent.
Migration Caution
 | This tool is unsupported and provided only on an as-is basis, without warranty. This tool may not move any or all of the available configuration options, if Hippo Technologies blocks any part of its actions. |
Basically, this tool should work, and should transfer the time remaining, but if it doesn't, it's not CasperTech's responsibility (the migration tool script depends on Hippo Technologies not changing anything in their scripts) - please test it on a single unit to verify that it still works before full-scale use!
Also, be aware that Hippo Technologies may take steps to disable this functionality in future versions of the HippoRent system, as is their right.
Migration Requirements
The migration kit itself doesn't need to connect to the HippoRent system.
However, the HippoRent units themselves will usually need to contact the website in order to retrieve data to feed to the migration script. Thus, on occasions when the HippoRent website is not contactable (such as if they have a site outage), getting data FOR migration is not guaranteed to happen either.
Migration Tool Configuration
At the time of this writing, this tool supports both web-enabled and non-web-enabled HippoRent boxes.
Configuration migration which is currently supported:
- Current tenant
- Current time remaining
- Price (and USD price setting if appropriate)
- Price term (Days, Weeks, Months)
- Prim count
- Minimum rental term
- Maximum rental term
- "Will not renew" setting
- "Auto Evict" setting
- Hovertext settings
- Change size / move / alpha on rent
- Extra prim allowance
- Profit shares
- Partners (Additional Tenants)
How to Use
- Rez the Migration Base somewhere on the same sim as your HippoRent unit
- Drop the Hippo Inquisitor script into a rental unit you want to convert
- Wait for the process to complete
- Run the latest CasperLet UpgradeBee on the "upgrade" function to be certain you have the latest CasperLet script in your new rental unit
NOTE: This will need to be done on a per-unit basis only. This tool cannot migrate an entire sim/region's worth of rental units at one shot.
FAQ / Troubleshooting
- Q. I migrated my renter information to CasperLet, but it's an older version of the CasperLet script - is this a problem?
- A. There's no harm, just use the UpgradeBee from the current shipping crate to bring them up to date. Casper just hasn't updated the CasperLet script in the migration tool yet.