The screenshots can be made
fairly easily by modifying the javascript calls so the reels stop in whichever location you want. That way you can guarantee a screenshot without having to manipulate any graphics via image editing. You just host the front end javascript on your own local server and then make the API call to your own script instead of the one on the cloudfront server. For example you could set these reel positions via simple variables:
Code:
data.response = &MSGID=BET&B=100120&VER=2.5.1751-2.5.2282-2297-4&RID=5&NRID=0&BPR=5&RB=6&RS=[B]15|163|160|85|73|22|[/B]
.
These numbers will attain to certain positions on the reel strips.
Why the bottom text values are off by £315 is beyond me, as it seems they put some time into getting the screen right, but this could be due to changing some variables and not others in the backend correctly. On inspection though the 0 character on the balance seems off (not in line with all of the other character heights for that group, when it should be via the code), so they could just of made some bad math judgement when manually editing this text via image editing.
There are some very interesting parts within the front-end coding of this game. Notably the maxWinnings variable, and the fact that
it seems impossible to win more than 2743x stake by design. I do want to add that this doesn't mean that the slot doesn't payout the RTP % it states, but to expect that a
serious monster win can happen is simply not possible and probably the reason we haven't seen such screenshots.
Feel free to visit the game on any provider, in Chrome right click, then press Inspect. Find the file named dragonborn.min.js and download it. You may want to beatify it via jsbeautifier. This holds the front end code for the game. (
Not the information regarding the actual reel land locations etc. This comes from the data.response which is server-side code) It can then be pieced together fairly easily for anyone with a simple understanding of Javascript programming.
Happy reading
- T