Player attacks added a constant 1.0 to the extra knockback strength, so
every hit pushed the victim on top of the base knockback applied by the
damage path. Vanilla only adds the Knockback enchantment bonus plus 0.5
for a sprint attack, and skips the push entirely when that total is zero.
Armor stands make the difference visible: their damage handling applies no
base knockback, so they should only move when the attacker sprints or
carries Knockback.
* compare BlockId instead of (str) name
* compare named BlockIds in Block::properties() and Block::from_properties()
* compare named BlockIds instead of u16 literals for `impl BlockProperties`
* try to add Android build github workflow
* fix: indent
* use cargo-ndk instead
* update android api version to 24
* try to apply them to exist workflows
* release the android executable
* correct the test workflow for android
* test it again
* im tired of trying;
* rollback to `cargo ndk-test`
---------
Co-authored-by: w9pi3cz1 <sdfghjk86@outlook.com>
The HTTP_OUTBOUND permission was wired up correctly in #2128, gating
whether a plugin's outbound HTTP requests are allowed via
wasi_http_hooks.allow_outbound. That block was accidentally dropped in
8ce513ff89 ("feat: more plugin features") when unrelated changes
overwrote the same permission-checking region in
wasm_host/mod.rs, leaving allow_outbound permanently false regardless
of the plugin's declared permissions.
This restores the check so a plugin granted http-outbound in its
manifest can actually make outbound HTTP calls again.
* chore(bedrock): Update most of the packets to mirror the official docs
more closely.
* Fix typo
* Fix CCreativeContent
* Undo unrelated `registry.rs` change
* Update WIT to merged PR
---------
Signed-off-by: Demetrius Kanios <demetrius@kanios.net>
* feat(bungeeguard): add BungeeGuard token authentication
Add a BungeeGuard shared secret to the proxy configuration, validate the token during the BungeeCord login flow, reject connections with invalid tokens, and prevent players from bypassing the proxy to connect directly.
* fix
* fix
* fix:ci
* feat(plugin-api): Better method chaining (Rust)
* Work around faulty force-link of `cabi_realloc`
* Stub for `pumpkin-plugin-api` as well
* Revert "Work around faulty force-link of `cabi_realloc`"
This reverts commit 4aa4d4370b.
Adds the vanilla /reload command (permission level 2), which reloads
the server's datapacks: it re-reads the enabled packs, re-runs the
#minecraft:load function tag and pushes the rebuilt recipes to every
player, through the same Server::reload_datapacks path /datapack
enable and /datapack disable already use.
Feedback follows Vanilla and is sent before the reload starts, so it
arrives even though reloading takes a moment.
Co-authored-by: Mcxiaocaibug <Mcxiaocaibug@users.noreply.github.com>
Implements the vanilla /debug start and /debug stop commands (tracked in #15):
- /debug start opens one server-wide tick profiling session and rejects duplicate starts.
- /debug stop reports elapsed seconds, processed ticks, and average TPS, then returns the floored average TPS.
- Profiling state handles tick counter wraparound and can be restarted after a completed session.
- Registers minecraft:command.debug at operator permission level 3 and uses the existing Java and Bedrock translation keys.
/debug function is intentionally out of scope because Pumpkin does not yet have the required function runtime.
