Open osjarw opened 5 months ago
As vet chemist gonna call this one a featue(certainly not biased :trollface:).
After hotplate and microwave nerfs a lot of medicine would become hellish for newbie/okayish chemists and I would not be surprised if 2 hour shift would still not be enough to make what medbay needs. They are already taking their sweet time reading guidebook and making sure their notes are in order, waiting and staring at Pyr premix is going to make them ssd when they get tired of fighting over who gets to use hotplate with other chemists.
Vets would probably just make lavabeakers but dilluted instead via buffer chems so greener chemists would need strong heating option or some way to store thermals more easily and "inject" them when needed perhaps?
If your problem making Dip specifically, you can use basic premix and pour it into jugs except for last batch, this one you cook and then pour ready Dip into premix which creates hot Dip which can be poured again and again... Then there is option to avoid microwave/hotplate heat and using reductive reaction of sulfuric acid or acetone and mixing that instead.
Of course there is always option of reductive water+potassium bucketmixing but then I bet someone will want to stop chemists blowing up chemlab being the correct way to do chemistry when time is of essence, which it always is in medbay.
Please do not kill speedchem, it's going to be such an ass to cook everything without temperature lock master has... As for mass Dip, just do not cook it in master? It has oil heat trap for newbies for a reason, so it wouldn't be mass produced by fresh chemists. If anything, i would love to have more recipes harder/easy to fuck up due to heat. (totally don't want to make temp lock into a feature :trollface: )
Heat traps and cold recipes would be what I would love as chemist myself too. Now its meta to have lavabeaker except dip/premix bombs/oil, but if it was tool that can go wrong often if misused it would be way better.
Hotplates/microwaves(50% power of hotplate roughly, though I suppose you can heat many beakers/jugs at once) would need HUGE buffs because how weak they are for adding energy to solutions, thats main reason how people learned and started using lavabeakers - to escape hours of waiting.
Reductive reaction chemisty would also be greatly nerfed if master heating/cooling were to be removed and stealing/bombing hotplate would send medbay way earlier than just stone age.
Description
Ever tried mass producing diphenhydramine? if so, then you most likely have experienced the curious case of seeing oil turning to ash the moment you move oil from chemmaster to a beaker that you used to produce the last batch of diphenhydramine.
Basically chemmaster doesn't do any temperature handling. When it moves stuff from buffer to a beaker, the beaker temperature doesn't change.
Reproduction put some liquid in chemmaster heat 1u of something in a beaker, to 1000k for example move lots of stuff from chemmaster to beaker regardless of how much stuff you moved to the beaker, it still remains at 1000k
Additional context The chemmaster basically behaves as a massive jug, with a single solution container, and uses it to store all chems. Since temperature is tied to the containers and not the solutions, the chems have to share the same container temperature.
Most likely temperature handling was just an afterthought, and left unimplemented.
Possible solutions
Magically make the chemmaster output chems always at room temperature, lorewise we can just say that it has some cooling system in it.
Use the single solutioncontainer to track heat, essentially mixing together the temperatures just like how beakers do. there most likely won't be any problems with this method, unless someone fills the chemmaster with superheated liquids. Pyra perhaps. We should probably allow the users to somehow see the temperature.
Make the chemmaster use multiple solution containers, lorewise it can just use a bunch of jugs or something. I think that this solution makes the most sense in terms of how the device would work in reality.
~~I think I'll implement solution 2 soon, just so we can get rid of this bug. Later on I can attempt 3, from what I can tell it isn't that hard to implement.~~