Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Bug Report: HTTP 403 when downloading schematics

Open
#4 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
55/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Active
Tech stack
java
Domain
backend

Research direction

Start by locating SchematicDownloadHandler and reproduce the failure with code JP7XS or the linked schematic URL. Inspect the request sent to createmod.com, including its headers and URL format, and compare the response with the browser-accessible page. Done means the example schematic downloads successfully without the HTTP 403 error.

Written by the indexing model from the issue text.

Description

Bug Report: HTTP 403 when downloading schematics

Mod version: 2.2.0 (NeoForge, MC 1.21.1)

Issue: Every attempt to download a schematic via code/URL fails with:

[SchematicDownloadHandler]: Error downloading schematic: Error downloading schematic: HTTP 403

Tested with: code JP7XS / https://createmod.com/schematics/3-cylinder-diesel-engine — the schematic page loads fine in a browser and is public, so it's not a login/permissions issue on the website side.

Reproduction: Tried multiple times over several minutes (all failed identically with HTTP 403), so it doesn't look like a transient network issue on my end.

Suspicion: Possibly a bot/anti-scraping protection (e.g. Cloudflare) on createmod.com's side now rejecting the request the mod sends (missing/changed header, User-Agent, or API format mismatch).

Dominant language
Java
Stars
2
Forks
0
PR merge metrics
No merged PRs in 30d

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Similar issues

More Java issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.