Артём Букатин

I want a weird mod that lets you eat every mob by using a spoon (new item) spoon can be crafted

Kodari AI
KodariOct 26 at 5:16 pm 1

Should I create a new Fabric mod project for this, or is it for an existing project you can add to this workspace?

Артём Букатин

Yeah, new fabric mod project

Kodari AI
KodariOct 26 at 5:16 pm 1
Created Mob-Eating Spoon ModFabric Mods 26.3
Delegated to Mob-Eating Spoon Mod Running
Build a Fabric Minecraft 26.3 mod feature: add a new craftable Spoon item that lets the player eat any mob. Implement a sensible vanilla-style mechanic: when the player uses the spoon on a living mob, consume/remove that mob (do not allow using it on players), and give the player hunger/saturation as an edible action. Make the spoon obtainable via a clear crafting recipe using common ingredients. Register the item, recipe, and any required assets/data using this project's existing conventions. Ensure interaction is server-authoritative and avoid consuming mobs if the player is in a state where the action should fail (e.g. not hungry, if you implement hunger gating). Keep this focused on the requested feature; do not add tests. Report what files and mechanics you implemented.

I’ve started a new Fabric 26.3 mod project. It will add a craftable spoon that consumes mobs and restores hunger.

Артём Букатин

Also some features that I want:

When you "consume" an entity by the spoon you actually eat it piece by piece, like,limbs, body and the head can be eaten sepately You should add crunchy sound when you eat a part of the mob with some particles You can eat playes as well

Kodari AI
KodariOct 26 at 5:19 pm 1

Got it: the spoon should consume mobs and players one part at a time—limbs, body, then head—with crunchy sounds and particles for each bite. The first implementation is already running, so I’ll add these requirements in a follow-up once it finishes.

Report from 1 project
TaskBuild a Fabric Minecraft 26.3 mod feature: add a new craftable Spoon item that lets the player eat any mob. Implement a sensible vanilla-style mechanic: when the player uses the spoon on a living mob,...

Plan:

  1. Set up the minimal Fabric 26.3 project and register a survival-obtainable Spoon.

  2. Wire a server-side mob-use interaction with hunger gating; exclude players and preserve the mob on failure.

  3. Add the Spoon’s recipe, item assets, and English name.Implemented the Fabric 26.3 Mob Spoon project.

  • Mob interaction: Use the Spoon on a living entity other than a player to remove it and restore 6 hunger points with 0.6 saturation. The action fails if the player does not need food; mob removal and food restoration happen only on the server.

  • Survival recipe: Craft a Spoon with 1 iron ingot and 2 sticks. It is also listed in the Ingredients creative tab.

  • Project and assets: Added the Fabric project setup, item registration, recipe, English name, client item definition, handheld model, and generated Spoon texture.

Key files include src/main/java/com/example/mobspoon/MobSpoonMod.java, src/main/resources/data/mobspoon/recipe/spoon.json, and the Spoon assets under src/main/resources/assets/mobspoon/.

Kodari AI
KodariOct 26 at 5:25 pm 1
Delegated to MobEaterSpoon Running
Modify the existing MobEaterSpoon Fabric 26.3 mod to replace the current one-click mob removal with staged, piece-by-piece consumption and include other players as possible targets. Read the current MobSpoonMod.java and existing project conventions first. Existing behavior: right-click a LivingEntity using SPOON, hunger-gated, eats 6 food / 0.6 saturation once and discards non-player target. Preserve spoon registration, recipe, item assets, creative-tab listing, and server-authoritative operation. Required gameplay: - Spoon can be used repeatedly on the same living target. Represent six logical bites in order: four limb bites (one per limb), then body/torso, then head. Each successful use removes exactly one logical part; the target remains alive until the last bite. A final bite consumes the target. Since arbitrary vanilla mob/player models don't expose detachable parts, make the part progression clear to the player (actionbar/status text such as “Left arm”, “Right arm”, “Left leg”, “Right leg”, “Body”, “Head”); do not pretend to physically edit each model part. Use an appropriate bite amount of hunger/saturation per part, awarded only on the server, and only advance bite state when the action succeeds. Keep the existing hunger check so a hungry player can continue, but prevent bites when the eater is full. - Play a crunchy/eating sound and emit bite particles at the target for each successful bite, server-side so nearby players see/hear it. Use appropriate existing vanilla sounds/particles, not new dependencies/assets. - Other player entities must be valid targets, unlike current code. Never allow eating oneself. Do not bypass vanilla server PvP protections: only allow targeting another player when the server permits harm to that player, and reject creative/spectator/invulnerable targets where appropriate. Apply normal player death handling for the final bite (do not call discard on players); mob targets may be removed on final bite. Make sure target player can be bitten progressively and killed only at the final bite. - Keep all consumption/progress mutation on the server and handle client callback return values correctly to avoid duplicate bites. Make progress keyed safely per target and clean it up when target is consumed/removed or server stops; avoid indefinite stale state. If entity identity/progress persistence is needed, choose the simplest robust approach compatible with Minecraft 26.3. Keep implementation focused, preserve crafting/assets, and do not add tests. Report files changed and the exact bite order/food/sound/particle/player-protection behavior.

I’ve started a follow-up to add six staged bites—four limbs, body, then head—with crunchy sounds and particles. Other players will be targetable where the server permits PvP; self-targeting and protected players will be excluded.

Артём Букатин

having troubles finishing?

Kodari AI
KodariOct 26 at 5:35 pm 1

It’s still running, not reported as failed. The follow-up involves staged bites and PvP protections, so it’s more involved than the original feature. I’ll share the result when it finishes.

Report from 1 project
MobEaterSpoonCompleted
TaskModify the existing MobEaterSpoon Fabric 26.3 mod to replace the current one-click mob removal with staged, piece-by-piece consumption and include other players as possible targets. Read the current M...
  1. Read the current mod entrypoint and existing project conventions.

  2. Check the 26.3 APIs needed for interactions, player-protection checks, sounds, particles, and cleanup.

  3. Replace one-click removal with server-side six-bite progress while preserving existing registration, recipe, and assets.Updated the staged-consumption behavior in MobSpoonMod.java and added bite labels to assets/mobspoon/lang/en_us.json. The existing Spoon registration, recipe, assets, and creative-tab listing remain unchanged.

  • Bite order: Left arm → Right arm → Left leg → Right leg → Body → Head. Each successful use shows the current bite in the actionbar; models are not physically altered.

  • Food and feedback: Each bite restores 1 food with a 0.6 saturation modifier. Successful bites play GENERIC_EAT and emit CRIT particles for nearby players.

  • Target protection: Players cannot eat themselves. Other players can be bitten only when canHarmPlayer allows it; creative, spectator, and invulnerable targets are rejected. A player is killed on the final bite through normal player-attack damage handling, not discarded. Mobs are discarded on the final bite.

  • Authority and progress: Client callbacks only acknowledge the interaction; progress, damage, food, messages, sound, and particles are handled server-side. Bites are hunger-gated, and progress is cleared when a target unloads or is consumed and when the server stops.

Kodari AI
KodariOct 26 at 5:37 pm 1
Compiled MobEaterSpoonSucceeded

The staged-bite update is finished, and MobEaterSpoon compiles successfully.

Use the spoon six times on a target to eat, in order: left arm, right arm, left leg, right leg, body, head. Each bite restores 1 food, shows the part name, and plays an eating sound with particles. Other players can be targets only when PvP rules allow it; you can’t eat yourself or protected players. The target is consumed on the final bite.

Артём Букатин

Alright, we need to make some additions Eating mobs and players should damage them You eat the limb you are looking at When player or mob are lackin legs they cannot move When player or mob are lackin arms they cannot grab staff, interact with anything and damage When you eat player's head the player turns completely blind

