Skip to content

Conversation

@drakewill-CRL
Copy link
Contributor

@drakewill-CRL drakewill-CRL commented Aug 26, 2024

About the PR

This PR will take most of the checks for plant growth and pull them into their own tiny components and systems, instead of being part of 1 huge function.

This is part of my Botany Rewrite proposal. Future PRs will handle making Plants a proper entity for components, and maybe other improvements.

Why / Balance

This is to make future plants more flexible, and open up more possibilities for the Botany system the current fixed setup allows. Everything right now is in PlantHolderSystem.Update() and all plants are identical, and it will be better to pull those apart into their own systems and components so each plant can check only what it cares about. This also allows individual plants to have unique code run on a growth tick, including wild or interesting effects not actually related to the plant growing.

As a refactor PR, balance isn't being changed, so as much of the existing logic as possible will be directly moved over. In the end, changes to how the system fires off may cause something to behave differently, but the core of waiting for plants to grow will remain. The time involved, or the sensitivity of plants to environmental factors, may possibly be noticeable if they need entirely redone for this.

Technical details

This includes making components and systems for the logic around water, nutrients, toxins, pests, gases consumed or exuded, tolerance for light/pressure/ heat, and auto-harvesting.

In the future, plants will be able to have different needs for growth, (EX: a cactus may not check for water, or space-plants may be dependent on special chemicals being present) and different effects can happen on a growth tick without hard-coding more checks into PlantHolderSystem. This also opens up possibilities to mutate these needs off of, or onto, other plants. In particular, a future-state plan for mutations requires plants to be able to consume plasma gas to start acquiring stronger mutations, and that will be its own growth component to trigger that change.

In the process of coding this, the following stats were removed: LightTolerance/Ideal Light (Unused and possibly unmeasureable).

Media

Nothing should be visibly different.

Requirements

  • I have read and I am following the Pull Request Guidelines. I understand that not doing so may get my pr closed at maintainer’s discretion
  • I have added screenshots/videos to this PR showcasing its changes ingame, or this PR does not require an ingame showcase

Breaking changes

This shouldnt affect anything outside of PlantHolder. TODO: confirm when work is complete.

Changelog

Nothing should be player facing. TODO: confirm when work is complete that there's nothing tangibly different for the player.

@github-actions
Copy link
Contributor

github-actions bot commented Sep 2, 2024

This pull request has conflicts, please resolve those before we can evaluate the pull request.

@github-actions github-actions bot added the S: Merge Conflict Status: Needs to resolve merge conflicts before it can be accepted label Sep 2, 2024
@github-actions github-actions bot removed the S: Merge Conflict Status: Needs to resolve merge conflicts before it can be accepted label Sep 8, 2024
@github-actions
Copy link
Contributor

This pull request has conflicts, please resolve those before we can evaluate the pull request.

@github-actions github-actions bot added S: Merge Conflict Status: Needs to resolve merge conflicts before it can be accepted Changes: UI Changes: Might require knowledge of UI design or code. Changes: Map Changes: Might require knowledge of mapping. Changes: Sprites Changes: Might require knowledge of spriting or visual design. and removed S: Merge Conflict Status: Needs to resolve merge conflicts before it can be accepted labels Sep 13, 2024
@github-actions
Copy link
Contributor

This pull request has conflicts, please resolve those before we can evaluate the pull request.

@github-actions github-actions bot added the S: Merge Conflict Status: Needs to resolve merge conflicts before it can be accepted label Sep 21, 2024
@SlamBamActionman
Copy link
Member

SlamBamActionman commented Nov 1, 2024

Hello! This PR is seen as conceptually favorable by maintainers, however it seems the branch has some issues that has caused it to incorrectly modify files. I will be marking this PR as stale and close within a week; you can either fix the branch with the current PR submission (at which point I will unmark it as stale), or you're free to open a new PR with a fixed branch. Thank you!

(oops clicked "Close with Comment" instead of "Comment", my bad!)

@SlamBamActionman SlamBamActionman added the S: Stale Status: Stale with no activity, and may be closed after a week if there is no new activity. label Nov 1, 2024
@SlamBamActionman SlamBamActionman self-assigned this Nov 1, 2024
@drakewill-CRL
Copy link
Contributor Author

That should fix the branch. I'll have to pick this up and see where I was. I do think that my plants-as-entities Part 3 PR should get merged first at this point, and I'll un-draft this one after its merged and I get this reworked to matched that.

@github-actions github-actions bot removed the S: Merge Conflict Status: Needs to resolve merge conflicts before it can be accepted label Nov 2, 2024
@SlamBamActionman SlamBamActionman added S: Untriaged Status: Indicates an item has not been triaged and doesn't have appropriate labels. and removed S: Stale Status: Stale with no activity, and may be closed after a week if there is no new activity. labels Nov 8, 2024
@Qwazori
Copy link

Qwazori commented Jan 9, 2025

when?

@Emisse Emisse removed the Changes: Map Changes: Might require knowledge of mapping. label Jan 19, 2025
@github-actions
Copy link
Contributor

github-actions bot commented Feb 8, 2025

This pull request has conflicts, please resolve those before we can evaluate the pull request.

@github-actions github-actions bot added the S: Merge Conflict Status: Needs to resolve merge conflicts before it can be accepted label Feb 8, 2025
@BramvanZijp BramvanZijp removed the S: Untriaged Status: Indicates an item has not been triaged and doesn't have appropriate labels. label Mar 1, 2025
@BramvanZijp BramvanZijp added P3: Standard Priority: Default priority for repository items. T: Refactor Type: Refactor of notable amount of codebase D2: Medium Difficulty: A good amount of codebase knowledge required. S: Stale Status: Stale with no activity, and may be closed after a week if there is no new activity. A: Service Area: Service department, including cooking, botany, etc S: Draft Status: This is a draft and might need to be retriaged upon opening. labels Mar 1, 2025
@MilonPL
Copy link
Contributor

MilonPL commented Apr 18, 2025

Thank you for your contribution! Due to this PR being marked as a draft and having no activity, we've decided to close it. If you ever come back to it, feel free to open a new PR.

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

Labels

A: Service Area: Service department, including cooking, botany, etc Changes: Sprites Changes: Might require knowledge of spriting or visual design. Changes: UI Changes: Might require knowledge of UI design or code. D2: Medium Difficulty: A good amount of codebase knowledge required. P3: Standard Priority: Default priority for repository items. S: Draft Status: This is a draft and might need to be retriaged upon opening. S: Merge Conflict Status: Needs to resolve merge conflicts before it can be accepted S: Stale Status: Stale with no activity, and may be closed after a week if there is no new activity. T: Refactor Type: Refactor of notable amount of codebase

Projects

None yet

Development

Successfully merging this pull request may close these issues.

7 participants