Have NWNX2 and MySQL on Ubuntu 6.0 Error: DB went away!

[Jesterb769]

im not much for scripting, but if I understood how to write to MySQL right, what I've got looks like this in my module heartbeat

[Papillon]

It looks a bit... unusual, but yes, this should work.
_________________
Papillon

[Jesterb769]

I was never very good with setting timers and such, so that could be the reason
_________________
Jester the Occasionally Merciful
World of Raathi
Creative Director/Admin

[FunkySwerve]

It's worth noting that delaycommands eat up more cpu than equivalent heartbeats, around five times more in nwn1. I haven't profiled your script, but generally speaking its better to use heartbeats for things that you always want running.
Funky

[Jesterb769]

in the interest of expanding my own knowledge then... could I ask how you would suggest doing it instead? I looked at your script and (as embarassing as it is), I didn't quite understand it. I admit I don't quite have a grasp on how the % sign is used yet...
_________________
Jester the Occasionally Merciful
World of Raathi
Creative Director/Admin

[FunkySwerve]

The % is 'remainder'. In normal nwn int division, the remainder is discarded (you can also think of this as always rounding down). With this function, it calculates the remainder as an int, rather than splitting it into a decimal. The quotient is disregarded, only the remainder is output. Here are a few examples:

6%5 = 1, because 5 goes into 6 once, with a remainder of 1.
50%10 = 0, because 10 goes into 50 5 times, with no remainder.
58%5 = 3, because 5 goes into 58 11 times, with a remainder of three.
46%12 = 10, because 12 goes into 46 3 times, with a remainder of 10.

I find it helps to think of the division brace we were taught in grade school:

__42__<----quotient
7/300
28
---
20
14
---
6 <----remainder

With that in mind, have a look at the if clause again:

if (!(nTime%60))

The ! simply reverses the truthhood of the statement it abuts, so that if it is FALSE(0) it becomes TRUE(nonzero), and if TRUE(nonzero) it becomes FALSE.

nTime is being incremented by 5, every 5 seconds. Most of the time, it will have a remainder, but when a multiple of 60 rolls around, the remainder will nonzero, or TRUE. The ! switches it so that its FALSE, except when a multiple of 60 rolls around every minute, when it's TRUE, and the conditional fires sending the SELECT 1 to the database:

5 - 5%60 = 5 (TRUE) so (!5%60) = FALSE
10 - 10%60 = 10 (TRUE) so (!10%60) = FALSE
15 - 15%60 = 15 (TRUE) so (!15%60) = FALSE
20 - 20%60 = 20 (TRUE) so (!20%60) = FALSE
25 - 25%60 = 25 (TRUE) so (!25%60) = FALSE
30 - 30%60 = 30 (TRUE) so (!30%60) = FALSE
35 - 35%60 = 35 (TRUE) so (!35%60) = FALSE
40 - 40%60 = 40 (TRUE) so (!40%60) = FALSE
45 - 45%60 = 45 (TRUE) so (!45%60) = FALSE
50 - 50%60 = 50 (TRUE) so (!50%60) = FALSE
55 - 55%60 = 55 (TRUE) so (!55%60) = FALSE
60 - 60%60 = 0 (FALSE) so (!60%60) = TRUE <-- conditional fires
65 - 65%60 = 5 (TRUE) so (!65%60) = FALSE
70 - 70%60 = 10 (TRUE) so (!70%60) = FALSE
75 - 75%60 = 15 (TRUE) so (!75%60) = FALSE
...
115 - 115%60 = 55 (TRUE) so (!75%60) = FALSE
120 - 120%60 = 0 (FALSE) so (!120%60) = TRUE <-- conditional fires

As you can see, the conditional will fired once per minute. The rest of the heartbeat is negligible overheadwise (and I'm a real stickler in that regard). We use a similar one to check for interserver messages in ourr database: