Switch to ArdorForum

When the site will be up, I would like to know more about this platform for example if I would make a game, I need to use only API and nothing more or can I use for example mysql database to store additional data for the game? And will it be available on your hosting too?

Quote from: xamax on August 06, 2014, 10:22:47 am

When the site will be up, I would like to know more about this platform for example if I would make a game, I need to use only API and nothing more or can I use for example mysql database to store additional data for the game? And will it be available on your hosting too?

The site if you are talking about nxtchance.com will not be up for a while. It's primary function will be to promote games, not provide information for developers. If we'd create it now it would be just the information that you can already read in the pdf, so we chose to focus our energy developing the back-end and games.

About your question:
Every game will have their own mysql database and every api call that calls a function that needs to save data about the game writes into this database. If you need additonal fields in the database or custom API calls to achive this, we can help with it.
But you can also use a separate database for other data if you wish.

I hope it will be possible to create additional databases in your hosting because otherwise it will be pointless to have another hosting only for second db. Anyway, if the site nxtchance.com is not to get more info about that API then where is place to get more info about it and start testing eventually? I mean to create small game etc.

I hope it will be possible to create additional databases in your hosting because otherwise it will be pointless to have another hosting only for second db. Anyway, if the site nxtchance.com is not to get more info about that API then where is place to get more info about it and start testing eventually? I mean to create small game etc.

Sure, you can create additional databases. Developers will get a cpanel account on the server.
Please contact us at info@nxtchance.com and we can discuss specifics about the API system and how to integrate into your game.

A standard API call looks like this:
https:// nxtchance.com/newGame?userID=nsqe-frsa-7982&amount=100&apikey=f4c3defbdas493e&hash=8baedbaaad322020ba4a26d364c8844c33c9d690245e6fdg1d1da0623f727932

This gets called when a user click on the bet button. Other parameters are accepted. The apikey is a public key unique for every game. The hash is a hash-256 string created from the api request string and a private key.

Thing I would like to know (and others probably too) is for example how much freedom developers have. Do they have to use only API or they would have more options like php and crone etc. Also some small tutorial and documentation would be nice to see.
And what is eta for user panel and other tools (like for example what tools did you use to create games on the client side, codeigniter maybe)?
I'm just trying to figure out how is that working in practice.

A quick overview how our service works from a game developers point of view.

You want to create a game: rock-paper-scissors.
You make the game interface, totally up to you how it looks and what tools you use to make it. You can make it browser based, or a windows client, or a mobile app.

When a new user (meaning have no cookie from the game) visits you call getNewUser and the system generates a new user ID and password, and gives you the result in JSON.

You have an element where you display user information, like ID, name, balance, deposit/withdraw options, etc. For this you call getUserData with UserID parameter and in the response will be everything you want to display.

When the user choose a Nick name, you call newScreenName to change it in the database. When they click Get deposit NXT address you call getAccountID to get one from a previously generated list provided by you.

There are other calls but I think it's clear how it works.

Now, how to play:

Rock-paper-scissors is a three outcome game, player can choose rock paper or scissors. Let's say they choose rock, and press "bet" button. This makes an api call newGame, that passes on how much the user bet, what outcome did they bet on, how many time they want to run this bet, etc. Also from what range from the outcome be generated. In this case 1-3, where 1 is rock, 2 is paper, 3 is scissors. (If a game works with more complex outcomes, we need to integrate it into the system. But it shouldn't be a problem)
The system then respond with the bet result in a JSON format, that you then can display any way you like.

The player likes this bet, so they add it to the Favorites. You call addFavoriteGame and the game gets added to the database for this player.

There are additional calls for listing users, previous bets, withdraw requests, etc. There are some to pause game, deposit, withdraw for maintanance.

Hi,
Yes you can do that, or we can integrate your rules to the API, and after that the API can fully manage your game too.

We need basicly one function from you: how to decide that a bet is win or lose. Now the API can decide some basic situation like bet is lesser or grater then the random number, like the dice game.

But if you make a game, where you roll 3 dices, and then add the first two and then multiply the result by the 3rd dice, then we need a little function which is tell us, that the bet is a win or lose. You don't have to share this function with the other users, so if somebody else want to create the same game, he have to produce this function too.

If there is a problem with this function you have to cooperate with us to fix the problem, but I think it's just a little uncomfort.

It looks like there is still some confusion about what we offering so I'm going to try to clear it up.
Our cooperation with a game developer looks something like this:


Someone wants to make a roulette game, so they contact us.
As we have no idea what roulette is, we will ask about the rules. What can be the outcome, what type of bets can the players make? (In case of roulette there is 37 (38) possible outcome, and player can make all kind of bets. Bet on number, odd/even, black/red, street, corner, etc).

When we know what is needed for the game we set out to create the neccessary decision making mechanisms if they don't exist yet. While we work we will keep contact with the developer to make sure everyting is as it needs to be.

While we doing this, the game developer have time to work on the games user interface, the web design and other important stuff. We will sent them the documentation for the standard API calls that can be integrated into the game (like account creation and display, how to create or delete favorites, etc)

When a bet occurs in the game the details are collected on the developers side and been sent to us using custom parameters for the particular game, to be processed. In our example it would look something like this:
newGame?userid=nsqe-zrsa-7987&amount=5000000000&bettype=street&bet=street1
User nsqe-zrsa-7987 bets 50 NXT on a street. Based on provably fair random generation the outcome is decided and everything about the bet gets passed back to the developer in the API response to be displayed.