 |
jed
Adept
Joined: 18 Dec 2005
Posts: 246
|
 Posted: Thu Jan 29, 2009 11:46 pm
[3.03a] SQL login Error
|
I was playin my mud yesterday when I logged out, then opened cmud again and I get this error
Then my main session window doesn't connect to my mud. I can get into cmud and modify my settings and such, but then I get an access violation error and cmud crashes. Does this look like it is something wrong with my settings, or with my maps, or sessions???? Any clues? |
|
|
|
|
jed
Adept
Joined: 18 Dec 2005
Posts: 246
|
Posted: Thu Jan 29, 2009 11:52 pm
|
I just created a new session, then opened the map I normally use, and got the error again, so I'm guessing it has something to do with the map.
|
|
|
|
|
Zugg
MASTER
Joined: 25 Sep 2000
Posts: 23379
Location: Colorado, USA
|
Posted: Fri Jan 30, 2009 5:40 pm
|
In your screen shot, it appears to be opening/creating the map for the Tells window, so it definitely seems related to your map. Try renaming your *.DBM map file and see if CMUD can load without the map.
|
|
|
|
|
jed
Adept
Joined: 18 Dec 2005
Posts: 246
|
Posted: Sat Jan 31, 2009 3:22 am
|
Well... First off, I got it working. I'm not quite sure what did it, although I can say I did have some issues. Zugg, why would it try to create a map for the tell window? and how do you know what window it will try to create the map "for" anyway? I cant seem to find a setting that says "open this map as part of the main sesson window" or similar. As far as the fix:
First, In my settings editor, I had two package tabs called all.... I couldn't figure out why. I still don't know why they were there, but turns out, one of them was my fox.pkg, except somehow the name of it had been changed to All, so it looked like there were two all tabs when one was actually the all tab, and the other was my fox package. Second, I deleted a bunch of old settings.Third, For some reason, I had a total of five script made windows, one for my main session window, and two each for chat, and two for quest chat even though I should have only had one. I wasn't (and I'm still not sure) sure why multiple ones were created, however I finally mustered the testicular fortitude to delete them. So I did. One of them was the tell window that zugg suggests may have been part of the problem. I then ran the script,and as expected a new window was made on the first use of the trigger.
Fourth, I disconnected from my map, created a new blank one, changed the name on the old one, then disconnected from the new one and reconnected to the old one. I really don't know what solved the problem. I still have old copies of the .pkg and .dbm files if it'd help sending them.
I should probably ask in a different thread, but on the subject of windows to open, I always use a trigger with a script of something like
to capture chat and send it to another window. Is this the best way of going about that process? Seems to me I read one post suggesting I create the window manually, then use a different command maybe #window to shove the chat text into it. It sounded like the benefit would be that CMUD wouldn't be tempted to create a new window by using this command (#window may be the wrong command... I searched the forums but couldn't find the thread I was looking for) but I'm not sure. Also this doesn't seem quite right, because #window can also be used to create a window.... |
|
|
|
|
Zugg
MASTER
Joined: 25 Sep 2000
Posts: 23379
Location: Colorado, USA
|
Posted: Mon Feb 02, 2009 5:59 pm
|
| Quote: |
| how do you know what window it will try to create the map "for" anyway? |
I guessed because the caption at the top of the map window says "Map for tell". It assigns the map to whatever window had the keyboard focus when you clicked the Map button initially. Or, when converting a 2.x map file, it might have done that if the map window was docked inside of the Tell window, or if an old version has somehow associated the map window with the tell window. There are lots of ways this could have happened in older versions.
The new mapper associates the map window with whatever MUD window is associated with the Location Object being tracked. If your Location Object is stored within the Tell window, then the map gets associated with that window. So in v3.x it's a very "indirect" sort of association. In the Settings Editor you can select View/Show/Locations to show the location objects to see exactly which window they are stored in.
My guess is that disconnecting the map and creating a new one is what cleared up the problem. But with all of the various duplicate windows and stuff, it certainly sounds like your package was pretty messed up from older versions.
Your capture/gag trigger is just fine...that's what most of mine look like. |
|
|
|
|
|
|
|
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
