playskyfall.fun
“Skyfall · Ten drop in. One walks out. The winner gets paid.”
Tech check
What the site says about itself, next to what its public page actually loads. Facts only, no verdict: you decide.
Wallet connection
“…n SOL, sent to the address you paste. Free to play, no wallet connect. THIS BATTLE ROYALE PAYS THE WINNER 0.0652 SOL POT 0.4…”E24
No matching code, calls or services in what loaded for us.
What it is
- The site describes itself as: “Skyfall: a battle royale with building in your browser. Ten drop from a blimp into a city, loot guns and shields, build walls, ramps and flo”E2
- Notable building blocks in its code: Three.js (3D graphics).E6
- In your browser it can copy text to your clipboard, saves small bits of data in your browser, keeps a live two-way connection open to a server and runs compiled WebAssembly code in your browser.E7E8E9E10
- It has sections such as /ledger and /docs.E23
- While loading, it called 4 endpoints on its own servers, such as /media/tex/manifest.json, /media/guns/guns.json, /media/chars/chars.json and 1 more.E13E14E15E16
Where your data goes
On a first visit the page only talked to its own servers (playskyfall.fun).
How key features work
Sign-in and accounts
Sign-in and account features show up in its code or traffic (/api/account).E22
/api/accountLive updates
It keeps live connections open (WebSockets) so content updates without reloading.E9
websocketLoading its content
Its content loads from its own API while you browse (/media/tex/manifest.json, /media/guns/guns.json, /media/chars/chars.json and /api/clientperf).E13E14E15E16
/media/tex/manifest.json/media/guns/guns.json/media/chars/chars.json/api/clientperfCookies and storage
Names only. We never store the values.
localStorageE5: ramp.pid
Pages and API calls
Pages it links to
//ledger/docsEndpoints
Called while loading (seen) or named in the code (code).
| playskyfall.fun/media/tex/manifest.json | seenE13 |
| playskyfall.fun/media/guns/guns.json | seenE14 |
| playskyfall.fun/media/chars/chars.json | seenE15 |
| playskyfall.fun/api/clientperf | seenE16 |
| /media/guns/guns.json | codeE17 |
| /media/tex/manifest.json | codeE18 |
| /api/clientlog | codeE19 |
| /api/clientperf | codeE20 |
| /api/live | codeE21 |
| /api/account | codeE22 |
Evidence
Every sentence above points to one of these. Code references show the file, line:column and the short identifier that matched, never the site's code itself.
Limits
- We only see what your browser sees: code and requests on a first visit, without logging in or accepting cookie banners. What the servers do with data is invisible from outside.
- Site code is usually minified (compressed), so names are partly lost and some code may be only partly analysed.
- Some trackers only load after you accept cookies or log in, so the real list can be longer.
- We visited from a server in the United States. Sites load different trackers and cookie banners in different countries (visitors in the EU usually get a consent banner first).
- The tech check compares the site's own words with what its public page loads. Work done on servers, in private code or in separate apps isn't visible here, so 'nothing found' means not visible on the public page, not that it doesn't exist.
- This text was written from fixed templates because no AI writer was available. It uses exactly the same evidence.
- REA hit its size budget on parts of 26 large bundle file(s); those parts weren't fully analysed.
Facts, not judgements: this page describes what the code and traffic show, not anyone's intent. Not financial advice. Case id yhlW1V1u.