The Basic principle is:
- 1. Pressure cook an item
2. Put into Test Tubes
3. Put it into Alembic
4. Repeat at 1
Step 1 raises the purity for sure and is the driving factor of the process. Step 2 is required to (randomly) raise some purity values. Together with the first step, the mean value of the random is slightly shifted to positive values. This means, provided enough runs, purity should go up over time. The main problem is the instability, which has to be countered with an alembic.
And here comes crucial point:
Does the alembic provide enough reduction of instability, while removing less purity than the Pressure Cooker/Test Tubes create?
I wrote an test application, which implements the functionality of the alchemy processors (Test Tubes, Pressure Cooker, Alembic, Retort) and creates test runs with changing parameters. The basic principles work, but i lack reasonable input parameters (like change rates, instability increments, ...).
For this reason i started this thread and ask all fellow pilgrims to help me gathering data. Assuming that enough data can be aquired, i'll run statistical analyses on them and post the results here. What i need are test runs from all alchemy processor formated like this:
- Code: Select all
("Alchemy Processor Name",
[purityValues before],
[purityValues after],
["stability before", "stability after"])
Here is an example:
- Code: Select all
("Pressure Cooker",
[.2, .2, .35, .25],
[.19, .19, .35, .27],
["slightly unstable", "somewhat unstable"])
("Pressure Cooker",
[.2, .2, .35, .25],
[],
["slightly unstable", "destroyed"])
I would appreciate if you guys could use the pattern above, because it helps parsing the data automatically. If some equipment is destroyed like a stove or an alchemy processor, just write it down in plain text until i figure out a better way.
Every sample helps!
Thanks.