|
Development Forum |
 |
| Ethics of disabling clone-on-import | |
| 
Sgeo

|
11/17/2013 | 1 |
So, it's fairly easy to disable cloning-on-import for Creatures that originated from another user's world. But if a Warp or Warp-like thing ever came back, then 'duplicated' creatures would collide, and the Warp mechanism may have to kill some. So, what's the best thing to do?
Disable export of imported norns who should have been cloned? And what of their children, since having children of 'duplicates' roam the Warp could result in confusing histories?
Disable the Warp in worlds where this is active? Since there currently is no Warp, this should have minimal effect, although future Warps may have to detect the presence of my agent. And, unlike the above solution, this cannot prevent children of duplicated norns roaming around, but that is a less severe problem than duplicated norns themselves from roaming around.
Also, I would love to integrate with CreatureLink, if there was a way in the .creature file to indicate a CL norn, I could just import without preconditions like unexportable or disabled Warp.
Neurogengineer and founder of the Creatures Wiki. |

Siinamon
 
|
11/17/2013 | |
I don't think that the children of duplicate creatures will necessarily pose a problem. I mean, the heritages will be kind of weird across worlds, but at least there will be no major conflicts like a twice-imported and warp killage.
This duplicate creature thing is going to be interesting to see develop.
What would it take for, instead of the warp to be aware of your agent, have the agent be aware of the warp? |

Sgeo

|
11/17/2013 | |
Unfortunately, it would require predicting the future.
If the community ends up using the old Warp protocol, not requiring extra agents or CAOS changes etc., then it's just the same as interacting with the old Warp. Easy enough for me to look in the bootstrap and change what I'd need to change. I could have my agent affect that under the assumption that this occurs.
However, I remember hearing about some kind of replacement in the works, and if it's not interoperable with the current Warp mechanism, I would need to see it and modify it in order to be able to affect that, which I can't do with code that doesn't even exist yet.
Neurogengineer and founder of the Creatures Wiki. |

Siinamon
 
|
11/17/2013 | |
Very true, sadly. From what I read on the thread regarding the Warp, it will be agent-based. This should allow some sort of interoperability, I'd imagine. If one is able to get a hold of the code, that is... |
|