Website profiles · Technology insights · Alternatives

puyo.gg

A new site for competitive Puyo Puyo.

Games & Board Games gatsby React bootstrap

No paid content found

Visit website

Profile views 0 Outbound visits 0 Normal

At a glance

Category: Games & Board Games
Language: English
Paid-content signal: No paid content foundObserved
Registered: Unknown
Hosting: NetlifyInferred
HTTPS certificate trusted: PassedObserved
Last updated: 2026-10-21 18:12

Website review

This review may include AI-generated content and is not individually verified. Domain, certificate and other facts come from the observed data on this page.

What is puyo.gg?

puyo.gg is a learning site for competitive Puyo Puyo, built around structured lessons, chaining drills and a chain simulator. Its author, S2LSOFTENER, frames it as a resource for a "rising puzzle esport," and the material is aimed at players who want to move from knowing the rules to building chains deliberately and playing competitively.

What you'll find there

Lessons: a numbered course from "Introduction to Puyo Puyo" and "The Basics of Chaining" through patterns (Stairs, Sandwich, GTR and extensions, L-shape), then competitive topics such as the scoring formula, garbage management and harassment strategies. Three starred advanced lessons cover the 13th row, optimizing placement speed and special topics.
Chaining Drills: a long list of practice setups labelled by form and chain length, from simple 2- and 3-chains up to named high-end forms like Tanaka Special, Sullen GTR and Kenny Formula at 12–19 chains.
Form Index and Chain Simulator: a reference for named forms, with the simulator currently pointing to the Puyo Nexus Wiki's chain simulator for playable practice.
Community: an invitation to join other competitive players.

One practical constraint: much of the content is rendered with Pixi.js and needs WebGL, so if drills or animations fail to appear, enabling hardware acceleration in your browser settings is the first thing to try.

Who it suits

It fits a player who has learned the basic rules and wants a curriculum rather than scattered videos — working through the numbered lessons in order, then drilling the matching forms. The drill labels double as a difficulty ladder: start with the 2- and 3-chain basics, and treat GTR, Sandwich and L-shape variants as later milestones. If you mainly want to play casually, the competitive framing (scoring, harassment, placement speed) may be more than you need.

For background material beyond this site, the Puyo Nexus community is the natural companion. As a next step, open the first lesson and one Basics 2-chain drill side by side, and repeat the drill until you can build the chain without pausing.

Do I need WebGL or hardware acceleration enabled to use puyo.gg?

Yes. puyo.gg states that it requires WebGL, and that much of its content is built with Pixi.js, a WebGL-based animation framework. The site warns that content will not load if your browser does not have WebGL enabled, and directs you to turn on hardware acceleration in your browser settings.

What this means in practice

Lessons, drills and the chain simulator: these are the core learning tools on the page, and they are the parts most likely to depend on the animated, WebGL-rendered content. Expect blank or non-loading panels if WebGL is off.
Hardware acceleration is the usual switch: in most browsers, WebGL depends on hardware acceleration being enabled. If the site loads but drills stay stuck on "Loading! Please wait.", hardware acceleration or WebGL is the first thing to check.
Older or locked-down machines: office laptops, virtual machines and browsers with GPU features disabled are common failure cases. If you cannot change those settings, the site is not a good fit on that device.

A quick check

Open a WebGL test page in the same browser. If it reports no WebGL support, enable hardware acceleration in your browser settings, restart the browser, and reload puyo.gg. If WebGL works elsewhere but puyo.gg still stalls, try a different browser before assuming the site is broken.

For background on the game itself while you sort out browser settings, the Puyo Nexus community is the long-running reference point the site itself points to.

Which lesson should I start with if I'm new to competitive Puyo Puyo chaining?

Start with Lesson 1, "Introduction to Puyo Puyo," then move straight into Lesson 2, "The Basics of Chaining." The site orders its lessons as a progression, and those two are the foundation everything else builds on: Lesson 1 gives you the rules and board concepts, and Lesson 2 introduces how chains actually form before you touch named patterns.

A sensible first path

Lesson 1 – Introduction to Puyo Puyo: learn the pieces, the board, and what a chain is.
Lesson 2 – The Basics of Chaining: practise triggering simple chains rather than stacking randomly.
Lesson 3 – The Stairs Pattern, then Lesson 4 – The Stairs Turn Around: your first real, repeatable form.
Lesson 5 – The Sandwich Pattern: a second core shape so you aren't reliant on one pattern.
Chaining Drills: use the drill links labelled "Basics: 2 Chain" and "Basics: 3 Chain" alongside these lessons. They are the practical counterpart to the reading.

What to skip for now

Lessons 6–9 (color conflicts, L-shape, tailing) and everything from Lesson 10 onward (GTR, scoring formulas, garbage management, harassment) assume you can already build and fire a basic chain. The starred special topics, "The 13th Row" and "Optimizing Placement Speed," are refinement material, not starting points.

Practical notes

The site states that much of its content is built with a WebGL animation framework and will not load without WebGL, so enable hardware acceleration in your browser before you begin; otherwise the lesson visuals and drills will appear blank or stuck on "Loading! Please wait." For a playable board to experiment on outside the drills, the site points readers to the chain simulator on the Puyo Nexus Wiki, and the community around Puyo Nexus is where competitive players discuss forms and matchups.

A reasonable decision rule: if you can't yet build a 3-chain deliberately, stay in Lessons 1–5 and the 2- and 3-chain drills. Once you can, Lesson 10 on GTR is the natural next step, since it is the standard competitive opening shape.

How can I practice a specific chain pattern like GTR or Sandwich using the drills and simulator?

Use the Chaining Drills section to load a named pattern and repeat it until the shape is automatic, then use the Chain Simulator to build and test your own variations. The drill library already labels patterns by name and length—GTR entries range from 7 to 13 chains, and Sandwich entries from 10 to 16—so you can pick a target that matches your current level rather than guessing.

A practical practice loop

Start with the lesson, not the drill. Read the relevant entry under Lessons first: "GTR and Common Extensions" for GTR, "The Sandwich Pattern" for Sandwich. The drills assume you recognise the shape.
Load the shortest drill for that pattern. For GTR, begin with the 7-chain drill; for Sandwich, the 10-chain drill. Short forms are easier to verify by eye.
Watch the animation once, then rebuild it from memory. The drills are animated, so resist the urge to copy piece by piece.
Repeat until you can place the first three or four pieces without pausing. The opening placement is what decides whether the pattern forms at all.
Step up one drill at a time. Move from GTR 7 to GTR 12, or Sandwich 10 to 15, only after the previous one feels routine.
Use the simulator for your own variants. Once a pattern is solid, change the tail or colour order and check whether the chain still resolves as expected.

Choosing between drills and the simulator

Goal	Better tool	Why
Learning a named shape	Chaining Drills	Fixed, labelled patterns with known chain counts
Fixing a specific mistake	Chaining Drills	You can return to the same setup repeatedly
Testing your own build	Chain Simulator	Free placement without a preset answer
Comparing pattern lengths	Both	Drills give reference counts; the simulator lets you extend them

What to expect technically

The page states that much of its content is built with Pixi.js and requires WebGL; if hardware acceleration is off in your browser, the drills and animations will not load. Check that before you sit down to practise, since a blank drill panel is a settings problem, not a mistake on your part.

A concrete scenario

Suppose you can build GTR but keep misplacing the turn that extends it. Work through the 7-chain GTR drill until the base is clean, then open the 12- and 13-chain versions and note exactly where the extra pieces attach. Rebuild each from scratch twice, then switch to the simulator and try the same extension with a different colour order. That sequence separates shape memory from colour-dependent decisions—the distinction the site's own "Color Conflicts" lessons address.

For background reading on pattern names and notation, the site points to the Puyo Nexus Wiki, and Puyo Nexus hosts the community the author directs readers toward.

What advanced topics like the 13th Row or placement speed optimization are covered for experienced players?

puyo.gg marks its advanced material with a star and lists three "Special Topics": The 13th Row, Optimizing Placement Speed, and a third entry shown only as ★3. Special Topics, whose subject isn't named in the page text. The first two are also cross-referenced from the main Lessons index, so they sit alongside the numbered beginner-to-intermediate sequence rather than in a separate silo.

What the page shows about each

The 13th Row appears twice in the index (once as ★1, once under Special Topics). The name points to the row above the visible playfield, where incoming nuisance Puyo queue up — so expect material on reading and managing that hidden buffer rather than on building chains.
Optimizing Placement Speed (★2) is about execution: getting pairs where you want them faster, which matters once chain knowledge stops being the bottleneck.
★3. Special Topics has no description on the page, so what it actually contains can't be confirmed from this evidence.

Where experienced players will get more value

The numbered lessons go well past the basics: Garbage Management (12) and Harassment Strategies (13) are competitive-play topics, and The Scoring Formula and Power Chains (11) covers the maths behind chain value — useful if you're deciding whether a longer chain or a faster, smaller one wins a given exchange. The Form Index collects named shapes (GTR and its extensions, L-Shape variants, Sandwich, Tanaka Special, Yayoi Fusion, Sullen GTR, Kenny Formula, Hellfire), and the Chaining Drills list pairs each with a target chain length, from 2-chain basics up to a 19-chain Kenny Formula. That drill list is the most concrete advanced resource on the page: you can jump straight to a shape and a length and practise it.

Practical caveat and next step

The site states that much of its content is built with Pixi.js and requires WebGL; the drills show "Loading! Please wait" placeholders until that renders, so enable hardware acceleration before a practice session. If you're an experienced player planning a routine, start with a drill for a form you already use (for example a GTR or Sandwich entry at your current chain length), then read The 13th Row and Garbage Management together — the first tells you what's coming, the second what to do about it. For wider reference material, the page points to the Puyo Nexus community, whose wiki and simulator live at Puyo Nexus.

How can I support puyo.gg through Puyo Nexus Patreon donations?

Go to the Puyo Nexus Patreon page and choose a membership tier there; puyo.gg itself does not process donations. The site's own welcome note asks readers who find its lessons and drills helpful to "consider donating to the Puyo Nexus Patreon," so the Patreon campaign is the stated support channel for this project.

What your support covers

puyo.gg is a learning resource for competitive Puyo Puyo, run by S2LSOFTENER. Its content is organised into numbered lessons (from "Introduction to Puyo Puyo" through "Garbage Management" and "Harassment Strategies"), starred special topics such as "The 13th Row" and "Optimizing Placement Speed," a Form Index, and a large set of interactive chaining drills built with Pixi.js. That drill library—chains ranging from simple 2-chains to GTR, Sandwich, L-Shape and Kenny Formula patterns—is the kind of material Patreon support helps keep online and expanding.

A practical next step

Before pledging, work through a few lessons and drills to confirm the site suits how you learn. If the interactive format clicks for you, a Patreon membership is the direct way to give something back. If you are new to the game, start with Lessons 1–3 and the "Basics" drills, then decide.

One technical note

Because much of the site uses WebGL, enable hardware acceleration in your browser settings; otherwise the lessons and drills will not load. This matters if you plan to use the site regularly, since a broken display makes it harder to judge whether supporting it is worthwhile.

For broader Puyo Puyo reference material alongside these lessons, the community wiki at Puyo Nexus is the usual companion resource.

Why a Puyo site would use Gatsby

Gatsby generates pages ahead of time as static files, so lesson pages, the form index, and topic lists can load quickly without a server rendering each request. That fits a content-heavy training site where most pages change rarely.

The interactive parts are a different story. puyo.gg states that much of its content is made with Pixi.js, a WebGL-based animation framework, and that the site requires WebGL. So the architecture is roughly two layers:

Layer	Technology	What it handles
Page shell and content	Gatsby (React-based)	Lessons, Special Topics, Form Index, navigation
Interactive content	Pixi.js / WebGL	Animated drills, chain simulator, visual demos

React appears because Gatsby is built on it; components for lesson lists or drill cards are React components compiled into static pages. Bootstrap, the third keyword, is a CSS framework for layout and styling, separate from both.

Don't confuse the tech stack with the lessons

The keywords describe how the site is built. The actual teaching content is listed on the page itself:

Lessons 1–13, from "Introduction to Puyo Puyo" through "Harassment Strategies"
Special Topics: The 13th Row, Optimizing Placement Speed
Chaining Drills with named forms such as GTR, Sandwich, L-Shape, and Tanaka Special
Chain Simulator, linked out to the Puyo Nexus Wiki simulator

None of these depend on knowing what Gatsby is. A reader who wants to learn chaining can ignore the framework entirely.

If content won't load, check WebGL first

A blank drill or simulator is more likely a graphics problem than a Gatsby problem. The site explicitly warns that content won't load if the browser lacks WebGL and advises enabling hardware acceleration in browser settings. Work through that check before assuming the build framework is at fault:

Confirm hardware acceleration is on in your browser settings.
Reload the page and see whether the drill or simulator renders.
If it still fails, try a different browser that supports WebGL.

Gatsby's role is delivering the page; WebGL's role is drawing the animated Puyo content inside it. Separating the two makes troubleshooting straightforward.

What Is React and What Is It Used For?

React is a JavaScript library for building user interfaces out of reusable components. You reach for it when a page needs to change state without a full reload — feeds, dashboards, editors, shopping carts — and you want to describe those changes declaratively instead of hand-editing the DOM. It handles the view layer only; routing, data fetching, and build tooling come from other libraries or a framework like Next.js.

The core ideas

Components

A component is a function that returns markup. You compose small ones into larger ones, which is why React scales from a button to a whole application.

function Greeting({ name }) {
  return <h1>Hello, {name}</h1>;
}

JSX

JSX is the HTML-like syntax inside JavaScript. It compiles to plain function calls, so it is not a template language you have to learn separately — expressions, loops, and conditionals are just JavaScript.

Props and state

Props are inputs passed down from a parent. They are read-only inside the component.
State is data a component owns and can change. Changing state re-renders that component and its children.

import { useState } from "react";

function Counter() {
  const [count, setCount] = useState(0);
  return <button onClick={() => setCount(count + 1)}>{count}</button>;
}

The mental model: UI is a function of state. You update the data, React works out the minimal DOM changes.

What people build with it

Use case	Why React fits
Single-page apps	Client-side routing swaps views without reloads
Interactive UI (forms, filters, drag-and-drop)	State changes map directly to re-renders
Dashboards and data views	Components compose into tables, charts, panels
Content-driven sites	Pairs with static-site generators and headless CMSs
Cross-platform apps	React Native reuses the component model for mobile

How React relates to Next.js and other tools

React is the library; Next.js is a framework built on top of it that adds routing, server rendering, and data fetching. The distinction matters when you pick a starting point:

Plain React (via a bundler like Vite) — you assemble routing and rendering yourself. Good for SPAs and learning the fundamentals.
Next.js — file-based routing and server-side rendering out of the box. Good for sites where SEO and first-load speed matter.

Both are common in the same stack. For example, a site can be built on Next.js for routing and rendering while a headless CMS handles content editing — TinaCMS, for instance, describes itself as adding real-time visual editing to React websites and stores content as Markdown in a Git repo, which keeps the content portable and readable by other tools.

Starting a React app

The fastest path is a scaffolding tool. With Vite:

npm create vite@latest my-app -- --template react
cd my-app
npm install
npm run dev

