Best posts made by mudrammer

~appears in a puff of logic~

This is caused by the iOS 11 keyboard sending smart quotes. Here are a few things you can try:

• You could long-press on the quote and apostrophe keys on the keyboard and choose the simple apostrophe (') and quote (") characters.

• You could send smart quotes to the MUD by changing MUDRammer’s encoding in MUDRammer Settings -> Advanced -> Encoding to a unicode encoding like UTF-8. MUDRammer will now send those characters correctly, but if the MUD does not support unicode, the MUD still won’t recognize those characters. You should check with your MUD to be sure.

• You could always send simple quotes by disabling smart punctuation in iOS Settings -> General -> Keyboards -> Smart Punctuation OFF.

@theonceler said in iOS 11 and MudRammer:

I mean that when I use it on my iPad Pro in iOS 11 it will drop connection if I spend more than a few seconds switched out to any other app.

When MUDRammer transitions to background, it will attempt to stay alive as long as iOS will allow. This varies with your device's hardware, current memory pressure, and the demands of the currently foregrounded app(s) — games, videos, and web can be very demanding indeed, and the system will ruthlessly kill backgrounded apps as needed.

The system employs subtle and nuanced magic here, but because MUDRammer is open-source, you can see for yourself exactly what its socket library GCDAsyncSocket can (and cannot) do when enabling backgrounding.

Same goes for if I use it on my phone while connected to Wifi. It's more reliable if I turn Wifi off and just use an LTE connection.

https://www.xkcd.com/1865/

Guys, I'm talking real dollaridoos here. $2.99? $4.99? Even $7.99? Uh, yes sir. The sky is the limit. The app store sky, though. So like $7.99. I'm not about to pay Through the Ages or Twilight Struggle money here.

I experimented with MUDRammer pricing between $1 and $5 and saw no meaningful difference in sales. This too is subtle and nuanced magic, but it suggests the price was still too low.

MUDRammer was my personal side project in my spare time. I never did charge for MUDRammer what I believed it was worth.

Ahoy MUDbuds,

Some of you have played with MUDRammer — A Modern MUD Client for iPhone and iPad, my personal side project these last few years.

I wanted to share some exciting news: MUDRammer is now open-source!

Contributions are welcome and no pull request is too small.

And no, this is not the end for MUDRammer. Exciting times lie ahead!

~ J

@auspice MUDRammer has not been under development for some time now, unfortunately. MUDRammer will crash if you try to email your logs (egg on my face...) but it's still dutifully recording them! You can connect your device to iTunes and copy/edit/delete your MUDRammer logs: https://support.apple.com/en-us/HT201301

@WildBaboons MUDRammer has not been under active development for some time now, unfortunately. But I still get email, and I try to reply

~appears in a puff of logic~

There are 2 things going on in your screenshot:

• The big black space shouldn't show up when you have a bluetooth keybaord connected. Try enabling MUDRammer's Settings -> Advanced -> Bluetooth Keyboard option. This tells MUDRammer you have a hardware keyboard connected. After that's on, you can press the eject or show/hide keyboard key on your hardware keyboard to collapse the extra space.
• The extra bar at the bottom is the shortcut bar, a new feature in iOS 9. You can hide it by disabling “Shortcuts” under iOS Settings -> General -> Keyboard.

MUDRammer should definitely handle both of these scenarios much better than it is today. Egg on my face...

@meg You are absolutely right - the website is a 90s horror show. A real acid trip.

I hope you won't let that put you off entirely - there's lots of great in-game help (it's definitely more-recently updated too) and many helpful players.

@Roz I connected to Arx with the debugger attached. Arx does engage in TTYPE negotiations with the client, which seems at odds with Arx's own in-game help on the @color command that you posted above.

• Arx says DO TTYPE
• MUDRammer says TTYPE MUDRAMMER
• Arx says SEND TTYPE (per RFC 1091, if the server rejects a terminal type, the server can enumerate multiple ttypes in the client by requesting ttype again)
• MUDRammer says TTYPE XTERM
• Arx says SEND TTYPE
• MUDRammer says TTYPE ANSI
• Arx says SEND TTYPE
• MUDRammer says TTYPE ANSI (MUDRammer has exhausted its list of ttypes and signals this by repeating the last ttype a second time)

It appears that Arx rejected all of MUDRammer's ttypes and ended up with ANSI, either because it was the default or because it was the last one that MUDRammer sent.

So... is it a bug in MUDRammer or in Arx? Probably both? ¯\_(ツ)_/¯