Wow, you're getting the point. This is big and it is a captive portal that you can place anywhere you want. It's a nearer cafe or in a public place and it will present itself as an access point. And you use the captive portal mechanisms of mobile devices to bring up a screen with your content in that case games. And the way it works is it intercepts the DNS queries. Well, it actually doesn't really intercept them. It just lies to the mobile device. And whatever is requested, it answers with its own IP addresses. You can see here on this diagram. And then it will of course serve HTML pages, HTML files from the local file system. And whatever is requested, if it does not know it, it will always send the index file. And you can work on from there. And this is how it works. First of course, you have to grab the code from my GitHub repository. It's called captive intro web. Well, because that's what it is, a captive intro web. And you have to upload all the files to your ESP module. The most notable files are the DNS layer, which is aptly called. So because it's lying to DNS requests, always sending back the modules IP address. The other important one is the server to the lower, which is the actual HTTP server that will respond with the index HTML file to everything it doesn't know. And if it does no other files, it will just send them. Here I'm uploading a small PNG picture. So if you don't overdo it, you can also get away with some smaller pictures. And the actual game files make up the biggest chunks here in the uploads because they contain a lot of JavaScript. So I try to roll them all into one compact file. Of course, you will need custom made node MCU firmware that will hand out DNS server address upon the HTTP requests. I can't really distribute that, but it's not hard to compile. There are lots of instructions out there by now on how to do it. And all you have to do really is set the flag for the DHCP DNS feature and a little just give the client that connects to the software IP, the DNS address, namely itself. You have to execute the apmode.lua file because that will set the module into soft ap mode and it acts as an access point from then. Now power should not be an issue with a 18650 battery. We need a battery holder for it. They come cheap from China. And this battery is cheap as well. Under that, he drink cubing. There's a silicon diet there where we drop 0.6 volts not to overload the module. I'll connect it up the usual way. We go insert the battery and we're up and running. By the way, if you restart the module like you do now, you see in the blue LED flashing couple of times that indicates that it had a good start. Now we need the magnets and place them underneath the battery. They'll stick to the battery which is really handy. Insert it into the box. Fit it all in. And seal it. So that's supposedly a rain proof. So it can stay out. And you'll stick to any metal surface. And you'll see a new Wi-Fi network. If you connect to that, it'll bring up this captive portal and you can play games on it. Yay. Now we're going to use dirty construction techniques. I'll just cut the wires, strip the insulation. And I fast forward that. We need two positive wires. One for the actual current. The other one's just for this chip-enabled pin. And that's a three-volt button cell. Three volts should be sufficient for the module. Positive and chip-enabled. And of course the negative. And I will just tape those directly to the button cell. So I'll connect the black wire to the negative terminal of the button cell. Sorry you can't see that on the camera at the moment. Here we go. And I'll use the magnet to connect the positive wires. And now LEDs should have lit up which they apparently don't. And so another dryer. It's all connected properly. No. Nothing wrong there. Looks good. It's got to work. That's too dim. Well I suspect the battery just isn't up to the job. I will read up on that. I might have known. So no, this throwy does not work.