Expected result: a dev server starts (Vite prints the local URL, typically http://localhost:5173) and you see the default page. Edit src/App.jsx, save, and the browser updates without a manual refresh.

If you want a content-driven site instead, TinaCMS documents a one-command start:

npx create-tina-app@latest my-blog

That scaffolds a Markdown repository ready for editing. Note that TinaCMS publishes a pricing page, so check current terms there rather than assuming the hosted editing experience is free — the open-source toolkit and any paid tiers are separate questions.

Common sticking points

State updates look asynchronous. Reading count right after setCount gives the old value. Use the updater form (setCount(c => c + 1)) when the next value depends on the previous one.
Mutating props or state directly. React compares references; mutate an array in place and it may not re-render. Create a new array or object instead.
Reaching for global state too early. Most sharing is solved by lifting state to a common parent. Add a state library only when prop drilling becomes the actual problem.
Confusing React with the whole app. React renders the view. Persistence, auth, and content live elsewhere — decide those separately.

Choosing whether to use it

Pick React when your interface has meaningful interactive state and you want a component model that a large ecosystem supports. Skip it for mostly static pages where plain HTML and a little JavaScript are simpler, or when a server-rendered framework alone already covers your needs. If you are already on Next.js, you are already using React — the remaining decision is where your content lives, not whether to adopt the library.

What "bootstrap" means on the Glaze website

On the Glaze site (glaze.cs.uchicago.edu), "bootstrap" is not a feature of Glaze and not something you download to use it. It appears as a site keyword tag, and the most likely referent is Bootstrap, the open-source CSS/JavaScript front-end framework used to build responsive web pages. If you arrived looking for Glaze — the tool that helps protect artists' work from generative AI — the keyword is a false lead, and you should go to the Download Glaze and User's Guide pages instead.

Why the tag is there

The Glaze site is a content and download hub: it hosts the FAQ, the "What is Glaze & How Does It Work?" explainer, the About Us page, the download page, and the user's guide. Sites like this are often built with a front-end framework, and Bootstrap is one of the most common choices. When a site's metadata lists "bootstrap" and "bootstrap5," it usually describes the underlying web stack, not a user-facing capability.

That distinction matters because the two meanings lead to completely different actions:

If you meant…	What it is	Where to go
Bootstrap (web framework)	A CSS/JS toolkit for building responsive sites	Bootstrap's own documentation
"bootstrap" as a site tag on Glaze	Metadata about how the Glaze site was built	Nothing to install; ignore it
Glaze	A tool from the SAND Lab at the University of Chicago that helps artists protect work from generative AI	The site's Download Glaze page and User's Guide

If you actually want Glaze

The Glaze site's own navigation points to the pages that matter:

Download Glaze — the current release noted on the site is Glaze 2.2 for Windows, which the page says supports new NVidia 50xx GPUs.
User's Guide — setup and usage instructions.
What is Glaze & How Does It Work? — the conceptual explainer.
Q & A / Frequently Asked Questions — troubleshooting and common questions.
WebGlaze — a separate option listed in the site navigation.

The site also notes that Glaze 2.1 included bugfixes and changes to resist a new attack, and links to more information on that. Version numbers and hardware support change over time, so check the download page for the current state rather than relying on any single snapshot.

How to tell which one you need

Ask what problem you're solving:

"I'm building or styling a website" → you want the Bootstrap framework, and the Glaze site is irrelevant to you.
"I want to protect my artwork from being used to train generative AI" → you want Glaze, and the "bootstrap" keyword is noise.
"I saw 'bootstrap' in this site's metadata and wondered if Glaze requires it" → it doesn't; it's a build detail of the website itself.

One caveat: the term "bootstrap" has other meanings in computing (for example, bootstrapping a system or a compiler), so if you encountered it somewhere other than this site's tags, confirm the context before assuming the CSS framework.

Website Overview

An advisory match combined with missing browser safeguards may increase exposure if the affected component is active. Deployment-specific verification and remediation deserve priority. Identifiable technologies and additional version or configuration signals make the service easier to fingerprint, which may help targeted scanners narrow their checks.

Domain and Registration

The registrar is NameCheap, Inc (https://www.namecheap.com), a widely used domain service provider. The domain uses the common .gg extension, which is not an independent safety signal.

DNS and Email

Nameservers are provided by NS1, indicating managed DNS hosting. No CNAME was found; the observed records resolve directly to addresses. No MX record was found. A conventional explicit inbound-mail route is not configured. The lowest observed DNS TTL is 120 seconds. No CAA record was found; there is no additional DNS-based restriction on certificate issuers.

TLS and Certificates

The public key uses EC with 256 bits. The server supplied a complete certificate chain. No organization name is present in the certificate; the available fields are consistent with domain validation. The certificate was issued by Let's Encrypt, commonly associated with automated certificate services. The certificate's total validity is about 89 days, consistent with a short renewal cycle.

HTTP and Browser Security

The response lacks these common security headers: CSP, Permissions-Policy. No X-Powered-By header was found, reducing one common source of backend fingerprinting information. No obvious internal addresses or debug information were found in the headers. The Server header contains the custom value Netlify. No explicit CDN or WAF marker was found in the response headers.

Technology Stack Analysis

The public page identifies Gatsby 2.3.34, Netlify, with exact versions exposed for 1 technologies. These details can narrow vulnerability checks, although exposure alone is not a vulnerability. The advisory source OSV places Gatsby 2.3.34 in the affected range of GHSA-c6f8-8r25-c4gc. Verify the deployed version and relevant configuration before drawing conclusions about exploitability. Updating affected components should be a priority.

Search and Social Sharing

The Generator tag identifies Gatsby 2.3.34, making the publishing system easier to fingerprint. No homepage canonical URL was detected. If duplicate URLs exist, consolidation may be less explicit. Open Graph is partially configured; og:image is missing. Twitter Card metadata is configured. The title has 14 characters, within a common display range.

Hosting and Email

DNSNS1

HostingNetlify

EmailUnknown

Approximate IP geolocation (inferred; a CDN or proxy may differ from the origin server) Ashburn, Virginia, United States Inferred 18.208.88.157

Open approximate map on OpenStreetMap

Registration details

RDAP / WHOIS

Registrar	NameCheap, Inc (https://www.namecheap.com)
Registered	Unknown
Expires	Unknown
Domain status	Active
Nameservers	Unknown
DNSSEC	unknown

DNS records

DNS

Type	Name	Value	TTL	Priority
A	www.puyo.gg	18.208.88.157	120	—
A	www.puyo.gg	98.84.224.111	120	—
AAAA	www.puyo.gg	2600:1f18:16e:df01::258	311	—
AAAA	www.puyo.gg	2600:1f18:16e:df01::259	311	—
NS	puyo.gg	dns1.p01.nsone.net	3600	—
NS	puyo.gg	dns2.p01.nsone.net	3600	—
NS	puyo.gg	dns3.p01.nsone.net	3600	—
NS	puyo.gg	dns4.p01.nsone.net	3600	—

TLS and certificates

TLS / SSL

Assessment	Normal configuration
Supported protocols	TLSv1.2、TLSv1.3
Negotiated protocol	TLSv1.3
Certificate subject	*.puyo.gg
Issuer	Let's Encrypt
Valid until	2026-11-26T23:49 · Remaining when checked: 36 days
Verification details	Certificate trust: Passed · Hostname match: Passed

HTTP response headers

HTTP

Header	Value
content-type	text/html; charset=UTF-8
cache-control	public,max-age=0,must-revalidate
server	Netlify
strict-transport-security	max-age=31536000
x-frame-options	DENY
x-content-type-options	nosniff
referrer-policy	same-origin

Identified technologies

Gatsby 2.3.34Netlify

Pages, Search and Sharing

Meta description	A new site for competitive Puyo Puyo.
Canonical URL	Not detected
Language	English (default)
Twitter Card	summary_large_image

Social Sharing Preview

6 fields

Sharing metadata

og:type	website
og:title	Home
og:description	A new site for competitive Puyo Puyo.
twitter:card	summary_large_image
twitter:title	Home
twitter:description	A new site for competitive Puyo Puyo.

robots.txt (opens in a new tab)

HTTP 404

No robots.txt found

Sitemaps

No sitemaps found

Recent Updates

Website images2026-10-21 18:59

User reviews (0)

No reviews yet.