#bytecode

The article “Python Code: Compiled or Interpreted?” explains how Python uses a hybrid execution model. Python code is first compiled into bytecode and then interpreted by the Python Virtual Machine (PVM), combining benefits of both compiled and interpreted languages. This approach balances flexibility with ease of development, though it may affect execution speed Read More..

Java Bytecode Simplified: Journey to the Wonderland (Part 1)

There are two ways to see a thing. One, see it as it appears to us; two, see it and appreciate it. For example, we get light when we switch on a lightbulb. We press the button and then get busy with our life. Pretty simple, but boring. On the other hand, if we know how the light gets energy from an electrical power grid far from our home with wires, and while traveling through the wires and…

El bytecode es un código intermedio más abstracto que el código máquina. Habitualmente, es tratado como un archivo binario que contiene un programa ejecutable similar a un módulo objeto, que es un archivo binario producido por el compilador cuyo contenido es el código objeto o código máquina . (more…)

WebAssembly: Bytecode Alliance is non-profit and open to new members

The Bytecode Alliance, an initiative for the cross-device and cross-platform standardization of software development based on WebAssembly (Wasm), has received legal status as a non-profit organization. At the end of 2019, Fastly, Mozilla, Intel and Microsoft founded the merger to advance the development of WebAssembly into an independent ecosystem outside of the browser. The common basis is the…

Improve Browser performance using Bytecode Caching

Bytecode Compilation can reduce JavaScript Execution Time on an Embedded Platform Bytecode caching flow Web Browsing is one of the most important software for computing devices like Smartphones, Tablets, and Laptops, etc. The user visits a set of websites and it dominates the total browsing times. Modern Browsers cache downloaded resources in local disks such as HTML, JavaScript, and Image…

I’ve been helping the lovely ladies at fuckyeahgakuenheaven with their translation tools, and trying to figure out the Siglus Engine script format, in the eventuality that they can add voices to their Gakuen Heaven translations and not be restricted for text. I’ve figured out a good chunk of the script format, and now all that’s left in that is to figure out the ByteCode. XD I’m about 40% sure of what each function does. Admittedly, it’s a little more tough to figure out what each piece does than other games I’ve played with.

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

ByteCode is basically when the game goes through the script, reads HEX values, and interprets it as a function in the game. Previously with my work on “Your Heart will be Stolen at the 24th Hour ~ Phantom Thief Jade ~”, I was fortunate enough that the script format for the Yuka Scripts (YKS) used actual text for function names and was fairly easy to figure out, so I could edit the script as I pleased. And boy did I fix a buttload of issues with that game! Even a game-breaking glitch at the end of the game where you couldn’t continue passed the last choice in the true route. Oops!

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

With Angel’s Feather, they’re using an older SCR format by “Studio e.Go!”, and their scripts also use ByteCode. For example, the hexcode “0x0100″ in the script would trigger a textbox for dialog, while “0x0000″ would be used for system functions like setting the title of the window. 

Theirs was a little harder to poke around with, but their functions all had the same format... 2 bytes to specify the function, then 4 bytes saying how long any following data was. The data could be text (wrapped in 0x30 and 0x00), or even more arguments, like where to position an image on screen. I had to manually change these to see what they did in game, then I made an alias name for the code to make it easier to identify for humans. It took a lot of trial and error to figure out what I could, and I still don’t know most of it. Lots of “Unknown_XX” functions floating around. XD Oh well.

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

This week I came to the point where I needed to secure a source-code I wrote on a Raspberry-Pi, which I installed in a publicly accessible control-unit, to be unreadable to others. It took me quite some time to find a solution to secure this source-code. On GitHub I found a simple tool named Bytenode.

Bytenode can be easily installed via npm. Then you can compile Node.JS files into V8 bytecode with this simple command:

bytenode --compile file.js

You can now run the code with:

bytenode file.jsc instead of node file.js.

And that’s it!