Heh, you know Josan, I really don't know much about this. Just thinking out loud.
I have no idea if this will work and what will happen with the ones that don't get a bed. They would keep going on with their normal business I hope (by checking a variable to not going for a bed anymore if all beds are taken).
I don't like this way much though, with everyone moving at once.
But I don't know if much can be done without giving them individual scripts.
Nah, what I was suggesting was that they all go for the same hex. The first critter to reach it gets that bed, so the rest will then go for the next available hex (bed), and so on until they are all taken. What you said would probably work pretty much the same way.Josan12 said:So if i understand correctly are you suggesting i assign a list of beds (hexes) to the generic critter script. Then have them select one at random. So the final result will be that most critters find seperate beds. Some, of course, will choose beds already taken - so i guess i need to test to see what happens.
I have no idea if this will work and what will happen with the ones that don't get a bed. They would keep going on with their normal business I hope (by checking a variable to not going for a bed anymore if all beds are taken).
I don't like this way much though, with everyone moving at once.
But I don't know if much can be done without giving them individual scripts.
I think the trigger for both go in critter_p_proc (by checking the time). What you need is two different sequences. I don't know how to do it but know it can be done.Josan12 said:Ok. So does that mean going to bed and getting up need seperate procs?Darek said:Also the sleep sequence would have to be split into two, one for going to bed and a second for waking up at the correct time.