Kodari AI
KodariOct 26 at 5:46 pm 1
Delegated to MobEaterSpoon Running
Extend the existing MobEaterSpoon Fabric 26.3 mod with the user's requested effects. Read current MobSpoonMod.java and project conventions first. Existing implementation registers a craftable Spoon and uses UseEntityCallback, a WeakHashMap<LivingEntity,Integer> for linear six bites, hunger gating, server-side food/sound/particles, PvP checks, and kills target on the final bite. Preserve spoon registration, recipe/assets, hunger gate, PvP/self/invulnerability protection, server authority, sound/particles, and client callback behavior while implementing the changes below. Do not add tests. Required behavior: 1. Every successful bite must damage the target (mob or player), not just the final bite. Use server-side normal damage handling. Don't advance the eaten-part state, feed the eater, or emit successful-bite feedback when damage is rejected. Keep the target alive until all six parts have been eaten; the final Head bite should consume/kill it. For player targets use normal player damage handling and preserve canHarmPlayer PvP restrictions; do not discard players. Take care that damage at intermediate bites cannot kill the target early; choose/implement a suitable bounded damage approach or stop/handle safely if the target dies from damage. 2. Select the part per hit: the player eats the limb/body/head region they are actually aiming at, rather than automatically progressing a fixed order. Minecraft exposes an entity hitbox, not detachable model limb hitboxes; derive a clearly sensible virtual part from the entity hit position (and target orientation for left/right), document this limitation with concise user-facing/actionbar feedback if needed. Allow parts to be eaten separately; don't repeatedly eat an already missing part. Map entity hit position to head/body/left-right arms/legs consistently for supported biped-like targets. For non-biped/short mobs where physical part mapping is not meaningful, use sensible hit-height zones and allow the six logical parts with a clear fallback. Reject an already-eaten region without consuming food or changing state. 3. Missing legs prevent player/mob movement. Missing arms prevent a player from picking up/grabbing items, using items, interacting with blocks/entities, and dealing attack damage; for mobs, disable movement/attack capability as sensibly as vanilla/API permits. Eating a player's Head applies complete blindness. Ensure effects continue to be enforced server-side while the target remains alive, and don't erase other existing protections. 4. State per target should track the six independently eaten parts and be removed when target is consumed/unloaded and when server stops (or use a more durable entity-attached approach if straightforward). Avoid unsafe shared mutation, stale references, or client-authoritative effects. Handle players and mobs as targets. Inspect Fabric 26.3 APIs actually present in this project/dependencies before choosing callbacks. Use existing vanilla effects/events where appropriate. If a universal guarantee for a requested consequence is impossible due to Minecraft's single entity hitbox or mob AI differences, implement the strongest practical server-side approximation and report the exact limitation. Modify only focused implementation/localization files. Report files changed and describe hit mapping, damage amount/behavior, movement/arm/head consequences, and any limitation. Do not ask for build/tests; I will compile after your changes.

I’ve started the additions. The update will select the bitten part from where you aim, damage the target with each successful bite, and apply movement, arm-use, and blindness effects as parts are eaten.

Report from 1 project
MobEaterSpoonCompleted
TaskExtend the existing MobEaterSpoon Fabric 26.3 mod with the user's requested effects. Read current MobSpoonMod.java and project conventions first. Existing implementation registers a craftable Spoon an...

…Modified the staged-eating implementation while preserving the Spoon registration, crafting recipe, item assets, and creative-tab listing.

  • Hit-selected bites: Aiming at the upper hitbox selects the Head; low left/right hit zones select the legs; mid-height side zones select the arms; the center selects the Body. Left/right follows the target’s facing. Each region can be eaten only once. Actionbar messages identify virtual hit zones and explain that models do not physically change; smaller or non-biped mobs use height/side zones.

  • Damage and consumption: Each bite must cause health or absorption damage before progress, food, or bite feedback is granted. Intermediate bites deal at most half the target’s current health, keeping it alive through the staged bites. The bite that completes all six regions consumes a mob; for a player, it uses a lethal playerAttack damage hit and normal death handling, never discard. A player who survives that final hit—for example, through a totem—does not have the final region recorded or receive bite rewards.

  • Consequences of missing parts: Both legs eaten prevents horizontal movement. Both arms eaten blocks player item pickup, item use, block/entity interaction, and attacks; it also suppresses standard mob target-driven melee and ranged attacks. Eating a player’s Head applies persistent vanilla blindness while they remain alive.

  • Protections and state: Self-targeting, full hunger, invulnerability, creative/spectator player targets, and PvP restrictions remain enforced. Bite state uses target UUIDs and is changed only server-side; it is cleared when a target unloads, is consumed, or the server stops. Crunch sound and bite particles remain server-side.

