ZoriaRPG
06-08-2015, 02:11 PM
I'm trying to cross-associate ZScript functions, to ZASM, for the purpose of documentation, and while running qa simple test, compiling and ticking 'Output ZASM to allegro.log', the output was garbage:
Ä
H€Š*y–nit
Ä
This was produced by placing into the compiler buffer:
global script init{
void(run){
Sin(30);
Rand(40);
}
}
Compile + Output ZASM.
It seems that the declaration of global script init, on its own, produced corrupted assembly.
I should be seeing pure ASCII output, with ASM instructions. This looks more like binary code represented as ASCII text... What exactly is happening here?
Further, despite making a fully new quest, and entering only one global active script into the buffer, then compiling, in the ZASM output, I see these lines:
GhostZHActiveScript
GhostZHActiveScript
Ä
H€Š*y–nit
How is GhostZHActiveScript being retained, and stored in a log file, for a quest with no active script, and no calls to Ghost.zh at all?
Is this something Saffith added to ZASM?
Ä
H€Š*y–nit
Ä
This was produced by placing into the compiler buffer:
global script init{
void(run){
Sin(30);
Rand(40);
}
}
Compile + Output ZASM.
It seems that the declaration of global script init, on its own, produced corrupted assembly.
I should be seeing pure ASCII output, with ASM instructions. This looks more like binary code represented as ASCII text... What exactly is happening here?
Further, despite making a fully new quest, and entering only one global active script into the buffer, then compiling, in the ZASM output, I see these lines:
GhostZHActiveScript
GhostZHActiveScript
Ä
H€Š*y–nit
How is GhostZHActiveScript being retained, and stored in a log file, for a quest with no active script, and no calls to Ghost.zh at all?
Is this something Saffith added to ZASM?