Skip to content

auto_unequip_and_reequip_for_carry_drop_throw#511

Open
OvercastInteractive wants to merge 1 commit intomainfrom
auto_unequip_and_reequip_for_carry_drop_throw
Open

auto_unequip_and_reequip_for_carry_drop_throw#511
OvercastInteractive wants to merge 1 commit intomainfrom
auto_unequip_and_reequip_for_carry_drop_throw

Conversation

@OvercastInteractive
Copy link
Copy Markdown
Collaborator

  • Automatically unequips the current wieldable when attempting to carry an object
  • When leaving a carried object (drop, throw or leave) reequips the current wieldable
  • Creates a more seamless & effortless transition between wielding and carrying. Similar in functionality & behavior to Half-Life 2.

- Allows the player to seamlessly carry objects while equipping wieldables by unequipping the current wieldable automatically when attempting to carry
- Restores the last equipped wieldable when the carried object leaves the carried state (drop, thrown, left)
@Phazorknight
Copy link
Copy Markdown
Owner

Hey, thanks for this - actually had implementing somethign like this on my to-do list so I'm very happy to see this.
Would you mind putting this PR on the new 1.1.6-rc branch here? https://codeberg.org/Phazorknight/Cogito/src/branch/1.1.6-rc

@Phazorknight Phazorknight added the enhancement New feature or request label Jan 12, 2026
@OvercastInteractive
Copy link
Copy Markdown
Collaborator Author

OvercastInteractive commented Jan 13, 2026

Alright, I set up my codeberg account and will try to work on this branch soon for 1.1.6-rc.

I discovered a bug where spamming carry and drop/throw input can allow the player to carry an object while wielding, which likely has something to do with animation playback for unequip or equip and some of the await timeout calls we use in wieldable handling functions in PIC, so I'll aim to fix those before publishing the PR.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

enhancement New feature or request

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants