-
Notifications
You must be signed in to change notification settings - Fork 25
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
Consider changing meten machine back to cloning #8
Comments
The metem machine is less like a cloning machine, because there's a chance it changes the race of the cloned entity, I personally think it should be left as it is. Or at least retain the same functionality. |
There's no need to, and there's also no need to modify the cloning system either. If you don't want to use the Metem machine, just don't map it, and map the cloning machine instead. The same cloning code system services both machines. |
But also, comment out the metem machine at your own peril, the cloning system has prototype ensures for its machines, and will throw crashy errors if it can't find its prototypes. If you really want to make it unobtainable at all, your best best will be to comment it out of science, and loot pools. |
Functionality is fine. Errors in cloning is good, can make up for not having the same cloning errors of 13 like Brian damage and cell damage that stop you taking coherently. It’s just the name for me if it’s going to life in medbay. |
Ah okay, explaining it that way can make sense. If you call the Metem machine the Cloning Machine, and call the original cloning machine the "Advanced Cloning". |
Auto correct did me dirty. But yeah good idea |
Description
The name bugs me now that epistemics is a sub dept. I kind of like that it raises glimmer, if we are keeping glimmer, but otherwise that can be provably explained as breaking the laws of nature by cloning.
Need opinions on this one.
The text was updated successfully, but these errors were encountered: