Replies: 6 comments 7 replies
-
PlanObservationsThe qcode addon in ApproachThe issue is requesting proper attribution for contributors to the qcode addon. Based on the manifest comment and description, three people contributed: supervoidcoder, NotTheBaton, and Centley Cell. The solution involves updating the credits array in the manifest to include all contributors who worked on the addon, following the same pattern used in other addons like Implementation Steps1. Update qcode Addon CreditsModify
2. Update Addon DescriptionIn the same manifest file:
3. Verify Addon RegistrationThe qcode addon is already registered in:
4. Documentation UpdateIf there's any documentation about contributors or the qcode addon:
Expected Credits Structure"credits": [
{
"name": "supervoidcoder"
},
{
"name": "NotTheBaton"
},
{
"name": "Centley Cell"
}
]This follows the same pattern as the debugger addon which lists multiple contributors, ensuring proper attribution for all who contributed to the qcode addon development. Import In IDE🤖 Prompt for AI Agents## Observations
The qcode addon in `file:src/addons/addons/qcode/_manifest_entry.js` is a placeholder addon with incomplete implementation. The manifest comment states "by supervoidcoder and NotTheBaton and NOT CENTLEY CELL" but only credits NotTheBaton. The description mentions "centley cell" and the addon files (`file:src/addons/addons/qcode/userscript.js` and `file:src/addons/addons/qcode/style.css`) are essentially empty placeholders. The issue title "guess who" with censored name refers to properly crediting "Centley Cell" for their contribution.
## Approach
The issue is requesting proper attribution for contributors to the qcode addon. Based on the manifest comment and description, three people contributed: supervoidcoder, NotTheBaton, and Centley Cell. The solution involves updating the credits array in the manifest to include all contributors who worked on the addon, following the same pattern used in other addons like `file:src/addons/addons/debugger/_manifest_entry.js` which lists multiple contributors.
## Implementation Steps
### 1. Update qcode Addon Credits
Modify `file:src/addons/addons/qcode/_manifest_entry.js`:
- Update the `credits` array to include all three contributors mentioned in the comment
- Add entries for "supervoidcoder", "NotTheBaton", and "Centley Cell" following the pattern from other addons
- Each credit entry should have a `name` field at minimum
- Optionally add `link` fields if Scratch profile URLs are available (following the pattern in debugger addon)
- Update the comment to reflect accurate attribution, removing the "NOT" prefix
### 2. Update Addon Description
In the same manifest file:
- Update the description from "aura farming addon + balkan rage + centley cell" to a proper description of the addon's actual purpose
- Ensure the description follows the pattern of other addons (clear, concise explanation of functionality)
### 3. Verify Addon Registration
The qcode addon is already registered in:
- `file:src/addons/addons.js` - the addon is listed in the addons array
- The addon is properly configured with userscripts and userstyles
### 4. Documentation Update
If there's any documentation about contributors or the qcode addon:
- Update any README or CONTRIBUTING files that might reference this addon
- Ensure the credits align across all documentation
## Expected Credits Structure
```javascript
"credits": [
{
"name": "supervoidcoder"
},
{
"name": "NotTheBaton"
},
{
"name": "Centley Cell"
}
]
```
This follows the same pattern as the debugger addon which lists multiple contributors, ensuring proper attribution for all who contributed to the qcode addon development.
💡 TipsSupported Commands (Inside Comments)
Supported Commands (Inside Description)
Community
|
Beta Was this translation helpful? Give feedback.
-
|
🤖 Issue Closed Hi @IM NOT TRAYCERAI! It looks like this issue isn't related to OmniBlocks, but rather links to an unrelated Scratch Discussion Forum topic. If this is a general question or discussion, feel free to move it over to the Discussions tab (https://github.com/orgs/OmniBlocks/discussions) where it's more appropriate. If there's something specific you'd like help with regarding OmniBlocks, feel free to clarify here! For now, I'll close this as it's not a valid issue. no - graison |
Beta Was this translation helpful? Give feedback.
-
|
@supervoidcoder @8to16 |
Beta Was this translation helpful? Give feedback.
-
|
I have updated the Implementation Plan to reflect the recent changes in the ticket.
|
Beta Was this translation helpful? Give feedback.
-
|
quack cwanker clanker |
Beta Was this translation helpful? Give feedback.
-
psst... |
Beta Was this translation helpful? Give feedback.

Uh oh!
There was an error while loading. Please reload this page.
-
it's me, BLEEP
https://scratch.mit.edu/discuss/topic/861974/
(this is semi important for qfb in a way because it's on there)
Beta Was this translation helpful? Give feedback.
All reactions