Zarran API is a simple POST request based API. It can handle users, authentication, and (UNTESTED!) matchmaking.
Why?
A lot of people said POST requests didn’t work after the pinging block. After finding they worked fine () I decided to go make an API for the hell of it.
How use?
There’s a few endpoints you can access. The API accepts JSON data, and form data by default.
One example is /api/adduser, which takes a username and password and returns the UUID (The main method of accessing user data).
Why do the 2 modules include ChatGPT in the credits?
Some of the module code was indeed written by ChatGPT. Since it worked, it looked nice, and was fast, I kept it.
Some of it is my own, though. Not matchmaking. I haven’t touched that bull yet, I’m doing that after V2 (Once I’ve tested and fixed all the endpoints).
Have fun working with this pet project! and do not try to make a frontend in HTML and JS oh my god
Zarran API 1.0 What’s new?
I’ve tested (and fixed) literally EVERYTHING in the API. Everything works fully as intended, all the usual checks work, and Zarran API is now ready-to-go for production enviroments!
How do I use this again?
I’ll post the documentation at a later date. I’ll do that before I start on 1.1…
Zarran API 1.1: I’m naming these now. I’m going to call this one Procrastination… What’s new?
There’s documentation now! Check out the repository. Oh, and the frontend should be done soon. I think (Keyword: Think I)
How do I use this?
RTGD (Read the glitchin’ docs)! You can find them here now that I have them added: Glitch :・゚✧
(Yes, ChatGPT wrote them. It’s honking midnight and I refuse to write documentation this late)
Zarran API Frontend v1.0: IT’S HEEEEEERE
As my new years gift to you all, I release the FUNCTIONING Zarran API frontend! Feel free to remix and make it look… well, decent. Please tell me if you do that.
Anyway… The main page (example page) was written by ChatGPT, everything else was written by me without the help of an almighty AI that somehow knows how to fix any JS issue given enough time.
Zarran API v2.0 Beta 1: The Matchmaking Update
Matchmaking is NOW AVAILABLE via the API call startMatch! It takes a UUID and token.
Once 2 users are in the queue (And each user’s RANK data is within 50 of eachother), you’ll be paired together and given a mock server ID! I haven’t implemented readding the ID, so until it restarts to due to an error you’ll not get that same server again.
Can we talk about this though? No, seriously. There is NO DOCUMENTATION on something like this and it is fucking ass. I tried to ground-up make it, but I failed so I had to resort to modifying ChatGPT code AGAIN.
Zarran API v2.0 Beta 2: I hope Akismet stops flagging me already… Oh, and Authflow/Google ID token support
I added support for Authflow to the backend! You can now create users using an Authflow token. I have not documented the new calls yet, so wait until Beta 3 when I clean up the rough edges.
Oh, and hi! This is my home account. Yes, it is still me, the Zarran API creator.
Yeahhh. Took me a while to finish the encrypted DB- Wait a minute I forgot to post an update log Zarran API NPM Modules v1.0:
Some of the Zarran API code snippets / modules are now NPM modules! Check out zapi-matchmaking and authflow-helper