Excellent report Sckoarn!

Challenges were a huge endeavour indeed, this and adding testing upgraded the quality of the game but gameplay increased development payload "threefold" by creating a lot of maintenance and sense of emergency. But after a while we can feel we have established something durable, and also collection traits were "warming up", so to speak, now they gained utility and even usage.

For others, please note that Sckoarn does not use testing in any way or capacity for his own advantage and actually often involves himself less in playing his own challenges and so much more in testing!

He also does not test any "real situation" (any specific raid or condition that actually exists for a player) and only tests collections virtually. So again there is no advantage here.

Python is a language that Sckoarn decided to use to make his own tools but we don't use it on our servers. On the technical side we share javascript asset files, screen logs and JSON results. For raids, we evolved with even more, separately and very detailed JSON log sections. So we are mostly language agnostic and proposed a secured API url.

We only work with people we can trust and Sckoarn has been dedicated, generous, available and trustworthy. Thank you Sckoarn for your support! :)