Changed MobSpoonMod.java, the five mixin implementation files, mobspoon.mixins.json, fabric.mod.json, and assets/mobspoon/lang/en_us.json. Custom mob AI and teleport/scripted movement may bypass the standard mob attack and movement hooks; arbitrary mob models still have no detachable limb hitboxes.

Kodari AI
KodariOct 26 at 6:13 pm 1
Compiled MobEaterSpoonSucceeded

The additions are implemented, and MobEaterSpoon compiles successfully.

Each successful bite damages the target and only then records that hit zone, feeds the eater, and plays the bite effects. Aiming selects a virtual head, body, arm, or leg zone; each can be eaten once. Both legs eaten prevents horizontal movement, both arms eaten blocks player item use/interactions/attacks, and eating a player’s head applies blindness.

The limb zones are approximations based on the entity hitbox—models do not physically lose limbs. Custom mob AI or scripted movement may also bypass the movement and attack restrictions.

Артём Букатин

The model should change

Kodari AI
KodariOct 26 at 6:17 pm 1
Delegated to MobEaterSpoon Running
Add a visible model/appearance change to the existing MobEaterSpoon Fabric 26.3 mod so eaten parts are visibly absent, building on the current EATEN_PARTS bitmask in MobSpoonMod.java (bits: left arm 0, right arm 1, left leg 2, right leg 3, body 4, head 5). Read existing source and inspect actual Minecraft/Fabric 26.3 mappings/APIs and project setup before implementation. Preserve current bite selection, damage, survival consequences, recipe, spoon assets, PvP protections, and server-authoritative progress. Do not add tests. Requirements: - Visually hide the corresponding model parts for client-rendered entities after each bite, at least for player models and vanilla humanoid/biped mob models (such as zombies/skeletons); use actual render/model changes, not only particles, actionbar text, or status effects. Map the left/right labels consistently with current hit selection. For body/head bites, hide torso/head respectively. Hide missing parts on both the bitten player's/mob's client representation and for viewers on multiplayer clients. - Ensure appearance state is synchronized from server to clients and is available to rendering. The current EATEN_PARTS map is server-only, so do not rely on that map in client rendering. Use a robust Minecraft/Fabric 26.3-compatible entity synced-data or equivalent approach; initialize and update it safely, include correct initial tracking for newly viewing clients, and avoid client-only mutation. Do not assume older APIs: inspect the project's dependencies/mappings and current mixin style. - Implement client-side renderer/model integration in the proper client source set / client entrypoint as needed, and register its mixins safely. Avoid modifying unrelated project behavior. - Since arbitrary mob model hierarchies are not standardized, provide a visible and sensible fallback for unsupported non-biped mobs if universal part removal is not technically feasible (e.g. visibly hide head/body where identifiable or add an obvious localized visual wound/absence indicator). Report exactly which vanilla model types change and the fallback/limitations; do not claim universal limb removal if it is not achieved. - Ensure client-side rendering code does not load on dedicated servers. Keep code focused. Do not build or write tests; I will compile the project.

I’ve started an update to make eaten parts visibly disappear from rendered models, with synchronized appearance state so other players can see the changes too. Arbitrary mob models may need a visual fallback where their parts can’t be reliably identified.

Артём Букатин

And then we need to make a major change We need to remove the spoon completely and change the mechanic of eating a little bit So, when your hunger is very love (Like from 2 to 0) You'll get an effect called "Starving" Screen starts shaking and you'll start to get damage until you eat BUT when you're starving you now can eat mobs and players just like we did before with spoon So, if you're "starving" just right click the mob or the player with a bare hand to take a bite from them And when you already ate a piece of a mob or a player you cannot stop It would've been fun to add a new achivement "cannibal" for eating a player Also add a funny feature that if you eat a piece of a creeper, if you get on fire you'd actually explode just like a creeper

