Why is Strikr back with a new domain?

As a dedicated Omega Striker myself, I loved using Strikr. Especially since it gave so much more and cleaner information than Corestrike.gg. But like many I found Strikr gone someday.

The last few days I’ve been pondering how I should spend my time and thus came the idea of just asking the original developer of Strikr Nodgear on what happened. It turned out that it was a conscious decision from him to take Strikr offline, due to missing time and dwindling interest in the game. After some back-and-forth, he was so kind to give me the front- and backend code for the website. With the code in hand, I went forth to resurrect Strikr and now here we are.

Sadly it’s currently not possible to use the old .gg Domain, so I’ve decided to go with .pro for now.

I will post some details on how I achieved this and the hurdles that presented themselves, at a later date on my personal blog.

Who is currently working on Strikr.pro

Currently there are two people working on Strikr.pro: lukimana and Achi.

Feature XY doesn’t work and Nao and Mako are missing!

Yeah, as expected. I’m not a developer nor do I have a deep understanding of coding. I was barely able to get the site up and running. Strikr hasn’t been updated for a good amount of time. I’m planning to update the site with the latest champs and awakening, but it will take me some time if I’m even able to achieve it. There is a reason why I’m just calling myself the maintainer and not the developer!

But if you are a developer who knows TypeScript and NodeJS and wants to contribute, please feel free to hit me up!

You can check the status of Strikr on the status page. This should at least give you an indicator if the code is just bugged at the moment or if the site is down. And yes if the status page tells you that the site is down, then I also already know.

Please don’t ask Nodgear about anything regarding the site. He has been a great help in teaching me about his code but in the end he decided for himself to stop supporting Strikr.

Can you add feature XY?

No. It’s not that I don’t want to but as I said, I’m missing the necessary skills to actually modify the code. If you know how to code and maintain such a project or know someone who might, just hit me up!

Can you share the code?

Strikr is broken down into two parts, the Front- and back end. The front end consists of the site itself while the Backend handles the Database and API calls. You can find the Repository of the Frontend here.

The Backend is more complicated. I’ve tried to answer it in the next question.

Where’s the API?

That’s a tricky question. Strikr used to have a free API that worked as the middleman between the API from Odyssey Interactive and your client. I’ve decided for now to not make this API publicly available due to a few reasons.

  1. I’m not 100% sure how it works. I know that it does work for now, but I’m fuzzy on the details. I can’t tell you if the inputs to that API were ever sanitized or if there is a chance of an exploit.

  2. During its lifetime there were apparently 150k unique API calls. I’m not sure if the current machines can handle those numbers.

  3. And lastly, in the end, this API just makes the same API calls to Odys API to get all the information. It was an enormous challenge to get the proper API-Tokens to even make calls to Odys API. I had to sniff out the right tokens and correctly use them with the endpoints to get it working. There is no official documentation on how to use Odys API. The former developer Nodgear was in contact with Ody about using their API, but apparently, even he didn’t get any help using it.

Since Odys API is getting used without proper permission and the fact that it’s not documented, I’ve decided to keep the backend code private for now, as well as the Strikr API.

I’m not ruling that out that the API might come back in the future. But as it stands, for now, the API as well as the backend code, will stay private. Maybe there will be a separate blogpost about the path that I had to take and documentation on how to use the Ody API yourself.