Skip to content

About

arjun fork

Resources

Stars

0 stars

Watchers

0 watching

Forks

 
 

Repository files navigation

Arjun's projects

Personal site hosted with GitHub Pages.

  • index.html: the home page, with links to the Web Development Projects, Productivity and Engineering Projects pages
  • projects/: the Web Development Projects page, with a full card for each game
  • productivity/: the Productivity page, with a full card for each tool
  • engineering/: the Engineering Projects page, with a full card for each engineering project
  • account/account.js: optional Google sign-in, added to every page with the shared top bar. Uses the rumblekarts Firebase project (same as the analytics and the Back Room games). Signed-in visitors get a row in Firestore members/{uid} (name, email, photo, first/last visit, page count and the analytics visitor IDs of their browsers), which the analytics dashboard shows under Signed-in visitors. The Back Room games reuse a signed-in account instead of switching to an anonymous one.
  • site.css: styles shared by the home, Web Development Projects and Productivity pages
  • hype-cycle-exchange/: Hype Cycle Exchange, a live classroom stock-market game (Firebase)
  • boxed/: Boxed, a competition math game with real AMC 10 and AIME problems: a Daily five, Practice, and live multiplayer games (Firebase, same project and Firestore rules as Hype Cycle Exchange; games are stored in games with kind: "math"). The page holds only contest names, problem numbers, official answers and a topic tag per problem (Algebra, Geometry, Number Theory, Counting & Probability); the problem text is loaded from the AoPS Wiki API while playing
  • e63334287a3deaa3/shell-crackers/: Shell Crackers (Back Room), a first-person egg shooter (Three.js, Firebase Realtime Database rooms under rooms/sc-…, same project and rules as Rumble Karts). Maps are block worlds (72 × 72 m; blocks are 1 m wide and 0.5 m tall, so stairs are rows of half-metre steps) built by the functions in MAPS (buildFarm, buildFactory, buildTown) from the tools above them: fill/clear, building (walls, floors, windows, doors, flat or gabled roofs), stairs, stairsDown, tunnel, and small props. The ground is 3 m thick so tunnels fit under it, and every call is also placed turned 180° about the centre so both halves match. Bots path over a navigation graph of every spot an egg can stand. The Training range (menu button under Practice) is its own map, buildRange with RANGE_MAP, kept out of MAPS so it never comes up in practice or online rotation: bullseye boards at 10/20/30/45/55 m, balloons that pop and come back, and unarmed dummies (DUMMY_ROUTES) that strafe or patrol and respawn after being cracked. Every gun is on keys 1–5 (6 is the pistol) and T resets the stats; the number keys stay fixed there, while T is the rebindable "Reset training stats" action in the Controls panel (keybinds.js) and the Pistol and Swap keys work on the range too. Magazines still need reloading but never run out, yolk bombs refill, and it has no clock, no rating and no database writes; its hit, accuracy and headshot counts live only in the open tab (Range in the page). On touch screens it adds a button for each gun and a Reset button (#tTrain) to the usual touch controls. Ranked rating: Elo from each match's finishing order, multiplied by 1.25^(real opponents − 1) (×1 for one real opponent, capped at ×3; bots-only practice ×0.4; first 10 matches move faster; leaving an online match after 45 s counts as last place). Ratings are stored at rooms/sc-ratings/players/<uid>, which the existing rules allow; each player's own browser writes their rating, so it isn't cheat-proof.
  • e63334287a3deaa3/trivium/: Trivium (Back Room), a trivia game: a Daily ten, Quick play by category, Survival, a 60-second Blitz, and live contests (Firebase, same project and Firestore rules as Hype Cycle Exchange and Boxed; contests are stored in games with kind: "trivia"; the host's screen grades answers and writes scores, players only write their own answers; invite links go through the home page as #tv-<code>). The question bank is in e63334287a3deaa3/trivium/bank/, one file per category; each row is [difficulty 1–3, question, right answer, three wrong answers, fact]. Questions get a stable ID from a hash of their text, so editing a question's wording makes it a new question. To add a category, add a file and a <script> tag for it in its index.html (and a color in CAT_COLOR). Keep every question and fact in your own words, and avoid facts that go out of date (current office-holders, records likely to be broken).
  • e63334287a3deaa3/showdown/: Showdown (Back Room), no-limit Texas Hold'em for up to 8 players (Firebase Realtime Database rooms under rooms/sd-…, same project and rules as Rumble Karts; invite links go through the home page as #sd-<code>). Everything travels through each player's own node: the dealer (the player with the newest dealer number, or with none yet, whoever has been in the room longest) runs the table and publishes it as JSON in tb, and seals each player's hole cards to that player's key in hc (ECDH P-256 + AES-GCM via Web Crypto), so the database never holds readable hole cards; players write only their own action (ac), sit-out (sit), rebuy (rb) and chat (ch). The dealer's browser does see every card, so it isn't cheat-proof against a dealer with developer tools. If the dealer drops, the next player takes over from the last table it saw and refunds the hand in progress. Bots (Easy, Normal, Hard) fill empty seats and run in the dealer's browser. Play chips only; nothing is stored between sessions except practice stats in the browser.
  • e63334287a3deaa3/chromaflage/: Chromaflage (Back Room), paint-yourself hide and seek for up to 8 players (Three.js, Firebase Realtime Database rooms under rooms/cf-…, same project and rules as Rumble Karts; Quick match uses rooms/cf-pub-1 to cf-pub-4; invite links go through the home page as #cf-<code>). Hiders paint their own bodies in a paint studio (brush, an eyedropper that reads the true colour of whatever surface you click, fill, undo, glossiness) and pose to hide; seekers tag them with a blaster whose misses cost ink. Modes: Classic and Infection. Like Showdown, everything travels through each player's own node at rooms/cf-<code>/players/<uid>, because the shared rules expect n, c, x, z, h, ts there and refuse other paths (such as events) for new prefixes: position and pose (y, po, fl, p), body (s shape, sz size, rf glossiness), paint (pv version and pd, the 256 × 256 body texture as a WebP data URL, or JPEG where the browser can't make WebP; about 1 KB for a plain colour and 10–20 KB for a detailed pattern, re-sent at most every 1.2 s and only when it changed, so late joiners read it straight from the node), the last shot (sh), squeak (ta) and tag claim (tg). The host (newest host number he, else whoever has been in the room longest) publishes the round as JSON in its own rs and checks tag claims loosely; if it leaves, the next player carries on from the last round it saw. Each body shape has a texture atlas where every texel knows its 3D spot on the body, so brushes paint by distance in 3D (atlasOf, Paint). Maps are axis-aligned boxes built by buildFlat and buildBazaar with the Builder helpers (box, at for turned furniture, prop for round things); the boxes are also the colliders, the bots' navigation grid and the surfaces the eyedropper and bots sample, and every pattern is drawn on a canvas by the P painters, from a fixed seed so all players get the same map. To add a map, write a build… function and add it to MAPS. The practice seeker bot "sees" by rendering a small view of you with and without you and comparing the colours (perceive, delta E), so better paint really does keep you hidden. Nothing is stored online between rounds; your name, body, last paint job and settings are saved in the browser under chroma-…. Parties can launch it (its row in GAMES in party.js). On touch screens the page adds touch to body, and the body.touch rules at the end of the stylesheet place the HUD, the lobby card and the paint studio for phones held upright or sideways (keep them clear of the stick and buttons when adding HUD pieces). The lobby card and the paint studio scroll an inner box (.lb-body, .st-body) instead of the card itself, because Chrome can leave a blank patch in the 3D view under a scrolling box with a solid background.
  • e63334287a3deaa3/backrooms-1v1/: Backrooms 1v1–4v4 (Back Room; the folder keeps its original backrooms-1v1 name), a third-person build-fight shooter in Level 0 of the Backrooms (Three.js). Practice is you against the Entity, a bot that runs only in your browser. Online rooms hold up to 8 players split into Red and Blue (1v1 to 4v4, uneven teams like 4v3 are allowed and never filled with bots) in the Firebase Realtime Database under rooms/br-… (same project and rules as Rumble Karts; invite links go through the home page as #br-<code>). Quick match waits in rooms/br-queue/players and pairs two people into a br-q… room for a 1v1. Each player writes only their own node players/<uid>: n, c, x, z, h and ts always (the shared rules expect that shape), plus height, pitch, health, shield, weapon, a dead flag, the match m and round rd the position belongs to, the team picked in the lobby t, kills this match k and join time j; about 20 times a second during a round (15 in rooms of 5 or more) and twice a second otherwise. The host is the live player who has been in the room longest (the next in line takes over when they leave; a newcomer only starts judging who the host is once the room's players and round have loaded, so a slow phone joining mid-match can't take over and reset it) and is the only one who changes round: {id, ends, seed, ns, ph, pt, to, rn, sr, sb, ro, dd, rw, mw, fm, rz}, where id is the match, ph the phase (lobby, cd countdown, fight, over, end), pt when the phase ends, to the rounds to win (3, 5 or 10, host's choice), rn the round, sr/sb the team scores, ro the roster (uid:r;uid:b), dd who is out this round, rw/mw the round and match winners, fm a forfeit, and rz the host's "Randomize teams" draw (each player then moves themself). The host writes with transactions guarded on id, ph and rn, and keeps ends at the time of writing because the rules cap how far ahead it can be. Shots, builds and deaths go through events/<push> (deleted after 5 s): the shooter's rays pass through teammates and the shot lists only the enemies it hit; the victim applies damage only from someone on the other team of the same match, and reports its own death naming the last shooter, which gives the kill credit. A round ends when one team has nobody left: dead, or silent for 10 s (a closed tab removes its node at once). A team with nobody left in the room (disconnected, or silent for 20 s) forfeits the match. A host whose own tab has just frozen waits a moment for the queued updates before judging anyone. Players who join mid-match wait in the lobby or watch until the next one, and dead players watch a living teammate (click, or tap Next on a touch screen, for the next one). The maze is 12 × 12 cells of 4 m, 14 for 5–6 players and 16 for 7–8; Red spawns along the west edge and Blue along the east, each spawn in a cleared 3 × 3 area. On touch screens it has a move stick, drag-to-look, Fire/Place, Jump, Aim, Reload and pause buttons, with the weapon and build slots as buttons along the top; while you watch, those give way to a Next button, and the lobby, pause and results screens are plain buttons that fit a phone either way up. Each browser is trusted for its own health and hits, so it isn't cheat-proof. A test hook (window.__br) exists only when navigator.webdriver is set.
  • e63334287a3deaa3/slipstream/: Slipstream (Back Room), a 3D open-wheel racer with a 22-car grid (Three.js, Firebase Realtime Database rooms under rooms/ss-…, same project and rules as Rumble Karts; invite links go through the home page as #ss-<code>). Bots fill every free seat; the host's browser drives them. Bot skill (DIFF: Easy, Normal, Hard; online races use Hard) scales corner speed, and the bots' braking, boost and lines are tuned by the AI constants; Hard runs close to a near-ideal lap. Track limits: going off costs nothing but time (a small "Return to the track" hint shows while off), and cutting a corner to gain time adds 1 s to the race time; each car's total penalty seconds travel online in pn. Nothing else is saved: settings (name, last room, seat, track, laps, difficulty, camera, mute) stay in the browser under ss: keys. In automated browsers only (navigator.webdriver), window.__ss exposes the race code so a test can run bots-only races and time laps.
  • e63334287a3deaa3/party.js: Parties (Back Room). A Party panel above the games: create a party (5-character code) or join one, up to 8 people; the person who has been in it longest is the leader, picks a multiplayer game and presses Play together, and every member's browser opens that game in a new room (#<prefix>-p<6 random characters>) and joins it. Back returns everyone to the party. Party invite links are /#pt-<code>: the home page holds them until the Back Room code is entered, then joins the party instead of opening a game. Works on the phone version too (m/index.html loads party.js, lends it its openGame, and sends #pt- invites to the party instead of Rumble Karts), and both after the home-page reveal (the home page's reveal() loads party.js from the Back Room folder and lends it openGame through window.BackRoom) and on the Back Room page opened directly (a <script> tag; games then open in party.js's own layer). Storage: Firebase Realtime Database, same project and rules as Rumble Karts, at rooms/pt-<code>/players/<uid>. The rules only let a browser write its own node and require the same fields the games write (n, c, x, z, h, ts; x/z/h are always 0), so the party keeps everything there: j (join time, which decides the leader), pk (game the leader picked) and go (the leader's latest launch: game, room, time). Nodes are removed on disconnect and ignored after 2 minutes without a heartbeat. Supported games: Shell Crackers, Rumble Karts, Kartwheel, Slipstream, Boostball (6 max), Coil, Showdown, Quarry, Backrooms 1v1–4v4, and Hail Mary (2 max; switched off for bigger parties). Trivium isn't supported (its contests get their code from the host's screen). party.js joins the game for each member by filling in the game's room box and pressing its own Play in room button (#room / #joinRoom, and #name only if empty), so the games themselves weren't changed: keep those ids if you rework a game's menu. To add a game, add a row to GAMES in party.js (prefix, folder, room size, and ids if its menu uses other ids).
  • e63334287a3deaa3/keybinds.js: rebindable controls shared by the keyboard Back Room games (Boostball, Coil, Hail Mary, Kartwheel, Quarry, Rumble Karts, Shell Crackers, Slipstream, Starhop). Plain JavaScript, no dependencies. Each game loads it with <script src="../keybinds.js"></script>, lists its actions in Keybinds.create({game, actions: [{id, label, keys: ['KeyW', 'ArrowUp']}]}) (keys are e.code names, so they're physical keys on any layout; mouse buttons are Mouse0/Mouse1/Mouse2 in games that pass mouse: true), checks input with KB.is(action, e.code) and KB.held(action, keys) instead of comparing key codes, and opens the panel from a Controls button with KB.open(). Changed keys are saved only in the player's browser, under localStorage keybinds:<game> as {v: 1, b: {action: [codes]}} (only the actions that differ from the defaults; Reset to defaults removes the entry), and never go to Firebase. Esc is never rebindable. Elements with data-kb="action" show the current keys and update themselves. The panel takes each game's look from --kb-* CSS variables and the game's own button classes; the comment at the top of the file lists the options. To add it to a game, do the same, and keep text inputs (names, room codes, chat) returning before any key lookup. Touch controls don't go through key codes: each game's touch buttons feed its input directly (in Shell Crackers and Quarry they hold actions by id in tAct, which the game checks alongside KB.held), so they keep working whatever keys are bound, and the Change keys / Controls buttons are hidden in the touch layout (body.touch).
  • joukowsky-dynamics/: only preview.jpg (used by the Engineering cards) and a redirect page. The Joukowsky Dynamics workbench itself is hosted, password protected, on the Joukowsky-Dynamics repo's own GitHub Pages site, https://ascoding11.github.io/Joukowsky-Dynamics/, and the cards link there. Don't put an unprotected copy back in this repo, or it would bypass the password.
  • docket/: Docket, a study planner for Canvas students (plain JavaScript, no backend; everything is saved in the student's browser). It imports assignments three ways: a bookmarklet that reads the Canvas API from the student's logged-in Canvas tab and hands the data to Docket in the URL hash (its source is the bmSrc block in the page), the Canvas calendar feed / any .ics or Google Calendar .zip export, or pasted text from a Canvas assignments page. It estimates time and difficulty per assignment, then schedules study sessions around calendar events and the student's activities. No ads on this page.
  • prompted/: Prompted, a supplemental essay tracker for college applicants (plain JavaScript, no backend; everything is saved in the student's browser under prompted:v1). Students add schools with a plan and deadline, paste a supplement page to pull out each prompt with its word or character limit and whether it's optional (parsePrompts in the page), write drafts with a live count, save and restore versions, and start new essays from existing drafts. A reuse map groups similar prompts across schools by kind (Why us, academic interest, community, and so on). Backups download as JSON; all drafts download as one .txt. prompted/schools.js is the school library: the U.S. News 2027 top 50 national universities with their 2026–27 supplement prompts (as short summaries in our own words, with real limits), choose-N sets, college- or program-specific prompts keyed to the student's intended major, application plans and deadlines. UC campuses share one application, so they're added as a single school. Update the file each August when schools publish new prompts, and keep every prompt as a summary in your own words: don't paste schools' official prompt text into this repo, even though it's posted publicly. No ads on this page.
  • e63334287a3deaa3/m/: the phone version of the Back Room: every game (the Back Room ones plus Boxed and Hype Cycle Exchange) as a tile, grouped by kind. A game opens full screen in a frame under a thin bar with the way back, and the last one played shows at the top as Keep playing. It can be added to a phone's home screen (manifest.webmanifest, icon-*.png), where it runs like an app; on Android it also goes full screen and turns sideways games sideways. Tiles use the small copies in m/thumbs/ (560 × 350) rather than the full previews. On a phone, entering the code on the home page opens this page in place of the Back Room, still at the home page's address, and invite links (#<room>) open their game straight away. The Back Room page also links to it (data-direct, so the home page opens it as its own page instead of in its game layer); that address is the one to add to a home screen. It isn't in the sitemap or linked from the public pages.

Touch: every game plays on a phone. Each game draws its own touch controls (a move stick, buttons, and drag-to-look for the first-person games) and shows them only on touch screens (pointer: coarse, or after the first touch), so the keyboard-and-mouse version is unchanged. The first-person games (Shell Crackers, Backrooms 1v1–4v4, Quarry) skip pointer lock on touch screens; in Quarry, taps in the inventory and crafting screens go to the same code as mouse clicks.

Ads: Google AdSense runs only on the game pages. The home page carries just the google-adsense-account meta tag, which verifies the site with AdSense without loading any ads. ads.txt (site root) and privacy.html are required by AdSense. Hype Cycle Exchange uses automatic ads; the other games show banners only on their menu and results screens, switched on by pasting a display ad unit ID into AD_SLOT near the top of each game's script.

The game's secret results file (rounds.json) is intentionally not in this repository. Keep it on your own computer and choose it when you host a game.

About

arjun fork

Resources

Stars

0 stars

Watchers

0 watching

Forks

Releases

Packages

Contributors

Languages