[Harven]

Originally Posted by CatoTheElder The application is 32 bit, so I wouldn't try passing a 64-bit value to a 32-bit application.

Hey, and why is that? Nothing is stopping you from using 64bit variables in 32bit machine/system/application. Here is some simple C application example:

#include <stdio.h>
#include <stdlib.h>

int main( int argc, char *argv[] )
{
        unsigned long long integer64bit = 0xffffffffffffffff;
        printf( "%d %llu\n", sizeof(long long), integer64bit );
        return EXIT_SUCCESS;
}

I'm runing it on my 32bit ARMv7 machine, and the output is:

[harven@fedora-arm test]$ ./bittest
8 18446744073709551615

And in the game on my 64bit Windows 7:

/script local var = 18446744073709551615 d(var.." type: "..type(var).." "..string.format("%l", var))

gives this:

1.844674407371e+019 type: number

Luaindex is not a type, it's a clue so we know what numbers we can use. It's like

typedef double luaindex

you can still pass -1, 3.2 and so one, but the name tells you what the function expects.