Here's a structured, helpful analysis of your situation, with suggestions:

Bias in Your Approach?

You've mentioned not being familiar with programming, yet attempted coding. While bold efforts to learn are commendable, this might not align with your natural nonprofit. Here's why:

  1. Misalignment with Expertise:
    • Your Goal: Game development, writing, and audio design.
    • Actual Skills:Video editing → Marketing potential for gaming content (streaming, animation designs, gameplay walkthroughs) rather than coding the game.
  2. Scattering of Efforts:
    • Trying to learn programming just a bit at a time, without "click" (commonly referred to when a skill finally becomes innate, like schedule smarts for ATeam members).
    • Comparing multiple programming/development attempts, which dilutes focus.
  3. Lack of (Non-)Technical Positioning in Outreach:
    • Asking for "developers" without specifying your role could generate more cold responses or scams.

Ethics of Assistance (INAT, Itch)

  • Honest Labeling: Do your labels or homepage make your expectations explicit? For example, if seeking collaborators, you shouldn’t uniformly label them as "developers." Clarify your role while being non-committal.

Strategies for Progress & Safety

  1. Use Your Non-Technical Expertise:
    • Market Overlap:
      • Integrate your video editing skills into gaming content streams (playthroughs, visual editorials)
      • Offer design services (mockup and animation for game/music assets)
    • Collaborative Gap Strategy:
      • Share what you're looking for (e.g., storyboard, marketing materials for gaming project)
      • Offer development tasks once the wheels turn (e.g.,腕の bast gameplay script sketch)
      • Viralize project regress for potential "gets" looking for non-dev collaborators.
  2. Break Down Your Request to Improve "Help Wanted" Feedback:
    • Direct vs. General Contact:
      • Split response flow: reach out to potential collaborators/group owners for specific project roles, and place more generic queries with other platforms.
      • Instead of "Help Wanted" on Itch, focus more on specific proposal e-mails (e.g., builders on GitHub for a chosen project aimee)
    • Clear Project Roles Criteria: Instead of asking broadly for all "developers", specify:
      • Link to sample project (even simple ones you did?)
      • Describe your contributions/expected roles (e.g., Animated GIP, Composer, Community Manager)
  3. Scam Avoidance:
    • Recognize Red Flags: Any response to your requests mentioning suspicious rates, ties to non-existent projects, or unreliable teams.
    • Public Reviews (for Itch, notably): Some teams offer 100% peer-reviewed projects. Helps validate other project quality. Consider rating projects as a way to signal reliability. Tutorial here

Portfolio Actionable Tip

  • Dynamic Portfolio: Instead of a static, generations-described set of cards, prioritize what excites you (e.g., the prototype, your recent translux designs, or the four set of behind-the-sceness that you got from a friendly offer that addressed some of your concerns. Translucence technically requires clear roles.)

Dynamic Alternative to "Help Wanted"

[inaguerrmale things: e.g.
How can I recruit freelancers *papers for the project?
Transparent role-based listing on your profile. (Add a list of clear project roles you can contribute to in the comments.)
Get emailing directly. (Put a link to contact in your channel description.)"]

Board of Directors for Development

  • Equitable Review:
    • Briefly call out the reviewers and their priorities for the project you’re offering
    • Ask reviewers what development aspects they couldn’t take (or breakdown projects into actionable items)

Potential Next Steps

  • Research similar projects for a market interest (e.g., indie game successes), keep an eye on YouTube Q&A portal
  • Ask for colleague opinions: You could attract people at instance asking around for professional thoughts or comparable Agencies (Sora Gaming Agency, for example)
  • Use specific marketing measurables to gauge if your visibility chunks off.

This should refocus your efforts, acknowledge your strengths, and enhance the likelihood of getting useful feedback. Let me know if you have any other ideas!