The Dink Network

Last year, someone came over on the discord and was asking around for help converting some .rttex files from Growtopia.

This fella was using a Mac and the only tool for it at the time was no longer maintained and unsupported on Mac. ( https://github.com/Nenkai/RTPackConverter )

So at the time, I forked the project and ported it to .NET7, setting it up so it builds for MacOS too. https://github.com/drone1400/RTPackConverter

Anyway, today I have updated it to .NET8 and also configured the github actions to build/publish it for arm64 based MacOS.

Latest Release: https://github.com/drone1400/RTPackConverter/releases/tag/V2.0.4

Why am I posting about it on a Dink forum?

Well, you can also use it to extract DinkHD textures and fonts if you so desire. (The stuff in DinkHD's interface folder)

I'm not sure how useful any of that would be to anyone, but if anyone is curious, know that you can now do so!

NOTE: I have no way of testing the MacOS builds myself, but they *should* work. At least, it worked for that person last year...

I'm using macOS 11 and the x64 build doesn't seem to want to do anything even after installing the runtime. I chmod +x it and then run from the command line and it just says "exec format error".

As it's somewhat related, Seth has the source PNGs in the RTDink repo under "media" in case someone wants to reskin the gui.

Out of curiosity, does the previous V2.0.0 work for you? That one was built with .NET 7 and it seemed to work then, although I'm not sure what macOS version he had...

EDIT: This might be a dumb question, but you're using the right 64 bit version right? I mean x64 vs arm64. Asking since I see that macOS 11 is available for both x86 and arm processors and idk what you're using.

No, it does the exact same thing for me. The plot thickens however, and running it through binutils readelf tells me it's an ELF64 rather than a Mach-O, suggesting it's a Linux binary even though it's in the osx-x64 package. Keep in mind i'm working from the assumption I could just double-click it rather than using Mono or whatever.

The mysterious issue has been solved! It seems I had some problem in my github CI/CD config file and files weren't being cleaned up when making a subsequent build for a different platform.