I want to clarify that by “currently” I mean the info logs will be removed from release builds. They actually shouldn’t be there outside of debug builds and are a bug. The game is intended to be played with the only feedback being data sent over the port from your own hive-- code
Just a quick guess, make sure before any hive-- code you have 0, eg 0q2>x. This specifies the worker to run the code on. Currently, only 1 worker with id 0 is spawned at startup; the plan is to make it so you can build more workers.
Also I will have to mess with that panicking issue, but my suspicion would be that the hivemm code is malformed. In design-notes/hivemm-design there’s some examples
This is a documentation issue, AKA “I need to explain how shit works better” which is an ongoing process. Dbglua is for connecting to the debug socket for inspecting the game state directly, the code for this is in the debug.rs file. Clientlua is an example lua client that connects to the actual gameplay socket. My apologies, proper documentation is on the todo list. Glad you took interest in it tho!!!
Also Hive-- is extremely simple. It’s meant to be a abstracted over, but is very straightforward to learn. Currently the language is documented in the form of design notes under design-notes/hivemm-design.txt. It isnt meant to be user facing but does hold all the information required to use hive--
The game has no ui, it runs as a background process that you talk to over IPC. You send Hive-- code to a worker and any value that code exits with is returned to you over the socket. You can only see the data your workers can gather from the surrounding environment. The debug build currently prints the position of worker 0 to the terminal for development purposes.
Depending on how fast you can teleport you could move pretty quickly. Even 12 teleports a second gets you 4.5 mph in any direction. Could be useful depending on the cooldown but for any significant speed you’d need to teleport really quickly. 20 teleports a second is almost 8 mph
I want to clarify that by “currently” I mean the info logs will be removed from release builds. They actually shouldn’t be there outside of debug builds and are a bug. The game is intended to be played with the only feedback being data sent over the port from your own hive-- code
Currently the only feedback will be in the form of info logs printed to stdout and sending data back over the port via the x command
Just a quick guess, make sure before any hive-- code you have 0, eg
0q2>x. This specifies the worker to run the code on. Currently, only 1 worker with id 0 is spawned at startup; the plan is to make it so you can build more workers.Also I will have to mess with that panicking issue, but my suspicion would be that the hivemm code is malformed. In design-notes/hivemm-design there’s some examples
This is a documentation issue, AKA “I need to explain how shit works better” which is an ongoing process. Dbglua is for connecting to the debug socket for inspecting the game state directly, the code for this is in the debug.rs file. Clientlua is an example lua client that connects to the actual gameplay socket. My apologies, proper documentation is on the todo list. Glad you took interest in it tho!!!
Thanks!!! Hopefully the people who will like this game find it
Also Hive-- is extremely simple. It’s meant to be a abstracted over, but is very straightforward to learn. Currently the language is documented in the form of design notes under
design-notes/hivemm-design.txt. It isnt meant to be user facing but does hold all the information required to use hive--The plan is to have very extensive documentation.
The game has no ui, it runs as a background process that you talk to over IPC. You send Hive-- code to a worker and any value that code exits with is returned to you over the socket. You can only see the data your workers can gather from the surrounding environment. The debug build currently prints the position of worker 0 to the terminal for development purposes.
“Computers don’t make errors” mfs when I upwarp in my super mario 64 run and nobody can recreate it for years
That picture is so unsettling and idk why
Thank god
There’s no way he actually said this. Did he actually say this?
AI :(
What is with the influx of anti voting memes lately holy shit touch some grass
Draw Steel lore is cooler
Oh how I wish
Only if you don’t value your hand. Perhaps you could teleport a hammer into someone’s face
Depending on how fast you can teleport you could move pretty quickly. Even 12 teleports a second gets you 4.5 mph in any direction. Could be useful depending on the cooldown but for any significant speed you’d need to teleport really quickly. 20 teleports a second is almost 8 mph
Big fan of the “let people hate things” motto
Did you just,, use bash variable syntax in a normal sentence?