Selling Objects and the Radial Menu Issue

I want to have items set for sale, so that they show as such in the new search, but also use a selling script that uses "pay" in order to split proceeds. The issue is that this results in showing both a buy and a pay option on the pie menu when the object is right clicked. Is the radial menu for an object modifiable by code to only show "pay" or only showing "buy" in the 'More" second level menu?

The only thing about the radial menu that can be changed directly is the text that appears in the "sit" and "touch" slices.

"Buy" is controlled only by setting the object for sale (or not) on the first page of the object properties. "Pay" is controlled by having a money() event in the current state for a script in the object. That control is simply on or off, though.

There is no way I know of to do both without the risk of the object being sold. It would be like putting up a vendor and setting it for sale. Would be very bad if someone bought your vendor full of items.

Make the vendor as a standard scripted item, and then click the "Show in Search" option on it.

the hardest part is not being able to set the buy price on a per item basis...

oh and how goes the kingdom?

Thanks all, and Wessex goes well . By the way since i have the object set to sell contents, the scripted object itself is not in danger of being sold, but of course if they should choose "buy" rather than "pay", the split does not occur.

It goes beyond this sub-forum, but my concern is if I use show in search, and not set for sale on the object, that it affects relevance on search results. Since the information is very sparse on relevance with the new search, I have yet to be able to find out if that is true or not. My current set-up uses JEVN GVS scripts.

These of late have been having numerous failures, requiring replacing both servers and vendors to be be replaced completely after a failure to deliver occurs. So I am playing with simpler sell scripting, non-server, to create a more dependable set-up. With over 40 servers, failures and replacing are a big hassle.

I'm also thinking of adding email notifications on sale to the script but am concerned with the delay this apparently introduces.

If you want to use only "Pay" why are you setting the object for sale in first place?

EDIT: @Kahiro
Becuase the word is search ranks differently for buy price listed and for just "show in search"... truth unknown, but likely since it does seem to rank pricing

the problem you'll have with setting buy is even worse than you imagine...

aside from not being able to run vendor style price switching, contents would also give out your pay split script (which I think needs to be in the root to trigger properly)

even assuming you moved the main contents out to a child prim and left a note card or some such in the root, the user could still buy it and "get ripped off".... you could attempt to prevent this by various means like setting a ridiculous buy price (which will skew your search results) or naming the notecard "Don't use buy, left click and pay" in conjunction with setting the default touch behavior, but eventually someone will be in a hurry and then have a fir when they are "ripped off".

even worse, assuming LL decided to list non-buy price set items first (which I highly doubt) you'd have a situation of every box vendor suddenly using a pay script and upping the sim script load

they can't list via set pay price, because that changes dynamicly in vendors, and if they only picked one value, people would game it with 1$L listings that didn't get you an item

the system is very skewed and screwed...

I expect to start seeing some very odd hide-a-prim vendor systems, where they issue commands to unlinked box vendor prims, which then pops forward, allowing the user to buy contents , or copy (or original, and then rerez as hidden), then hide it away... so that it's still on a parcel for listing, but not seen... still doesn't help with paysplits though.... perhaps if buy triggered the money event =/