No Input?, Can't use Savitar at all now. Options

[Ellis1138]

This was odd. I downloaded 1.3b7, started it up and the window came up with a white bottom of the screen (where you type text in). I tried a few times, and still no good. Then, I attempted to use much older Savitar versions and it still does that. I can't get Savitar to let me into any worlds.

Something must have happened between last night's use of 1.3pre-2b7 and 1.3b7.

[Stormy]

I'm having the same problem, as well as ansi still not working and whatever world preferences I set (and save) getting reset. I've even tried deleting world files and starting from scratch. Still nothing.

[Guest_cybern8r_*]

I'm having the same problem. I opened up 1.2.4, realised I wanted 1.3.7b instead, loaded that up, and got that problem with the input window not loading or something. It didn't crash, so there's no crash log I can post.

[Ellis1138]

I got an email back from Jay, which began with 'Eek', so I think there's some kind of echo trouble.

I went back to using 1.1.4, which is doing fine. All my OSX Savitar versions are totally shot. He says he'll try to put out 1.3b8 as soon as he can. I sent him the stuff he asked for, so I hope it helps.

[Guest_cybern8r_*]

I just discovered something. Deleting the Savitar 2.0 Preferences fixes the problem. But I SO don't want to do that. I have 130 triggers in my MUD(I backed up the prefs before I deleted it from the Library folder). But I can't find any other way to fix it.

[Ellis1138]

I got an email back from Jay, which began with 'Eek', so I think there's some kind of echo trouble.

I went back to using 1.1.4, which is doing fine. All my OSX Savitar versions are totally shot. He says he'll try to put out 1.3b8 as soon as he can. I sent him the stuff he asked for, so I hope it helps.

[Ellis1138]

I think what you can do is grab your prefs in a text file (they should be readable). Save that as something else, somewhere else. Then, when you re-start Savitar from scratch, get the new Prefs 2.0 and add in all the stuff that says TRIGGER and WORLD. It won't be easy, and I can't guarantee it'll work. :/

[jay]

This bug is fixed in 1.3b8, which I just released moments ago.

You may have to set-up your world settings again, but in 1.3b8, they will properly save (and subsequently load).

Real sorry about this bug, I didn't catch it because I don't save my worlds in the World Picker. I save them as documents. When I test, I assume people are saving worlds out as documents too.

When I originally designed the World Picker, I didn't envision that people would use it as their regular way for saving worlds. I see I may want to do more with the World Picker's design in 1.4+, perhaps?

/jay

[Day]

You might, but I, for one, don't use it except in setting up new worlds. I have core documents that I've saved out and loading those up seems best to me... Especially with the addition of the Open Recent... menu it just seems much easier.


->Day<-
-----------------------
"y r u a h8r, day?"
-Aili @ Elendor

[Ellis1138]

It seems to be back to working in 1.3b8. Thanks

[Guest_cybern8r_*]

Okay, the bug is fixed. Nice work, jay.

[cooner]

I just had this same problem. Came here to post about it, but I see it's already been addressed, so I'll grab 1.3b8 in a moment.

As a bit of advice to folks: As a long-time user of Savitar (and no offense, Jay) I've gotten into the habit of keeping a backup copy of both my Savitar Prefs and License files elsewhere on my harddrive, and on a backup disk. When this input problem came up, first thing I did was trashed the Prefs and License files, replaced them with copies of the backed up files, and everything was right as rain. I highly recommend backing up those files.

And Jay ... yeah, sorry, I know you expect most folks to save World Documents, but personally I don't prefer the clutter of a dozen little documents for every muck and character I use ... so I'm one of those that just keeps everything saved in the World Picker. Sorry.