Zaylor Tokugawa
Registered User
Join date: 16 Feb 2005
Posts: 5
|
08-01-2005 18:53
I have developed a casino gaming table that is exhibiting odd behavior. There are several scripts that speak with other via link_message's. The script with the money event waits for a message to begin listening for someone to pay. After someone pays and begins to play, the script proceeds to another state and no longer listens for money events while the play is in action.
This part works fine. What is distressing, is that other prims of the table show the "pay' pie slice while the table is busy. It is almost as if these prims have a script with money events waiting for someone to pay, but these prims contain no scripts at all.
Has anyone encountered this phenomenon or have suggestions for resolving?
TIA Zaylor
|
Moonshine Herbst
none
Join date: 19 Jun 2004
Posts: 483
|
08-02-2005 00:06
This bug has been around for ages. Sometimes the 'Pay' goes away, sometimes it doesnt. My solution is to NOT leave the state with the money event, but rather refund money if they are paid at the wrong time. For instance by using variable IN_PLAY=TRUE when a game is running and IN_PLAY=FALSE when it is open for a new game. Then if IN_PLAY==TRUE, I just refund the money given. Another solution is to use a credit system. This will let them pay anytime they want, but it requires prims for the credits display, 'PLAY' & 'CASH OUT' buttons, and a check to see if the payee is the current player.
|
Bosozoku Kato
insurrectionist midget
Join date: 16 Jun 2003
Posts: 452
|
08-02-2005 05:20
Not too familiar with this "bug", but is the money script in the parent prim? That might matter with the pie menu.
Might even try to manually "update" the object, with a quick llSetPos(); up and down 0.001. Dunno if that matters with the pie though, but who knows (certainly works with floating text).
|
Malachi Petunia
Gentle Miscreant
Join date: 21 Sep 2003
Posts: 3,414
|
08-02-2005 07:55
To amplify Bosozoku, there are prim properties (non-physical rotate, llSetText, etc) that "stick" to the prim even when it doesn't seem like they should. I suspect that the pie menu text has this "feature".
As Moonshine notes, money() events should *always* check for overpays (or not-allowed-now pays) and refund. Nothing irritates customers like devices that take your L$ and don't give what you were expecting.
Happy LSL.
|
Jade Lily
Cat Herder
Join date: 9 Oct 2003
Posts: 219
|
08-22-2005 17:51
What if the scripted object is a single prim? Should we still expect this bug?
|