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.

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

The age_grow and baby_timer attributes take more time than intended #37324

Closed
RarkGrames opened this issue Jan 23, 2020 · 4 comments
Closed

The age_grow and baby_timer attributes take more time than intended #37324

RarkGrames opened this issue Jan 23, 2020 · 4 comments
Labels
stale Closed for lack of activity, but still valid.

Comments

@RarkGrames
Copy link
Contributor

Describe the bug

Animals take 2-3 more time to grow from their young to mature animal than the number specified in their age_grow entry. Spawned a calf, a cattle dog puppy, a bulldog puppy, a piglet, a bear cub. They matured in 2-3 times the amount of days given at age_grow.
baby_timer seems to be the same (2-3 times the given value).

Steps To Reproduce

Steps to reproduce the behavior:

  1. Spawn a calf and teleport 5+ tiles away.
  2. Forward the world time by 200 days (calf age_grow is 180).
  3. Teleport back to the calf.
  4. It fails to upgrade.
  5. Repeat the above 1-2 more times.
  6. The calf is now upgraded.

Expected behavior

Animals upgrading according to their age_grow attribute, reproducing according to their baby_timer attribute.

Versions and configuration

  • OS: Windows
    • OS Version: 10.0 1909
  • Game Version: 0.D-11543-g3e11834 [64-bit]
  • Graphics Version: Tiles
  • Mods loaded: [
    Dark Days Ahead [dda],
    Disable NPC Needs [no_npc_food]
    ]

Additional context

See comments in #37283.

@SirPendrak
Copy link
Contributor

Maybe its related to default evolution rate being x4 as slow?

@RarkGrames
Copy link
Contributor Author

No, this is a fixed number. Evolution uses a different calculation that is semi-random and based on the evolution speed.

@stale
Copy link

stale bot commented Feb 23, 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 Feb 23, 2020
@stale
Copy link

stale bot commented Mar 24, 2020

This issue has been automatically closed due to lack of activity. This does not mean that we do not value the issue. Feel free to request that it be re-opened if you are going to actively work on it

@stale stale bot closed this as completed Mar 24, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
stale Closed for lack of activity, but still valid.
Projects
None yet
Development

No branches or pull requests

2 participants