27 réponses à ce sujet

[Tarot Redhand]

@meaglyn you're not stepping on anybodies toes, the more the merrier. As I have never knowingly (accidentally might be another matter) written code for mp, I'll bow to your knowledge there. For sp I would think my boolean is probably more efficient (but for such a tiny thing efficiency probably doesn't matter). When I was doing my experiments earlier in this thread I did find that a heartbeat for one area could appear to be still be working when you are another area. I had the PC speaking a set of numbers (vector) and I was getting the results from a different areas hb script until I disabled that particular hb. Which is one of the reasons I suggest going with a phb. 

 

TR

[meaglyn]

Okay, okay...  I've uploaded a new version that works on a single PHB which runs every hour so that it can update the positions when the day changes etc. It starts on PC enter if not already running. And then checks if there are PCs in the area before rescheduling itself. No need mess with a counter, which can get out of sync if a PC dies in there (of course there won't be any violence in such a place, right?).

 

Rolo, I moved the initial moon position back to south because for some reason the first SetFacing, which is to 347.xxx does not apply if it is too close to the painted position.  If it was at least two "ticks" away from 347 it did fine. Later ones seemed to be better but I did not advance many days.  This is unrelated to the change to PHB however since all the code for this is the same as it was before.  I tried a hack of making the first move farther away and then to the right place but it didn't work.  Putting it here won't really solve the problem since that could be near the right location when someone does enter.  But it makes the demo look better

[meaglyn]

This one is better https://db.tt/hGJZrBWM. The one last night seems to have been the old one, at least that's what I got from dropbox when I downloaded it. This one runs the PHB every 6 seconds until the first hour tick and then goes to every hour. The other one could have been up to almost an hour slow in doing rises/sets depending on when the first PC entered the area.  It's not completely tested because there is only one area so there's always a PC in the area.

 

It looks like the rotation just does not like to work when it is a small amount. Getfacing reports the new setting but the placeable does not rotate. May need to poke at that a bit.