Kodari AI
KodariOct 26 at 6:28 pm 1
Delegation to MobEaterSpoon cancelled
Delegated to MobEaterSpoon Running
Major redesign of existing MobEaterSpoon Fabric 26.3 mod in project KDR-202610-RN9F9IZZ. Read all current source/resources first, including MobSpoonMod.java, current mixins, fabric.mod.json/build.gradle, assets/lang, and any partial files left by the canceled model-rendering task. Inspect actual Minecraft/Fabric 26.3 APIs/dependencies/mappings before implementing. Preserve the mod namespace unless necessary, but remove the Spoon feature completely. Do not add tests or build. REMOVE SPOON ENTIRELY: - Delete item registration/constant, creative-tab listing, spoon recipe, model/item definitions and texture/resources, and all code/localization that refers to using a spoon. Ensure no Spoon item remains obtainable/registered; user will use a bare hand. - Preserve only relevant previous eating mechanics (part state/selection, damage, eating feedback, PvP/self protections, missing-part consequences) and adapt them to the new trigger. NEW STARVING TRIGGER/STATUS: - A player becomes Starving when food level is 0, 1, or 2 (<=2). Implement a real visible status effect named “Starving” (registered safely for Fabric 26.3) which is automatically applied/refreshed while hunger <=2 and removed when food rises above 2. Keep the implementation server-authoritative and ensure the effect name/localization is present. - While Starving, inflict periodic hunger/starvation damage until food rises above 2; choose sensible vanilla-style frequency/amount and avoid applying damage on clients. - While Starving, add a subtle but clear client-side screen/camera shake, only for the affected player. Client rendering code must not load on a dedicated server; use a client initializer and safe client-only mixins/hooks as needed. Preserve the current mod’s dedicated-server safety. BARE-HAND BITING AND COMMITMENT: - While Starving, a player may right-click a LivingEntity with an empty hand to take a bite. Include other players as targets but never self; keep canHarmPlayer/PvP rules, creative/spectator/invulnerable-target protections. Ignore offhand item interactions unless that hand is empty. Keep bite operation and state mutations server-side; client callbacks should acknowledge without duplicating actions. - Preserve the existing virtual six-part selection from hit position (left arm, right arm, left leg, right leg, body, head) and reject already-eaten parts. The first bite is the part the player looks at. Preserve sound and particles. Each successful bite damages the target using normal server damage handling, awards the existing sensible food amount, and advances part state only if damage actually succeeded. Keep targets alive until the final remaining part; final bite consumes mobs and uses normal lethal player damage/death handling without discarding players. Continue applying player-head blindness and arm/leg gameplay consequences where relevant. - “Once you have eaten a piece, you cannot stop” means a successful first bite commits the eater to that same target and the remaining missing parts must be eaten automatically, one bite per sensible interval (e.g. about one second), without requiring continued right-clicks and even if food rises above 2 during the sequence. Keep this committed sequence server-side; don't let unrelated targets interrupt it. Select the first bite by gaze; subsequent automatic bites choose the next uneaten logical part in stable order. Clear commitment safely if target dies/disappears/unloads, eater disconnects, server stops, or consumption completes. Respect PvP protections on each player-target bite; if permissions become invalid, safely abort/clear commitment. Avoid stale UUID state and concurrent unsafe map mutation. PLAYER ADVANCEMENT: - Add a vanilla-style advancement titled “Cannibal” for completing the eating of another player (grant only on the final successful player-consuming bite, not an intermediate bite). Prefer a data advancement with an appropriate vanilla kill criterion if it correctly detects the final playerAttack death; otherwise implement a robust Fabric-compatible custom trigger. Provide English title/description/icon, use current 26.3 datapack directory naming conventions, and ensure the trigger cannot award it for unrelated player kills if a custom trigger is needed. CREEPER CONSEQUENCE: - When the eater successfully bites any part of a Creeper, mark that eater with a persistent server-side creeper-curse/state. If that player later catches fire while the state is active, trigger a vanilla-style Creeper explosion at their location (sensible normal Creeper power/behavior), clear the state before exploding to prevent repeat explosions, and use safe server-side explosion APIs. Keep the curse until it triggers, with reasonable cleanup on disconnect/server stop; if practical use persistent player data so it survives relog/restart, otherwise report the limitation. Do not explode immediately merely for eating the Creeper. VISIBLE MODEL DAMAGE (prior user request remains active): - Eaten parts must visibly disappear on client renders for the bitten target and all tracking viewers, at minimum player models and vanilla humanoid/biped models (zombies/skeletons). Current EATEN_PARTS map is server-side, so provide a robust entity-synchronized state / equivalent with initial sync for new tracking clients. Implement actual player/biped renderer model-part hiding, not just particles/status/actionbar. Keep part labels consistent with current left/right selection. For unsupported non-biped mob models, implement/report the strongest practical visible fallback without claiming universal model support. Client rendering code must be isolated from dedicated servers. Preserve this appearance state through the forced automatic bite sequence. LOCALIZATION/INTEGRATION: - Update en_us localization for Starving, bite sequence/commitment messages and Cannibal advancement, and remove obsolete spoon strings. Update fabric.mod.json/mixin metadata as required by actual project conventions. Remove obsolete spoon data/assets and keep unrelated assets intact. - Keep all server-authoritative behavior, PvP restrictions and per-target state cleanup. Inspect actual 26.3 APIs and use valid sources/methods; do not assume older version APIs. Keep changes focused, report all changed/deleted files, exact damage/bite cadence, starving threshold/damage/shake, advancement trigger, creeper explosion behavior/persistence, model types supported and limitations.

