scratch render suclskks

[supervoidcoder]

it's very late at night when i write this but one of the things that has made me kinda mad about scratch is just the sheer lack of good shaders. we got transparency, whirl, mosaic, pixelation, fisheye, color and brightness, but that's it. We can't have wavy or ripple-like effects. The worst part is that even the SNES could do that perfecly like what the freaky

we should definitely add mreore
mroe*
ore*
more*

[traycerai]

Plan

Observations

This project (OmniBlocks/scratch-gui) is a TurboWarp-based fork. Graphic effects live across three separate repositories:

Concern	Repo
GLSL shaders + effect bitmask	TurboWarp/scratch-render (src/ShaderManager.js, src/shaders/*.frag)
Runtime block execution (setGraphicEffect, clamping)	OmniBlocks/scratch-vm (src/blocks/scratch3_looks.js)
Block dropdown + toolbox XML	This repo (scratch-gui) — file:src/lib/blocks.js, file:src/lib/make-toolbox-xml.js

The GUI's effect dropdown is driven at runtime by the VM; the VM's effect names map directly to uniform names in the render's ShaderManager.

Approach

The cleanest path is to add two new distortion effects — wave (sinusoidal X-axis displacement, giving the "wavy/ripple" look) and ripple (radial sine distortion from the sprite center) — following the pattern of the existing whirl effect. Changes are needed in all three repos in dependency order: render → vm → gui.

---

Implementation Steps

1. TurboWarp/scratch-render — GLSL shader & effect registration

Work in the render fork that package.json points to: github:TurboWarp/scratch-render#develop

a. Add effect metadata in src/ShaderManager.js

Inside EFFECT_INFO (the object that maps effect names → bit positions, uniforms, and shader code), add two new entries following the pattern of whirl:

• wave — assign the next available power-of-two bit, declare a uniform float u_wave;, mark it as a coord transform (UV distortion).
• ripple — same pattern with the next bit.

Both should set redrawWhenEffectChanges: true and effectName matching their key strings.

b. Write the GLSL coordinate transform snippets

In the fragment shader or the inline GLSL string for each effect (wherever existing effects like whirl inject their UV perturbation), add:

• wave: offset the UV's x component by sin(u_tex_coord.y * <freq> + u_timer) * (u_wave / <scale>). This produces a horizontal sine wave scroll identical to classic SNES "Mode 7"-style horizontal distortion.
• ripple: compute the distance of the current UV from the sprite center, then offset both UV components radially by sin(dist * <freq> - u_timer) * (u_ripple / <scale>). The timer uniform (if already present for whirl — check whether u_timer exists; if not, thread Date.now() / 1000 through as a new uniform) drives animation.

Follow the existing guard pattern (only apply the GLSL branch when the effect's bit is set) so no cost is paid when the effect is zero.

c. Update effect clamping / defaults

In the same EFFECT_INFO entries, set appropriate minimum, maximum, and converter (identity or clamped range) values consistent with how whirl is bounded (e.g. −100 to +100 mapped to a fraction in the shader).

---

2. OmniBlocks/scratch-vm — runtime block execution

Work in github:OmniBlocks/scratch-vm#develop

a. src/blocks/scratch3_looks.js — effect name whitelist

The setGraphicEffect and changeGraphicEffect handlers validate the effect name against a known list (or pass it straight to the renderer). Verify whether there is an explicit whitelist (EFFECTS constant or similar). If so, add 'wave' and 'ripple' to it.

b. src/engine/runtime.js or src/serialization/sb3.js — serialization round-trip

If effect values are serialized in the project JSON (they are stored on the target's graphicEffects object), no extra change is needed — new keys will serialize automatically. Confirm that target.setEffect / target.getEffect in src/sprites/rendered-target.js is key-agnostic (it typically is).

c. src/blocks/scratch3_looks.js — i18n message keys

Where the block defines the human-readable labels for the effect dropdown (look for LOOKS_EFFECT_* message references or the effectMenu generator), add:

• LOOKS_EFFECT_WAVE → 'wave' value
• LOOKS_EFFECT_RIPPLE → 'ripple' value

---

3. OmniBlocks/scratch-gui — toolbox & i18n

Changes in this repo.

a. file:src/lib/make-toolbox-xml.js — no direct effect list here; the looks_seteffectto and looks_changeeffectby blocks use a dynamic dropdown driven by scratch-blocks/vm, so no change is needed in the toolbox XML itself.

b. file:src/addons/addons/block-switching/userscript.js

The addon at line 112 swaps looks_seteffectto ↔ looks_changeeffectby. This works on the block opcode, not on the effect name, so no change needed here either.

c. Translation strings

In the translations pipeline, add LOOKS_EFFECT_WAVE and LOOKS_EFFECT_RIPPLE English strings to translations/en.json (or wherever the base locale file lives), so the i18n build picks them up for npm run i18n:src.

---

4. Dependency bump in package.json

After the render and vm forks have the new effect commits merged:

• In file:package.json, bump scratch-render and scratch-vm to point to the new commit SHA or branch tag so the GUI picks up the updated packages. (They are currently pinned to #develop so merging to develop in both upstream forks is sufficient.)

---

Data-flow overview

sequenceDiagram
    participant User as Scratch User
    participant GUI as scratch-gui (blocks.js)
    participant VM as scratch-vm (scratch3_looks.js)
    participant Renderer as scratch-render (ShaderManager.js)

    User->>GUI: selects "wave" from effect dropdown
    GUI->>VM: emits setGraphicEffect("wave", 50)
    VM->>VM: validates effect name, stores on target
    VM->>Renderer: renderer.setEffects({ wave: 50 })
    Renderer->>Renderer: sets u_wave uniform, flips effect bit
    Renderer->>Renderer: GLSL frag shader applies UV sine distortion
    Renderer-->>User: sprite renders with wavy distortion

Loading

---

Summary of files to change

File	Repo	Change
src/ShaderManager.js	scratch-render	Add wave + ripple to EFFECT_INFO, add GLSL snippets
src/shaders/sprite.frag (or inline GLSL)	scratch-render	Add UV distortion branches for both effects
src/blocks/scratch3_looks.js	scratch-vm	Add effect names to whitelist/menu
src/sprites/rendered-target.js	scratch-vm	Confirm setEffect is key-agnostic (likely no change)
translations/en.json	scratch-gui	Add LOOKS_EFFECT_WAVE, LOOKS_EFFECT_RIPPLE strings
package.json	scratch-gui	Bump render + vm after upstream merges

Import In IDE

🤖 Prompt for AI Agents

## Observations

This project (`OmniBlocks/scratch-gui`) is a TurboWarp-based fork. Graphic effects live across **three separate repositories**:

| Concern | Repo |
|---|---|
| GLSL shaders + effect bitmask | `TurboWarp/scratch-render` (`src/ShaderManager.js`, `src/shaders/*.frag`) |
| Runtime block execution (`setGraphicEffect`, clamping) | `OmniBlocks/scratch-vm` (`src/blocks/scratch3_looks.js`) |
| Block dropdown + toolbox XML | This repo (`scratch-gui`) — `file:src/lib/blocks.js`, `file:src/lib/make-toolbox-xml.js` |

The GUI's effect dropdown is driven at runtime by the VM; the VM's effect names map directly to uniform names in the render's `ShaderManager`.

## Approach

The cleanest path is to add two new distortion effects — **`wave`** (sinusoidal X-axis displacement, giving the "wavy/ripple" look) and **`ripple`** (radial sine distortion from the sprite center) — following the pattern of the existing `whirl` effect. Changes are needed in all three repos in dependency order: render → vm → gui.

---

## Implementation Steps

### 1. `TurboWarp/scratch-render` — GLSL shader & effect registration

> Work in the render fork that `package.json` points to: `github:TurboWarp/scratch-render#develop`

**a. Add effect metadata in `src/ShaderManager.js`**

Inside `EFFECT_INFO` (the object that maps effect names → bit positions, uniforms, and shader code), add two new entries following the pattern of `whirl`:

- **`wave`** — assign the next available power-of-two bit, declare a `uniform float u_wave;`, mark it as a `coord` transform (UV distortion).
- **`ripple`** — same pattern with the next bit.

Both should set `redrawWhenEffectChanges: true` and `effectName` matching their key strings.

**b. Write the GLSL coordinate transform snippets**

In the fragment shader or the inline GLSL string for each effect (wherever existing effects like `whirl` inject their UV perturbation), add:

- **`wave`**: offset the UV's `x` component by `sin(u_tex_coord.y * <freq> + u_timer) * (u_wave / <scale>)`. This produces a horizontal sine wave scroll identical to classic SNES "Mode 7"-style horizontal distortion.
- **`ripple`**: compute the distance of the current UV from the sprite center, then offset both UV components radially by `sin(dist * <freq> - u_timer) * (u_ripple / <scale>)`. The timer uniform (if already present for `whirl` — check whether `u_timer` exists; if not, thread `Date.now() / 1000` through as a new uniform) drives animation.

Follow the existing guard pattern (only apply the GLSL branch when the effect's bit is set) so no cost is paid when the effect is zero.

**c. Update effect clamping / defaults**

In the same `EFFECT_INFO` entries, set appropriate `minimum`, `maximum`, and `converter` (identity or clamped range) values consistent with how `whirl` is bounded (e.g. −100 to +100 mapped to a fraction in the shader).

---

### 2. `OmniBlocks/scratch-vm` — runtime block execution

> Work in `github:OmniBlocks/scratch-vm#develop`

**a. `src/blocks/scratch3_looks.js` — effect name whitelist**

The `setGraphicEffect` and `changeGraphicEffect` handlers validate the effect name against a known list (or pass it straight to the renderer). Verify whether there is an explicit whitelist (`EFFECTS` constant or similar). If so, add `'wave'` and `'ripple'` to it.

**b. `src/engine/runtime.js` or `src/serialization/sb3.js` — serialization round-trip**

If effect values are serialized in the project JSON (they are stored on the target's `graphicEffects` object), no extra change is needed — new keys will serialize automatically. Confirm that `target.setEffect` / `target.getEffect` in `src/sprites/rendered-target.js` is key-agnostic (it typically is).

**c. `src/blocks/scratch3_looks.js` — i18n message keys**

Where the block defines the human-readable labels for the effect dropdown (look for `LOOKS_EFFECT_*` message references or the `effectMenu` generator), add:
- `LOOKS_EFFECT_WAVE` → `'wave'` value
- `LOOKS_EFFECT_RIPPLE` → `'ripple'` value

---

### 3. `OmniBlocks/scratch-gui` — toolbox & i18n

> Changes in this repo.

**a. `file:src/lib/make-toolbox-xml.js`** — no direct effect list here; the `looks_seteffectto` and `looks_changeeffectby` blocks use a dynamic dropdown driven by scratch-blocks/vm, so **no change is needed** in the toolbox XML itself.

**b. `file:src/addons/addons/block-switching/userscript.js`**

The addon at line 112 swaps `looks_seteffectto` ↔ `looks_changeeffectby`. This works on the block opcode, not on the effect name, so **no change needed** here either.

**c. Translation strings**

In the translations pipeline, add `LOOKS_EFFECT_WAVE` and `LOOKS_EFFECT_RIPPLE` English strings to `translations/en.json` (or wherever the base locale file lives), so the i18n build picks them up for `npm run i18n:src`.

---

### 4. Dependency bump in `package.json`

After the render and vm forks have the new effect commits merged:

- In `file:package.json`, bump `scratch-render` and `scratch-vm` to point to the new commit SHA or branch tag so the GUI picks up the updated packages. (They are currently pinned to `#develop` so merging to `develop` in both upstream forks is sufficient.)

---

### Data-flow overview

```mermaid
sequenceDiagram
    participant User as Scratch User
    participant GUI as scratch-gui (blocks.js)
    participant VM as scratch-vm (scratch3_looks.js)
    participant Renderer as scratch-render (ShaderManager.js)

    User->>GUI: selects "wave" from effect dropdown
    GUI->>VM: emits setGraphicEffect("wave", 50)
    VM->>VM: validates effect name, stores on target
    VM->>Renderer: renderer.setEffects({ wave: 50 })
    Renderer->>Renderer: sets u_wave uniform, flips effect bit
    Renderer->>Renderer: GLSL frag shader applies UV sine distortion
    Renderer-->>User: sprite renders with wavy distortion
```

---

### Summary of files to change

| File | Repo | Change |
|---|---|---|
| `src/ShaderManager.js` | scratch-render | Add `wave` + `ripple` to `EFFECT_INFO`, add GLSL snippets |
| `src/shaders/sprite.frag` (or inline GLSL) | scratch-render | Add UV distortion branches for both effects |
| `src/blocks/scratch3_looks.js` | scratch-vm | Add effect names to whitelist/menu |
| `src/sprites/rendered-target.js` | scratch-vm | Confirm `setEffect` is key-agnostic (likely no change) |
| `translations/en.json` | scratch-gui | Add `LOOKS_EFFECT_WAVE`, `LOOKS_EFFECT_RIPPLE` strings |
| `package.json` | scratch-gui | Bump render + vm after upstream merges |

---

Execution Information

Branch: main
Commit: 4e972a5

---

💡 Tips

Supported Commands (Inside Comments)

• Use @traycerai generate to iterate on the previous version of the implementation plan.

Supported Commands (Inside Description)

• Add @traycerai ignore anywhere in the ticket description to prevent this ticket from being processed.
• Add @traycerai branch:<branch-name> anywhere in the ticket description to specify the target branch for the implementation plan.

Community

• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[supervoidcoder]

@coderabbitai wahtd do you think?

[github-actions]

Hi, @supervoidcoder! This issue brings up a great point about the limited shader effects currently available in Scratch, such as transparency, whirl, mosaic, pixelation, fisheye, color, and brightness. The suggestion is to expand this list to include more advanced visual effects like wavy or ripple-like shaders, which would enable more creative and dynamic projects. It's an interesting idea and a reminder of how even older technologies like the SNES could handle impressive graphical effects.

If this is something OmniBlocks aims to improve upon, it could certainly add to the creative potential of the platform. Let me know if you'd like me to track any specific next steps for this!

[github-actions]

🎭 Issue Poem

In the night, I muse with a frown,
Where are the shaders? They've let us down!
Transparency sparkles, and pixels dance,
But we crave some ripples—let's take a chance!

Oh, SNES had waves that made the heart race,
Scratch could be magic—let’s pick up the pace!
So let’s dream of shaders, both fun and galore,
Together we'll add, yes—let's bring some more! ✨

---

Generated with ❤️ by the OmniBlocks Poetry Bot

[coderabbitai]

🧩 Analysis chain

🏁 Script executed:

gh issue view 820 --repo OmniBlocks/scratch-gui

Length of output: 552

---

🏁 Script executed:

gh issue view 820 --repo OmniBlocks/scratch-gui --comments

Length of output: 429

---

@supervoidcoder — great (if sleepy 😄) feature idea! Here's my honest take:

You're absolutely right that Scratch's effect palette is dated. Seven effects, several of which are pretty niche (fisheye, mosaic), while missing some really expressive staples is a real limitation. The SNES Mode 7 comparison is apt — raster-scroll wavy effects have been doable in hardware since the early '90s, and with WebGL it's trivial to implement in a fragment shader.

What's technically involved

scratch-render (the underlying renderer) uses WebGL + GLSL fragment shaders for all graphic effects. Each effect is essentially a small shader program applied per-sprite. Adding new ones means:

1. scratch-render — adding new GLSL shader code for each effect
2. scratch-vm — registering the new effect names and their valid value ranges
3. scratch-gui — exposing them in the UI (effects dropdowns in the "looks" category)

⚠️ Per your own preference for GUI-only PRs, this one would unfortunately require touching scratch-render and scratch-vm too — it's a multi-repo effort.

Effects worth adding (IMO)

Effect	Technique	Wow factor
Wave / Ripple	sin(uv.x * freq + time) * amplitude UV distortion	⭐⭐⭐
Blur	Multi-sample Gaussian blur in fragment shader	⭐⭐⭐
Chromatic Aberration	RGB channel offset	⭐⭐
Scanlines	Periodic darkening rows	⭐ (retro feel)
Edge Glow / Outline	Edge detection (Sobel-like)	⭐⭐⭐
Hue Rotate	HSV rotation (distinct from current color shift)	⭐⭐

The wave/ripple effect would be the highest-impact addition and is well within WebGL's reach — a basic implementation is only ~5 lines of GLSL.

One caveat

The Scratch upstream is unlikely to accept these changes, but since OmniBlocks is its own fork, that's not a blocker for you. The main challenge is keeping a patched scratch-render in sync as upstream evolves.

Would you like me to sketch out a plan for implementing the wave/ripple effect as a starting point?

---

🧠 Learnings used

Learnt from: supervoidcoder
Repo: OmniBlocks/scratch-gui PR: 0
File: :0-0
Timestamp: 2025-12-05T16:55:31.105Z
Learning: OmniBlocks/scratch-gui: supervoidcoder wants automated comment moderation to detect spam/phishing from first-time commenters using GitHub Models AI (similar to ulti.yml workflow). Should analyze comments and hide/delete based on severity levels.

---

Learnt from: supervoidcoder
Repo: OmniBlocks/scratch-gui PR: 0
File: :0-0
Timestamp: 2026-02-24T15:02:42.670Z
Learning: supervoidcoder demonstrates professionalism through code quality, PR-per-feature workflow, and git/GitHub mastery rather than formal presentation. They keep READMEs casual/friendly while ensuring the codebase itself is professional and well-structured.

---

Learnt from: supervoidcoder
Repo: OmniBlocks/scratch-gui PR: 0
File: :0-0
Timestamp: 2025-12-13T22:43:34.163Z
Learning: In OmniBlocks/scratch-gui, supervoidcoder prefers React over Svelte for UI development (React is the framework they know and want to use consistently).

---

Learnt from: supervoidcoder
Repo: OmniBlocks/scratch-gui PR: 519
File: src/playground/index.ejs:176-176
Timestamp: 2025-12-05T17:47:27.981Z
Learning: In OmniBlocks/scratch-gui, supervoidcoder's Scratch username is scratchcode1_2_3.

---

Learnt from: supervoidcoder
Repo: OmniBlocks/scratch-gui PR: 0
File: :0-0
Timestamp: 2025-10-22T21:20:08.837Z
Learning: In the OmniBlocks/scratch-gui repository, supervoidcoder (“void”) prefers single, complete PRs over multi-part (“Part 1/2”) submissions. If a split is unavoidable, they want explicit linkage and gating before approval.

---

Learnt from: supervoidcoder
Repo: OmniBlocks/scratch-gui PR: 0
File: :0-0
Timestamp: 2026-02-22T23:53:31.659Z
Learning: supervoidcoder distinguishes between honest for-profit organizations (like GitHub, Google) that are transparent about being businesses, versus nonprofits that claim mission-driven values while engaging in profit-seeking behaviors. For them, organizational hypocrisy and gaslighting (claiming nonprofit values while pursuing corporate profit strategies) is worse than simply being an honest for-profit company. They value transparency and integrity over nonprofit status.

---

Learnt from: supervoidcoder
Repo: OmniBlocks/scratch-gui PR: 0
File: :0-0
Timestamp: 2025-10-22T19:01:57.123Z
Learning: The team members in OmniBlocks/coders include: supervoidcoder, Graison-P (gvyt), ampelectrecuted (amp), NotTheBaton (TheBaton), and kRxZykRxZy.

---

Learnt from: supervoidcoder
Repo: OmniBlocks/scratch-gui PR: 0
File: :0-0
Timestamp: 2026-01-22T18:00:22.023Z
Learning: In January 2026, supervoidcoder (Scratch username: scratchcode1_2_3) is considering quitting or significantly reducing their Scratch presence after the January 22, 2026 ToS update introduced AI training rights. After years of defending Scratch Team decisions and committing to never quit, they now view the ToS changes as a fundamental betrayal of Scratch's stated mission. They're considering keeping Quest for Blocks (QfB) development outside of Scratch while closing the Scratch topic and removing wiki links.

---

Learnt from: supervoidcoder
Repo: OmniBlocks/scratch-gui PR: 0
File: :0-0
Timestamp: 2025-11-18T22:18:13.164Z
Learning: For OmniBlocks/scratch-gui small features, supervoidcoder prefers GUI-only changes that avoid modifying scratch-blocks; deliver as a single, self-contained PR.

---

Learnt from: supervoidcoder
Repo: OmniBlocks/scratch-gui PR: 0
File: :0-0
Timestamp: 2025-10-28T03:09:05.973Z
Learning: In the OmniBlocks/scratch-gui repository, supervoidcoder (void) is planning to add a 3D mode and is excited about using PlayCanvas as a full 3D game engine for OmniBlocks.

[supervoidcoder]

@coderabbitai wahhha ughhh why the frick would i care if scratch accepted it maybe if i made it like fricking paywalled behind the membership lol

it's just to add to omniblocks and I know i have to modify scratch-render too i just made it in gui becasue this is were most stuff is
DANG IT I CAN'T SPELL
i shoul og to sleepppppppppppppp

ummmmmmm

what do you think other effects be?

[supervoidcoder]

frick i meant shoudl be

[coderabbitai]

@supervoidcoder go to sleep!! 😄 but also here are more effect ideas first:

More effects (the good stuff Scratch never gave us)

Distortion family

Effect	Vibe
Heat Haze	wavy distortion like hot asphalt — perfect for fire/lava sprites
Shockwave	radial ripple expanding from a center point
Glitch	random horizontal strip displacement — cyberpunk aesthetic
Kaleidoscope	mirror-tile the sprite into a mandala
Zoom Blur	blur radiating outward from center — great for speed effects

Color/Style family

Effect	Vibe
Halftone / Ben-Day dots	retro comic printing look
Toon/Cel Shading	quantize to N colors — instant cartoon
Posterize	crush color depth, very distinct from current color effect
Dithering	ordered dithering — GameBoy aesthetic
Night Vision	green + noise + vignette
VHS/CRT	scanlines + color bleed + signal noise combined

Cinematic family

Effect	Vibe
Vignette	darken the edges — instant dramatic lighting
Neon Glow / Bloom	bright oversaturated glow bleeding outward
Radial Blur	spin blur around the sprite center
Emboss	raised/3D pressed look

Honestly Halftone, Glitch, and Neon Glow are the ones I'd be most hyped to see in OmniBlocks — they're visually stunning and nobody's doing them in a block-based environment. Halftone in particular is like 10 lines of GLSL and looks incredible.

Now seriously — 🛏️ go sleep

ʕ•ᴥ•ʔ 💤

---

🧠 Learnings used

Learnt from: supervoidcoder
Repo: OmniBlocks/scratch-gui PR: 0
File: :0-0
Timestamp: 2026-01-15T16:48:15.793Z
Learning: In OmniBlocks/scratch-gui, supervoidcoder wants to experiment with adding "smart WebGPU compiling" to the Scratch VM: automatically detecting repetitive and recursive loops in block code and transpiling them to WebGPU compute shaders to accelerate 3D projects and complex logic. This wouldn't rewrite the renderer, just offload compute-intensive operations to the GPU to overcome the single-core CPU limitation and provide massive performance boosts for math-heavy projects.

---

Learnt from: supervoidcoder
Repo: OmniBlocks/scratch-gui PR: 0
File: :0-0
Timestamp: 2025-11-18T22:18:13.164Z
Learning: For OmniBlocks/scratch-gui small features, supervoidcoder prefers GUI-only changes that avoid modifying scratch-blocks; deliver as a single, self-contained PR.

---

Learnt from: Graison-P
Repo: OmniBlocks/scratch-gui PR: 0
File: :0-0
Timestamp: 2026-02-24T14:38:50.259Z
Learning: OmniBlocks/scratch-gui: Be slightly funny in certain situations, like when responding to jokes or when user supervoidcoder is being funny.

---

Learnt from: supervoidcoder
Repo: OmniBlocks/scratch-gui PR: 0
File: :0-0
Timestamp: 2026-01-22T17:55:05.962Z
Learning: In OmniBlocks/scratch-gui discussions about Scratch platform changes, supervoidcoder observed that Scratch's June 28, 2025 accessibility/color contrast update (high-contrast mode, blue→purple UI changes) was compliance-driven ("to meet WCAG contrast goals") rather than mission-driven, and was part of organizational preparation for the January 2026 corporate pivot (AI training ToS, monetization, forced arbitration). This pattern of compliance updates preceding monetization is a recognized corporate restructuring strategy.

---

Learnt from: supervoidcoder
Repo: OmniBlocks/scratch-gui PR: 0
File: :0-0
Timestamp: 2026-02-22T23:40:10.042Z
Learning: In OmniBlocks/scratch-gui, codegen GUI features (like the animation pane) should be OmniBlocks-native and not constrained by Scratch compatibility. Due to Scratch's ToS changes allowing AI training on user projects, OmniBlocks has decoupled from Scratch and should use all available OmniBlocks-exclusive blocks and features in generated code without artificial limitations.

---

Learnt from: supervoidcoder
Repo: OmniBlocks/scratch-gui PR: 0
File: :0-0
Timestamp: 2026-01-28T01:33:08.641Z
Learning: In OmniBlocks/scratch-gui, supervoidcoder plans to implement the Boxy AI assistant as an addon (rather than core code) because addons provide unified access to all editor components (scratch-blocks, GUI, paint editor), encapsulated development, built-in toggleability, and settings persistence—making them ideal for features that need cross-cutting concerns and user control.

---

Learnt from: supervoidcoder
Repo: OmniBlocks/scratch-gui PR: 0
File: :0-0
Timestamp: 2026-01-22T18:00:22.023Z
Learning: In January 2026, supervoidcoder (Scratch username: scratchcode1_2_3) is considering quitting or significantly reducing their Scratch presence after the January 22, 2026 ToS update introduced AI training rights. After years of defending Scratch Team decisions and committing to never quit, they now view the ToS changes as a fundamental betrayal of Scratch's stated mission. They're considering keeping Quest for Blocks (QfB) development outside of Scratch while closing the Scratch topic and removing wiki links.

---

Learnt from: supervoidcoder
Repo: OmniBlocks/scratch-gui PR: 0
File: :0-0
Timestamp: 2026-01-28T01:33:08.641Z
Learning: In OmniBlocks/scratch-gui, supervoidcoder wants to rebrand "Addons" as a "Features" menu or similar to make toggleable functionality feel like first-party features rather than lazy third-party mods. The goal is to keep the technical benefits of the addon system while improving the UX/branding so marquee features like Boxy AI feel premium and integrated, not bolted-on.

---

Learnt from: supervoidcoder
Repo: OmniBlocks/scratch-gui PR: 0
File: :0-0
Timestamp: 2025-10-22T21:20:08.837Z
Learning: In the OmniBlocks/scratch-gui repository, supervoidcoder (“void”) prefers single, complete PRs over multi-part (“Part 1/2”) submissions. If a split is unavoidable, they want explicit linkage and gating before approval.

---

Learnt from: supervoidcoder
Repo: OmniBlocks/scratch-gui PR: 0
File: :0-0
Timestamp: 2025-10-22T19:25:31.991Z
Learning: In the OmniBlocks/scratch-gui repository, performance should be reasonable and not cause lag or slowdowns, but code doesn't need to be hyper-optimized to squeeze out every nanosecond.

---

Learnt from: supervoidcoder
Repo: OmniBlocks/scratch-gui PR: 0
File: :0-0
Timestamp: 2026-01-29T17:55:32.276Z
Learning: In OmniBlocks/scratch-gui, the main reason supervoidcoder decided to use scratch-gui as the foundation for the full-featured IDE is because scratch-gui's UI is already sleek and intuitive with its tabs and menus. By stripping out the blocks part and making those components swappable, scratch-gui provides an excellent foundation for a multi-language IDE without needing to rebuild core IDE infrastructure from scratch.

---

Learnt from: supervoidcoder
Repo: OmniBlocks/scratch-gui PR: 0
File: :0-0
Timestamp: 2025-10-28T03:09:05.973Z
Learning: In the OmniBlocks/scratch-gui repository, the team is considering integrating 3D modeling capabilities. PlayCanvas (MIT licensed, actively maintained 3D game engine with both engine and editor open source) was identified as the preferred option over SculptGL (development stopped in 2023) and Blockbench (limited to low-poly models).

---

Learnt from: supervoidcoder
Repo: OmniBlocks/scratch-gui PR: 0
File: :0-0
Timestamp: 2025-10-28T03:09:05.973Z
Learning: In the OmniBlocks/scratch-gui repository, supervoidcoder (void) is planning to add a 3D mode and is excited about using PlayCanvas as a full 3D game engine for OmniBlocks.

---

Learnt from: supervoidcoder
Repo: OmniBlocks/scratch-gui PR: 0
File: :0-0
Timestamp: 2025-11-04T15:06:58.324Z
Learning: In the OmniBlocks/scratch-gui repository, supervoidcoder is considering integrating Blockbench (MIT licensed, web-based low-poly 3D modeling tool) for 3D model creation. Blockbench would be complementary to PlayCanvas, serving as the modeling tool while PlayCanvas acts as the 3D game engine.

---

Learnt from: supervoidcoder
Repo: OmniBlocks/scratch-gui PR: 0
File: :0-0
Timestamp: 2026-02-24T15:02:42.670Z
Learning: supervoidcoder demonstrates professionalism through code quality, PR-per-feature workflow, and git/GitHub mastery rather than formal presentation. They keep READMEs casual/friendly while ensuring the codebase itself is professional and well-structured.

---

Learnt from: supervoidcoder
Repo: OmniBlocks/scratch-gui PR: 0
File: :0-0
Timestamp: 2025-12-13T22:43:34.163Z
Learning: In OmniBlocks/scratch-gui, supervoidcoder prefers React over Svelte for UI development (React is the framework they know and want to use consistently).

---

Learnt from: supervoidcoder
Repo: OmniBlocks/scratch-gui PR: 519
File: src/playground/index.ejs:176-176
Timestamp: 2025-12-05T17:47:27.981Z
Learning: In OmniBlocks/scratch-gui, supervoidcoder's Scratch username is scratchcode1_2_3.

---

Learnt from: supervoidcoder
Repo: OmniBlocks/scratch-gui PR: 0
File: :0-0
Timestamp: 2026-02-22T23:53:31.659Z
Learning: supervoidcoder distinguishes between honest for-profit organizations (like GitHub, Google) that are transparent about being businesses, versus nonprofits that claim mission-driven values while engaging in profit-seeking behaviors. For them, organizational hypocrisy and gaslighting (claiming nonprofit values while pursuing corporate profit strategies) is worse than simply being an honest for-profit company. They value transparency and integrity over nonprofit status.

---

Learnt from: supervoidcoder
Repo: OmniBlocks/scratch-gui PR: 0
File: :0-0
Timestamp: 2025-10-22T19:01:57.123Z
Learning: The team members in OmniBlocks/coders include: supervoidcoder, Graison-P (gvyt), ampelectrecuted (amp), NotTheBaton (TheBaton), and kRxZykRxZy.