Well, i didn't have a good title. Sorry.
My idea is: Add an Extra Field. For example: We have Subscriptions, but we want to give Coins with this method.
Would be cool that, eh? But, if we give coins we don't give subs. :/
CheckPassport(passport,field)
Then we create the new field and we do
CheckPassport ("123456789abcdefg","Gold") To get Gold
CheckPassport ("123456789abcdefg","Subscriptions") To get the Subscriptions
Then the Fields would be like this:
Create a new Field
It asks the Name and Type (In type, example: String, Date (DD-MM-YYYY), Number, etc)
Understand? D:
1
2
ID:104058
Nov 1 2010, 12:50 pm
|
|||||||||
| |||||||||
Nov 17 2010, 8:21 am
|
|
Nice.
|
So basically you're asking for a method to provide micro-transactions? People would be able to sell gold separately from an actual monthly subscription?
|
No, for example. Player A haves a Subscription. (We're using Subscription Field), now Player B gets Gold (we're using Gold Field) Then in Field A will appear Player A - Time
and in Gold Field will appear Player B - Gold |
Seems like it would be simpler to use different passports for the different types of transactions.
|
Then the feature request should probably be, "Let us have more than one passport."
|
Lol. Let me explain:
Did you see that we can do Subscriptions using CheckPassport. Well, but only Subscriptions? That sucks! (Omg, like robot) What about making fields for Gold, Points, or those things? Also in Gold/Points value can go "String, Date, Number, etc) Example: Subscriptions Key - Expiration (Date) Ocean King - 999999 (Lifetime) Gold Key - Amount (Number) Ocean King - 99999 Understand? =P |
Yea, I understand that part, and support it. I don't understand why you would be making multiple hubs
|
Bump again, I still think this should be on the list, and therefore would like to bring back attention to this.
|
I like the idea, but it's possible to work around with a database and some type of subscription server.
|
Lummox JR wrote on issue #2979:
CheckPassport(), which just gives a yes or no answer as to whether a user is currently a subscriber, is obviously inadequate to the task because the point would be to check for new goods (and refunds, etc.) since the last time the game was played. We could make a new proc: CheckHubItem (passport_identifier,key,fields,amount) It can work like a cross between CheckPassport & GetScores Args: passport_identifier: a text string assigned to you by BYOND Hub. key: the name of the player, character, etc. for which scores have been set fields: The data fields to retrieve amount: the amount they have in the field Example: world >> hub = "My.Hub" //change this to your own hub entry mob/var/Gold mob/Login() >> var/gold = 0 >> client.CheckHubItem("0123456789abcdef",src.key,"Gold",gold)) >> src.Gold = gold >> return ..() |
1
2