There are no planned deployments / restarts for week #10.
The HTTP / Vivox RC viewer updated to version 126.96.36.1991980 on Friday March 4th. This release sees the CURL updated to 7.47.0, together with 10 further fixes and updates over the previous release, included HTTP fixes and fixes with issues within the viewer such as avatar bake fails, viewer crashes, notifications problems, and music stream failures.
The current Maintenance RC viewer updated on Wednesday, March 2nd to version 188.8.131.521770.
As noted in my last Project Bento update, the Bento project viewer updated to version 184.108.40.2061861, also on Wednesday, March 2nd, and includes a new version of the Bento skeleton with additional bone sets and other revisions.
Aditi Inventory Syncing
As reported by Coyot Linden at the Simulator User Group meeting on Tuesday, March 8th, the new process for syncing users’ Aditi (Beta grid) inventories with their Agni (main grid) inventories is in the final stages of QA testing, and should be deployed either later this week or early in week #11.
I’ve covered on this subject a number of times since it was first noted as being in the works in December 2015, but in short.
- Once in place, the new process will not require users to change their SL passwords in order to trigger their Agni inventory being copied over to Aditi. Instead, anyone logging-in to Aditi will automatically have their inventory copied from Agni to Aditi a part of a new process (run at about 06:00 SLT each day)
- This will happen each time a persona logs in to Aditi, unless their inventory is already flagged for copying.
- Instead of overwriting a person’s existing Aditi inventory, the incoming Agni inventory will be merged with their existing Aditi inventory – so items unique to a user’s Aditi inventory will no longer be lost as a result of their Agni inventory overwriting the Aditi inventory
- The process will not duplicate items previously copied to Aditi from Agni; however, if an item is renamed or moved to another inventory folder on Agni, it will be copied to Aditi
- If an item is deleted from inventory on Aditi, but exists in inventory on Agni, it will be copied to Aditi the next time the process runs for that user
- Inventory and folder links will also be copied from Agni to Aditi
- Trash and the Current Outfits folder will be excluded from the copy process (the latter to prevent avatars on Aditi ending up wearing multiple outfits).
PaleoQuest Banning Issues
PaleoQuest, the Lab’s dino-related quest game which features Experience Keys and which opened in July 2015, has always had some fairly strict rules on what is and isn’t allowed. However, these rules appear to have been recently updated, with the result that a number of users have found themselves banned (or in receipt of a ban warning) where no infringements have taken place (see here, here, and here for examples).
One major cause of recent bans seems to be that the game is confusing HUDs worn by a user when trying to enter the game (or even in the middle of playing the game), with an attempt to wear a “fraudulent” game HUD, resulting in the wearer gaining an immediate ban, together with the following notice:
YOU ARE WEARING AN OBJECT THAT IS TRYING, WITHOUT SUCCESS, TO PASS ITSELF OFF AS A GENUINE PALEOQUEST HUD. THIS BEHAVIOUR IS ASSOCIATED WITH FRAUDULENT ATTEMPTS TO OBTAIN REWARDS IN THE GAME AND IS NOT TOLERATED. YOU HAVE BEEN BANNED FROM PALEOQUEST.
The problem with the bans has been further exacerbated by some who have raised support tickets having their bans reversed with a note that the system will be adjusted, while others appear to have had their tickets summarily closed.
As a result of this, and other issues encountered with the ban system during what is effectively “normal” game play, a bug report as been raised (BUG-11533). Should you find yourself banned from the game or in receipt of ban warnings whilst engaged in “legal” game play, you might want to add the specifics of your situation to the JIRA, and don’t forget to append information about your viewer / system from Help > About (+ viewer logs, if you have them).