Another project had been finished, an accounts system, and an online leaderboard system, along with a registration page developed using HTML and BOOTSTRAP. All GML HTTP requests were handled with PHP & MySQLi, using highly secured PHP scripts and methods to avoid SQL injections and unauthorized POSTMAN & cURL requests. All the processing and heavy work is done on the server-side, and GameMaker merely sends a request to the server.

Players can create their accounts via the game's website or within the game, they can also log in to their accounts and keep their high scores in an online leaderboard that the player can choose to retrieve the "Top 100 High Scores" within "All Time," "This Year," "This Month," or "The Past 7 Days."

​

Features include but not limited to the following:

Considerable features:

[ACCOUNTS]
1. Log into and register accounts within the game.
2. Auto login if user checked "Remember Me"
3. Cookies and Score.
4. Unverified accounts will be deleted after 24 hours.
5. Advanced security with high performance.

[LEADERBOARD]
1. Local leaderboard displaying player's top 10 scores.
2. Online leaderboard displaying top 100 scores within [all time, this year, this month, past 7 days]
3. Scrollable leaderboard area to display 100 records comfortably.
4. rm_highscore_update updates highscore, just send the highscore variable there.
5. Local highscore is updated as well.
6. If no internet access is available, player will play offline.
7. Advanced security and high performance.


Many, many, MANY MORE features. Flexible code on the server and the client side.

Registration Page Design HTML & Bootstrap

Login System and Accounts Management

The client wanted a "lock system" for their private game, my client would have a control panel on a website, where he can create accounts and also remove them. The account holders are the only people allowed to play the game. Within the game, a login page is present in the opening. Once the account holder signs in (using their username and password), they would be transferred to the game, otherwise an error would pop-up and they won't access the game. The process is simple:

1. A player opens the game, he would be presented with a login page.
2. The player enters their login credentials, created previously by my client.
3. The game would connect to a database on a server and retrieve the user information if the login was successful, otherwise, they would receive an error message, "Login was unsuccessful!"
4. Once the player had logged in, they would be transferred to the game, and their online status will be "online."

My client is also provided with an easy-to-use control panel directly from their website, they can.

• Create accounts for new players.
• Remove accounts.
• Keep track of total logins, today's logins (in case someone else has been using the same account, one would know if an account had been used without permission), and their online status.

Real-Time Online Status System

One of the features in this system, and the one both my client and I are very proud of, is the real-time online status system. You can play the game and see which one of your friends is playing at the same time as you are, and when they have turned off the game.

The system is completely programmed using PHP and MySQL, and the heavy work is done on the server-side, on the client-side (the game and within GameMaker), the game just retrieves and updates information, therefore not slowing down the game with processes.

This system could also be incorporated into online games, html5 games, or mobile games, any game that requires keeping track of players' online status, as long as they have accounts.

Players that have logged into the game won't be able to log in again from another device or window. This could be helpful in identifying which account is being used.

I was hired to organized a project, debug it, optimize the codes, shorten them, and converte similar codes to functions/scripts to be reused. As well as add some features, including a one-way-platform.

An old project, I have developed this website for a client for his game, uZombie.

After we worked together on Blackjack, my client decided to renew the contract to develop a Roulette Wheel. Even though the development was a little challenging, the project was delivered within 3 days.

After trying out my asset, PapuDante emailed me to modify my Blackjack asset and develop a Multihand Blackjack game for him. Even though I had the Blackjack asset ready, I decided to build the game from scratch, to meet the client's expectations and include all the features he wants. As well as plan everything ahead for future updates.

The game took 5 days to be developed. And had been updated twice after delivery.