When Dream Daemon is the parent, startup will work and create the child, or slave.
Now the slave is being used as a utility to manage other stuff, including updating the server with new files, but startup wont work for the child.
Numbered Steps to Reproduce Problem:
Create a world, have the world create a child via startup() and then have that child create a new child via startup()
Code Snippet (if applicable) to Reproduce Problem:
startup()
Expected Results:
Child worlds making more child worlds for infinite babies.
Actual Results:
No babies are made ;( they're all sterile.
Does the problem occur:
Every time? Or how often? Always
In other games? Unsure
In other user accounts? Of course
On other computers? Yep
When does the problem NOT occur?
I dont know, I would like to know though.
Did the problem NOT occur in any earlier versions? If so, what was the last version that worked? (Visit http://www.byond.com/download/build to download old versions for testing.)
Before the 5.0 update it worked, from what I recall anyway.
Workarounds:
use shell to manage daemons and use python for additional stuff but it seems a bit unnecessary.
Maybe there's even some params that might get this to work. -suidself might work