2022-02-06 13:14:41 -07:00
|
|
|
using Content.Server.Botany.Systems;
|
2024-02-01 13:33:57 +00:00
|
|
|
using Content.Shared.Botany.Components;
|
2022-04-16 17:32:35 +12:00
|
|
|
using Robust.Shared.Serialization.TypeSerializers.Implementations.Custom.Prototype;
|
2020-10-26 23:19:46 +01:00
|
|
|
|
2022-02-06 13:14:41 -07:00
|
|
|
namespace Content.Server.Botany.Components;
|
2021-03-05 01:08:38 +01:00
|
|
|
|
2022-02-06 13:14:41 -07:00
|
|
|
[RegisterComponent]
|
2022-06-07 15:26:28 +02:00
|
|
|
[Access(typeof(BotanySystem))]
|
2024-02-01 13:33:57 +00:00
|
|
|
public sealed partial class ProduceComponent : SharedProduceComponent
|
2022-02-06 13:14:41 -07:00
|
|
|
{
|
|
|
|
|
[DataField("targetSolution")] public string SolutionName { get; set; } = "food";
|
2020-10-26 23:19:46 +01:00
|
|
|
|
2022-04-16 17:32:35 +12:00
|
|
|
/// <summary>
|
|
|
|
|
/// Seed data used to create a <see cref="SeedComponent"/> when this produce has its seeds extracted.
|
|
|
|
|
/// </summary>
|
Botany Rework Part 1: Mutations (#31163)
Instead of each mutation being a flag that gets checked at some unique point in BotanySystem somewhere, they're now EntityEffects that get applied when the mutation occurs and when produce is harvested. One new list was added to SeedData so that multiple other fields could be removed.
All the non-stat-change mutations that have been rolled are added to the Mutations list, and get applied to the plant when the mutation occurs or when a seed with the mutation is planted. Produce get mutations applied at harvest if they apply to the produce, and carry all of the plant's mutations over as a seed. This gets rid of the one-off checks for things like Slippery, Bioluminescent, Sentient, etc.
The base odds of a mutation applying should be equal to the odds of the original mutation check. It pretended to have 1 bit flip (on averge) per mutation power, and odds of each mutation was the odds of one of its bit being flipped (1 /275 * bits). The 'thermometer code' applied for numbers will be replaced with simple random rolls, as both average out to the middle value. The new checks are much easier to understand and don't obfuscate the actual changes of something happening behind 3 layers of math. The biggest player-facing change is that Potency will be able to get over 65 significantly more often than it did in the previous system, but it will be just as common to get low values as high ones.
Mutation definitions have been moved to a .yml file. These include the odds per tick per mutagen strength of that mutation applying that tick, the effect applied, if it applies to the plant and/or its produce. This makes mutations simpler to add and edit.
This PR is limited specifically to the mutation logic. Improving other aspects of the system will be done in other PRs per the design document. Mutations was chosen first because its got the largest amount of one-off checks scattered all over that could be consolidated. Once this is merged, mutations could be contributed to the codebase with minimal extra work for later botany refactor PRs.
2024-09-14 23:12:17 -04:00
|
|
|
[DataField]
|
2022-04-16 17:32:35 +12:00
|
|
|
public SeedData? Seed;
|
|
|
|
|
|
|
|
|
|
/// <summary>
|
|
|
|
|
/// Seed data used to create a <see cref="SeedComponent"/> when this produce has its seeds extracted.
|
|
|
|
|
/// </summary>
|
Botany Rework Part 1: Mutations (#31163)
Instead of each mutation being a flag that gets checked at some unique point in BotanySystem somewhere, they're now EntityEffects that get applied when the mutation occurs and when produce is harvested. One new list was added to SeedData so that multiple other fields could be removed.
All the non-stat-change mutations that have been rolled are added to the Mutations list, and get applied to the plant when the mutation occurs or when a seed with the mutation is planted. Produce get mutations applied at harvest if they apply to the produce, and carry all of the plant's mutations over as a seed. This gets rid of the one-off checks for things like Slippery, Bioluminescent, Sentient, etc.
The base odds of a mutation applying should be equal to the odds of the original mutation check. It pretended to have 1 bit flip (on averge) per mutation power, and odds of each mutation was the odds of one of its bit being flipped (1 /275 * bits). The 'thermometer code' applied for numbers will be replaced with simple random rolls, as both average out to the middle value. The new checks are much easier to understand and don't obfuscate the actual changes of something happening behind 3 layers of math. The biggest player-facing change is that Potency will be able to get over 65 significantly more often than it did in the previous system, but it will be just as common to get low values as high ones.
Mutation definitions have been moved to a .yml file. These include the odds per tick per mutagen strength of that mutation applying that tick, the effect applied, if it applies to the plant and/or its produce. This makes mutations simpler to add and edit.
This PR is limited specifically to the mutation logic. Improving other aspects of the system will be done in other PRs per the design document. Mutations was chosen first because its got the largest amount of one-off checks scattered all over that could be consolidated. Once this is merged, mutations could be contributed to the codebase with minimal extra work for later botany refactor PRs.
2024-09-14 23:12:17 -04:00
|
|
|
[DataField(customTypeSerializer: typeof(PrototypeIdSerializer<SeedPrototype>))]
|
2023-08-22 18:14:33 -07:00
|
|
|
public string? SeedId;
|
2020-10-26 23:19:46 +01:00
|
|
|
}
|