Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Spread: better handling for large objects and piles of objects #44508

Open
LyleSY opened this issue Sep 29, 2020 · 4 comments
Open

Spread: better handling for large objects and piles of objects #44508

LyleSY opened this issue Sep 29, 2020 · 4 comments
Labels
[C++] Changes (can be) made in C++. Previously named `Code` (P4 - Low) Low priority issues: things which are e.g exotic, minor and/or hard to encounter <Suggestion / Discussion> Talk it out before implementing

Comments

@LyleSY
Copy link
Contributor

LyleSY commented Sep 29, 2020

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

Currently bodies larger than 1000 L/kg are not handled well. If they're too large, they disappear entirely. If they're too heavy, when they are harvested all leather, bones, and meat disappears, leaving only scraps of meat and organ to stay under the 1000L tile cap.

Describe the solution you'd like

Large objects can exist, but cover adjacent tiles. High piles of objects spread out to adjacent tiles instead of disappearing.

Describe alternatives you've considered

For now, DinoMod is capping monsters at 1000L/1000kg as a hack

Additional context

Inspired by a bunch of hungry players
@LyleSY LyleSY mentioned this issue Sep 29, 2020
Merged
@stale
Copy link

stale bot commented Oct 30, 2020

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. Please do not 'bump' or comment on this issue unless you are actively working on it. Stale issues, and stale issues that are closed are still considered.

@stale stale bot added the stale Closed for lack of activity, but still valid. label Oct 30, 2020
@anothersimulacrum anothersimulacrum added the <Suggestion / Discussion> Talk it out before implementing label Nov 8, 2020
@stale stale bot removed the stale Closed for lack of activity, but still valid. label Nov 8, 2020
@stale
Copy link

stale bot commented Dec 9, 2020

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. Please do not 'bump' or comment on this issue unless you are actively working on it. Stale issues, and stale issues that are closed are still considered.

@stale stale bot added the stale Closed for lack of activity, but still valid. label Dec 9, 2020
@LyleSY LyleSY mentioned this issue Jan 25, 2021
Merged
@actual-nh
Copy link
Contributor

Status?

@stale stale bot removed the stale Closed for lack of activity, but still valid. label Jan 25, 2021
@anothersimulacrum anothersimulacrum added (P4 - Low) Low priority issues: things which are e.g exotic, minor and/or hard to encounter [C++] Changes (can be) made in C++. Previously named `Code` labels Jan 25, 2021
@jackledead
Copy link
Contributor

man this sucks

@LyleSY LyleSY mentioned this issue Sep 10, 2021
Merged
@LyleSY LyleSY mentioned this issue Apr 30, 2022
Merged
16 tasks
@mqrause mqrause mentioned this issue Nov 21, 2022
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
[C++] Changes (can be) made in C++. Previously named `Code` (P4 - Low) Low priority issues: things which are e.g exotic, minor and/or hard to encounter <Suggestion / Discussion> Talk it out before implementing
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@LyleSY @anothersimulacrum @actual-nh @jackledead