buy() *please*

Please.
Pretty please.
Pretty please with sugar on top!

I want buy()
I want it to work exactly like money() works, cept for it being called whenever the object is purchased.

We're hearing this all over the forums and in world.

We need to know which of our items that we have in world for sale ARE actually selling, so we know which ones aren't.

So I'm begging.
I'm pleading.
I'm on my knees.

And I'm gonna hold my breath til you (LL) say "yes". Oh yes I will. I'll hold my breath til I turn blue in the face and then pass out and then won't YOU feel bad?

<sobbing> Pleeeeeeeeeeease? </sobbing>

#!

hehe, my pleases aren't as pretty, but it would be handy to have something like that. Personally, I think it would be even nicer if a event handler like Shebang wants would be able to sense whater other objects have been sold, so not every itme would have to be scripted. It would certianly help me find out who is givving me all this money!

BBC

What BBC said.

It would be VERY nice to not have to script it into every for sale item (especially since the way I intend to use it involves emailing me -- and I don't think my buyers necessarily want that script, at least not with MY email address in it).

So, buy() in ObjectA's script would detect when other objects owned by the same owner that are within X distance of ObjectA are purchased and would grab the name of the buyer and the name of the object purchased. Am I understanding the way you meant, BBC?

(Btw, LL, I'm a lovely shade of baby blue now =)

#!

As Shebang knows, this is something I need pretty badly. Especially since there can be a problem with shelf space (both physical and just in maintaining a display object that's complex and not selling well when it could be repackaged).

So I'm going to join in on the breath-holding... *holds breath*

I was thinking along a similar vein a few days ago. And a buy() would be very nice!

But then I think, is that fair to the modellers who don't want to script and still sell gobbs of stuff? They should have access to it as well.

This sounds like a job op for someone that definitely isn't me.

flyk

OK, OK... sorry I hadn't seen this thread till now. Hope you are all still with us

Yes I agree this is totally important to have. I'll try to think of a back end way to do this ASAP.

How about instead of a buy() (although I think that is cool as well), we IM you whenever something gets bought. So in real time, if somebody buys something of yours, you get a system message:

"Shebang Sunshine just purchased 'blue sunglasses' for $50"

Something like that.

Hey Phil... can you have like a retail history? so only objects that are bought show up? Like...

Item - number sold - Cost of the item - total
Socks 2 20$ 40$

Even take in account how many weeks and how much the item cost to keep "in world" plus profit. The Items in the history would only be items that you put for sale. Not every item in your inventory.
-Nexus Nash

Philip,

If IM is your best offer, then we'll accept (like we have a choice... LOL!)

The only problem I have with IM's is that they aren't logged -- worse case scenario, I log in, get the IM but crash before I've even had a chance to read it, much less make a note of it.

If the IM way is to be a temporary bandaid until buy() can be coded in, then I'm 100% on board.

The no longer blue #!

IMing is a big step up, especially if it's temporary. I think eventually SOME long-term method of tracking sales is going to be a must...