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

BounceBlocks auto trigger option

Open
#1,217 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
java
Domain
game-dev

Research direction

Start by locating the BounceBlocks and auto blocks implementations, then trace how slime_block entries are parsed and triggered when players walk into them. The feature is done when an auto-trigger option can be configured for a whole section and for exact blocks, with behavior clearly distinguishing automatic activation from requiring a jump.

Written by the indexing model from the issue text.

Description

status:pending type:feature-request version:five

Is your feature request related to a problem? Please describe.

Just to this when players walk into bounce blocks (automated) like slime block that is used as "jump pad" on spawn, then they have to jump on it, so they don't even know it's bounce block.

Describe the solution you'd like

Would be nice if you add way to set auto trigger option to whole section of bounce blocks and ALSO to exact blocks in auto blocks, so slime_block: "1,1,0, trigger" or something like this.
Describe alternatives you've considered

New mechanism called jump pads?

Dominant language
Java
Stars
320
Forks
165
PR merge metrics
No merged PRs in 30d

Getting set up

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.

More from EngineHub/CraftBook

All issues in EngineHub/CraftBook

Similar issues

More Java issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.