-
Notifications
You must be signed in to change notification settings - Fork 4.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Clothing items collide that shouldn't #36634
Comments
The examples you provided look like legitimate clothing layer conflicts to me:
In your screenshots, the messages indicate why the items are in conflict - wearing multiple items on the same layer, on the same body part, is adding the extra encumbrance. My understanding of the clothing layer system is that's how it's supposed to work. Have I misunderstood, or am I missing something? |
Yeah this is expected behavior for the current system. I want to improve the system so we've got better granularity in body part coverage and layers. Compression shorts are a bad example but we have some things that collide in the same layer that are normally worn together. The knee pads and ammo pouch shouldn't collide because theyre on different parts of the leg. I meant to handle this one before 0f but I got caught up with other things. |
Maybe we could add separate segments for thigh, knee, and calf? Same for the arms, and maybe the torso (abdomen, chest, neck, back) so that your scarf wouldn't be trying to occupy the same space as your mouthguard &etc. |
knee pads and a leg ammo pouch no longer collide
|
Can confirm. Looks like it is fixed. |
Describe the bug
Wearable items that shouldn't collide in clothing layers often do. This is most visible in SKINTIGHT and BELTED.
Steps To Reproduce
Steps to reproduce the behavior:
Expected behavior
Clothes that are normally worn over each other do not cause extra encumbrance penalties. Clothes that occupy the same layer but different areas do not cause extra encumbrance penalties.
Screenshots
Versions and configuration
The text was updated successfully, but these errors were encountered: