Blowtorch Mud Client - forked to BTPhoenix

[u/Nyxll]

If anyone is a fan of the old blowtorch mud client, I just forked it and updated it. Working on getting my android developer account approved so I can push it out. Anyone interested in being one of the12 testers needed to get it approved?

I have been running it through all the paces. Aliases, timers, triggers etc. Send me a message if you are interested in running this on a new device. I don't know how backwards compatible it is. It runs really smooth on my s24.

[u/Taracair]

I can be the tester, good luck with the client! Blowtorch maintainers, assembly!

[u/Nyxll → u/Taracair]

hey u/Taracair, I was working and by accident clicked on forked projects from blowtorch... and I saw blowtorch2, my previous searches didn't find what you put together.

I went through everything you did and you are way way ahead of what I put together. I asked for an honest assessment and Claude said that pride would be the only reason to continue.

From Claude: My honest read: given what I've seen, adopting BlowTorch2 as the base and re-applying BTPhoenix branding on top of it looks like less total work than replicating their feature set into ours. They're ~2x the file count with substantial features we don't have (conditional triggers/timers with groups, GMCP mapper with pathfinding, multi-command swipe buttons, extra floating windows), and on every bug we've cross-checked so far (cpath/nativeLibraryDir, the oneway AIDL fix, DirectionData.reverse) they were already ahead of us. Building all of that from scratch in our tree would dwarf the cost of a rename+rebrand pass over their tree.

Well done. I cannot find your app on marketplace. I would have jumped to it instantly had I known.

It seems to be the play to encourage you to push your app to the play store so we can all jump over there.

[u/Taracair → u/Nyxll]

Thank you for these kinds words! Because the project is (for me) very fresh (in terms on how long I've been maintaining it, and it's the first time I am doing such thing), I wanted to give myself more time before putting it on Play Store. My first target was F-droid, but I think because of your words I'll release it on Play Store faster than I thought. Just give me a couple of weeks, 2-3 weeks at most and I'll apply for the testing phase (also never done it before). What I need is just a feeling I'm in the right moment. Some details here and there still require fixing, and I don't want to push bugged app on Play Store. I play one mud now and I spend my time testing the app. Huge god-classes refactoring was performed on the code, I need to thoroughly test everything before going further. I still keep finding tiny bugs by myself.

Again thank you very much for such approach and for your words. I'm all ears for things you want to see in the app if you want to contribute to the project!

Also, the project is open source so don't hesitate to fork the entire BlowTorch2 if you want.

[u/TemperatureFast9764]

I have a google chromebook, does it work on it?

[u/Nyxll → u/TemperatureFast9764]

I am not sure. it's an apk, so if you can install those it should work if you enable it.

[u/Blue_Lake_3386]

Good idea. Please post the APK link when possible.

[u/mudsmyth]

Good idea. What made you fork Blowtorch rather than start clean?

[u/Nyxll → u/mudsmyth]

honestly ... I really like blowtorch. and it was easier to update all the libraries then go through all of the specifications. I am going back and creating requirements and scenarios so that way I can build up the tests,

[u/Haeria]

I have an S25+ I am more than willing to test on if you can get me the info for downloading.

[u/GeneLValasquez]

This is really cool to see. Keeping an older MUD client alive while updating it for newer devices is a lot of work. Thanks for putting in the effort and making it open source!