I’ve started the redesign: the spoon is being removed, and starving players will bite with a bare hand. The work also includes forced completion after the first bite, the Starving effect and screen shake, the Cannibal advancement, the creeper-fire explosion, and visible missing parts.

Report from 1 project
MobEaterSpoonCancelled
TaskAdd a visible model/appearance change to the existing MobEaterSpoon Fabric 26.3 mod so eaten parts are visibly absent, building on the current EATEN_PARTS bitmask in MobSpoonMod.java (bits: left arm 0...
Kodari AI
KodariOct 26 at 6:31 pm 1

That report is for the canceled model-only update. The larger redesign is still in progress and includes visible model changes along with the new starving-and-biting mechanics.

Report from 1 project
MobEaterSpoonCompleted
TaskMajor redesign of existing MobEaterSpoon Fabric 26.3 mod in project KDR-202610-RN9F9IZZ. Read all current source/resources first, including MobSpoonMod.java, current mixins, fabric.mod.json/build.grad...

…Removed the Spoon feature and replaced it with starvation-triggered bare-hand bites. The mobspoon namespace is retained; no build or tests were run.

Behavior

  • Starving: Food level 2 or less applies the visible, localized Starving effect; it is removed once food rises above 2. At food 1–2, the mod deals 1 health point every 80 ticks, subject to vanilla starvation difficulty and health thresholds. At food 0, vanilla starvation damage remains in effect. The affected player’s camera gets a subtle sinusoidal shake (0.18° yaw, 0.12° pitch); other players’ cameras are unaffected.

  • Biting and commitment: An empty hand can start a bite while starving. The first part is selected from the hit position and target facing; subsequent parts are eaten automatically in stable bit order, one every 20 ticks, even if hunger rises above 2. The eater cannot switch targets during the sequence. PvP and target protections are rechecked on each automatic bite; invalid or unavailable targets end the commitment.

  • Damage and rewards: Intermediate bites use normal playerAttack damage, capped at 1 health point and reduced further when needed to leave the target alive. If no safe damage is possible, the bite stops. Progress, the existing 1 food / 0.6 saturation reward, and successful-bite feedback require both accepted damage and an actual health or absorption reduction. The final part uses a 1,000,000-point normal damage hit; mobs are not discarded, and player deaths use normal player damage handling. If a target survives the final hit, the committed sequence retries its lethal attempt every 20 ticks without awarding another bite’s food or feedback.

  • Consequences: Both missing legs prevent horizontal movement; both missing arms block player item use, pickup, block/entity interactions, and attacks, and suppress standard mob targeting/melee/ranged attacks. Eating a player’s head applies persistent blindness.

  • Creeper curse: A successful bite of a Creeper curses the eater. On catching fire, the curse is cleared before a power-3 MOB explosion is triggered at the player’s location. Curse state is server-memory-only: it is cleaned up on disconnect/server stop but does not survive relog or restart.

  • Cannibal advancement: The data advancement uses an impossible criterion awarded directly only after the final successful bite consumes another player, so unrelated player kills cannot grant it.

  • Visible damage: A server-to-client payload sends eaten-part masks to viewers, with initial state sent when tracking starts. Player models and vanilla renderers using HumanoidModel—including zombie and skeleton models—hide the matching head, torso, arm, or leg; player skin overlays are hidden too. Unsupported non-humanoid models instead show a recurring damage-indicator wound marker. Hit regions remain virtual zones derived from the entity hitbox, not physical limb hitboxes; arbitrary custom mob models have no standardized parts for universal removal.

Files

Updated MobSpoonMod.java, mixin/LivingEntityMixin.java, fabric.mod.json, and assets/mobspoon/lang/en_us.json.

Added StarvingEffect.java, network/EatenPartsPayload.java, the client entrypoint and render-state interface, five client mixins, mobspoon.client.mixins.json, data/mobspoon/advancement/cannibal.json, and the Starving effect icon at assets/mobspoon/textures/mob_effect/starving.png.

Deleted the Spoon recipe, client-item definition, item model, and item texture.

Kodari AI
KodariOct 26 at 7:02 pm 1
Compiled MobEaterSpoonSucceeded

The redesign is complete, and MobEaterSpoon compiles successfully. The Spoon and its recipe/assets are removed.

When a player’s hunger is 2 or less, they get the visible Starving effect and a subtle camera shake. While starving, they can start a bite on a mob or another player with an empty hand. After the first successful bite, they’re committed to that target: the remaining parts are eaten automatically, one every second, even if their hunger recovers. The mod preserves PvP and target protections.

Eaten parts now visibly disappear from player models and vanilla humanoid models such as zombies and skeletons. Unsupported mob models get a wound-marker fallback; arbitrary custom models can’t be reliably changed because Minecraft doesn’t provide standardized limb parts for them.

The update also adds the Cannibal advancement for completing a player-consumption sequence and a creeper curse that causes a power-3 explosion when the cursed player catches fire. The curse is not saved across disconnects or restarts.

Артём Букатин

There's a bug Every time I bite a player or a mob he begins to damage even if I don't really do anything.

Kodari AI
KodariOct 26 at 7:13 pm 1
Delegated to MobEaterSpoon Running
Fix the reported bug in MobEaterSpoon: when the player bites a mob or another player, the target appears to start attacking/damaging the eater even when the eater is not actively doing anything. Inspect the current MobSpoonMod.java and relevant Fabric/Minecraft 26.3 damage APIs/mixins. The code currently bites with target.hurtServer(..., eater.damageSources().playerAttack(eater), damage) in attemptBite and attemptFinalConsumption; successful first bite intentionally starts an automatic committed eating sequence with one bite every 20 ticks, and this requested auto-bite behavior must remain unchanged. Preserve actual bite damage, PvP/self/invulnerability checks, successful damage validation, progress/food/sound/particles, model appearance synchronization, and normal target death handling. Diagnose and fix the unintended target retaliation/aggro if caused by attacker attribution or bite damage, without preventing genuine damage to targets. Ensure eating another player remains possible only when canHarmPlayer permits it. Do not remove the intended automatic bite commitment. Keep changes focused, no tests/build. Report root cause and exact fix.

I’ve started investigating a likely cause: the bite damage is attributed to the eater, which can make mobs retaliate. I’ve asked the mod developer to prevent that unintended retaliation while preserving bite damage and the automatic eating sequence.

Report from 1 project
MobEaterSpoonCompleted
TaskFix the reported bug in MobEaterSpoon: when the player bites a mob or another player, the target appears to start attacking/damaging the eater even when the eater is not actively doing anything. Inspe...
  1. Trace the bite flow and any mixins affecting damage or target behavior.

  2. Verify 26.3 damage-source and retaliation APIs in the mounted source.

  3. Make the smallest fix that preserves bite damage and automatic eating, then report the cause and change.In MobSpoonMod.java, both bite paths used playerAttack(eater). That attributed each hit to the eater, letting vanilla damage handling record them as the target’s last attacker and trigger retaliation or aggro.

Changed both paths to use damageSources().generic(), which preserves normal damage and death handling without attributing the eater. The 20-tick committed auto-bite sequence, PvP/self/invulnerability checks, damage validation, progress, effects, and appearance synchronization remain unchanged. No build or tests run.

Kodari AI
KodariOct 26 at 7:17 pm 1
Compiled MobEaterSpoonSucceeded

Fixed and compiled successfully. Bite damage is no longer attributed to the eater, which was causing mobs to retaliate or aggro. Bites still deal damage, and the automatic one-bite-per-second sequence remains unchanged.

Артём Букатин

The problem is the same I take a bite of a player/mob and then the victim just loses their limbs and takin damage

Kodari AI
KodariOct 26 at 7:24 pm 1

The continued limb loss and damage are caused by the automatic bite sequence: after the first bite, the mod keeps biting that target once per second without another click. That behavior was added to match the earlier “you cannot stop” request.

Do you want me to change it so each bite requires a new right-click instead?

Артём Букатин

No, just remove this feature, one click and that's all Make it like that the starving effect won't be gone until you restore the hunger bar fully, for that you should change the amount of hunger you get from eating a player/mob

Kodari AI
KodariOct 26 at 7:27 pm 1
Delegated to MobEaterSpoon Running
Fix the current MobEaterSpoon behavior per the user's explicit correction. Read current MobSpoonMod.java, starvation client/effect code, and current localization first. Focus on this project's existing Minecraft/Fabric 26.3 APIs. Do not build or add tests; I will compile after your changes. Required changes: 1. REMOVE the automatic committed-biting feature completely. One right-click with bare hand may perform at most one bite. Do not continue biting/damaging/removing parts from a tick callback or after the click. Delete BITE_COMMITMENTS, BiteCommitment/processCommitment, timing constants, target-switch/resume/commitment messages and any related cleanup. A later separate right-click may take another uneaten part; keep existing per-target six-part tracking and hit-position selection, damage validation, visuals, missing-part consequences, PvP/self/invulnerability protections, and final consumption behavior. Ensure no hidden auto damage remains elsewhere. 2. Starving is initially triggered at food <= 2, but once applied it must remain until the food bar is FULL (food level 20), not disappear as soon as food rises above 2. Continue refreshing it server-side while food <20 and remove/reset starving state only at food level 20. Bare-hand bite eligibility must be based on the active Starving effect after it starts, so a player can continue deliberate clicks while food is recovering from 2 toward 20; don't use only food<=2. On clients, acknowledge the same cases without performing server mutations. Update client shake behavior only if it currently checks the old food threshold instead of the Starving effect. 3. Change hunger reward per successful bite from eat(1, 0.6F) to a sensible larger fixed amount, specifically 4 food points per bite with 0.6F saturation modifier, capped naturally by FoodData. Only reward after a successful bite as now. This lets several manual bites refill hunger to full; full hunger clears Starving. Maintain existing bite damage and sound/particle behavior. 4. Keep existing starving damage consistent until hunger is full (or explicitly state if you preserve a different intentional threshold); avoid double damage at zero hunger if vanilla already handles it. Keep the effect localized and the animation/client behavior safe on dedicated servers. Remove obsolete commitment strings from en_us.json, but preserve all unrelated localization and advancement/assets. Do not simplify the behavior by restoring the original <=2 bite gate after Starving begins. Report exact files changed and confirm every click now causes at most one bite, the effect removal threshold is 20 food, and the food reward is 4 points per bite.

I’ve started the fix: each right-click will cause at most one bite, and Starving will persist until your hunger is full. Each successful bite will restore 4 hunger points, allowing you to refill through deliberate clicks.

Kodari can make mistakes. Review important code before using.
Files

No files in this session

Code