TomCube2

It's supposed to play back a set of inputs when the command is run, sort of like a piano roll for a player piano. It has a packet format, with a length byte and and array of that length of bytes. Each byte in the array corresponds to a value in the InputButtons enum. Alas, it doesn't load the inputs properly and I haven't the slightest idea why -- it's not an IO thing, so I'll have to do some deeper debugging.

Similar to RainbowSkeppy, I've also made Bad Apple, but it's server side. Video here, source code here. Client-side survival (designed for singleplayer): https://github.com/yomcube/ClassiCubeServyvalPlugin. No mobs or HP anything, just block functionality. Simple command-line ClassiCube launcher written in Python: https://github.com/yomcube/classicube-stuff/blob/main/ClassiCube/CCLaunch.py Nonfunctional client-side TAS plugin (work-in-progress): https://github.com/yomcube/ClassiCubeTASPlugin. The client's Input.h has to be modified such that NormDevice and Input become CC_VAR (originally extern). Outdated plugin for C# plugins (and other Mono languages): https://github.com/yomcube/ClassiCubeMonoPlugin. This almost certainly won't compile anymore.

You need to use the raw file (https://raw.githubusercontent.com/ClassiCube/MCGalaxy-Plugins/refs/heads/master/plugins/utilities/RelayRoute.cs)

You can also manually compile plugins by referencing MCGalaxy_.dll. From the root directory: mcs -target:library -r:MCGalaxy_.dll -out:plugins/{PLUGIN}.dll plugins/{PLUGIN}.cs From the plugins directory: mcs -target:library -r:../MCGalaxy_.dll -out:{PLUGIN}.dll {PLUGIN}.cs These command line arguments are the same for mcs and csc.

I haven't tested it, but I'm 90% sure it works on vWii, 99.9% sure it won't brick your Wii U

I saw issue #765 and realized it was fairly simple to implement so I added it. It has no use in single player because there's no MOTD or server name in singleplayer.

"You can use any host you want though" – An unspecified source

Good morning, and in case I don't see ya, good afternoon, good evening, and good night!

Don't check the file update time; store the value of `latest_ts` in a file (I'd recommend an entry in `options.txt` Actually, don't put it in `options.txt`. I saw that you have JSON files, so it'd probably be better to use those) so you can compare it when you update

I'm on mobile so I can't test it atm, but this looks like a really cool project! A few things that I think you can improve (this is only from looking at the code, so I may not get the full picture): Move initialization logic (creating directories, etc.) into separate function instead of in the file scope Instead of downloading CC every time the program is opened, check for updates using builds.json; as update logic gets more complex, move updating to separate class Detect OS using `os.name`/`sys.platform`/`platform.system()` (see here) + `is_64bit = sys.maxsize > 2**32` to download the correct binary Line 21-22: Change `finally: "Do nothing"` to `except: pass`; `finally` does nothing to stop errors because there's nothing to catch them; `pass` is a better way to say `"do nothing"`

If you minimize the window it'll contain itself to the system tray and remove itself from the taskbar

`IsometricDrawer_Render` could be used with a `count` of 1

If it were CC_API, I'd suggest `IsometricDrawer.c/h`, but it sadly isn't

Not very well. I used the wrong tense there 😕 (I meant vi, not vía)

Ah, lo vía. Es muy bien

No sé ¯\_(ツ)_/¯

Sí, pero eso será muy fácil con la práctica

There's not really an easy way like Scratch, so I'd recommend learning C.

Unfortunately, no

Documentation for making client plugins can be found here: https://github.com/ClassiCube/ClassiCube/blob/master/doc/plugin-dev.md

The skin server is defined in options.txt iirc

Use the online version. Singleplayer: https://www.classicube.net/server/play/ Multiplayer (login required): https://www.classicube.net/server/list/

You could maybe possibly perchance try actually doing what it says to do? Idk man, just a thought...

I mean, you could also look at the README. I wonder if there's anything related to MacOS in the Setup section...

I completely agree. Someone should really put that in the README or something! Though, I definitely shouldn't assume people would read it.