SphynxDraft/Test Code: Difference between revisions

From CasperTech Wiki
Jump to navigation Jump to search
No edit summary
No edit summary
Line 13: Line 13:
Casper created an explanatory video about delivery issues relating to viewers in Second Life. This information pertains to ALL scripted delivery systems, not just CasperVend.  
Casper created an explanatory video about delivery issues relating to viewers in Second Life. This information pertains to ALL scripted delivery systems, not just CasperVend.  


<div style="width:100%">{{#ev:youtubehd|9Cs0HwONr18||left|Video by Casper explaining viewer-related delivery issues}}</div>
<div style="display:inline-block">{{#ev:youtubehd|9Cs0HwONr18||left|Video by Casper explaining viewer-related delivery issues}}</div>


== '''<span style="color:#00528c">Transaction Log OK, but Still No Delivery?</span>''' ==
== '''<span style="color:#00528c">Transaction Log OK, but Still No Delivery?</span>''' ==

Revision as of 09:20, 17 June 2014

This is just for editing code snippets until they stop making me rip my hair out

                    


Video About Delivery Issues

Casper created an explanatory video about delivery issues relating to viewers in Second Life. This information pertains to ALL scripted delivery systems, not just CasperVend.

VideoService "youtubehd" not recognized.

Transaction Log OK, but Still No Delivery?

Then what may have happened is any of the following:

  1. Customer may have not noticed the delivery popup (especially if they're on a v3-interface viewer such as the SL Viewer 3, Firestorm, Catznip, Exodus, etc.)
  2. Customer may have accidently clicked "Delete" - if you are not using the Bot Delivery system, clicking "delete" doesn't even send it to the user's trash folder - it's just gone forever.
  3. Customer may have accidentally muted your dropbox
  4. Customer may have muted - by name - "CasperTech DropBox ((version number))" from someone else. If you have never renamed YOUR dropbox from that default, then YOUR dropbox would get caught in that muting as well.
  5. Customer may have accidentally muted YOU
  6. Customer may be in "busy" mode (which typically declines *everything*, regardless of whether it comes from a person or object)
  7. Customer might need to relog to see either the delivery prompt, and/or see the product in their inventory.

Points #1 and #2 in this list are also explained in the video linked above.