-
Hail Guest! We're looking for Community Content Contribuitors to Stratics. If you would like to write articles, fan fiction, do guild or shard event recaps, it's simple. Find out how in this thread: Community Contributions
-
Greetings Guest, Having Login Issues? Check this thread!
-
Hail Guest!, Please take a moment to read this post reminding you all of the importance of Account Security.
-
Hail Guest! Please read the new announcement concerning the upcoming addition to Stratics. You can find the announcement Here!
B
Bill Gates OSD
Guest
AMEN! I don't think you can disable the 10 YEARS out-dated "Codex of Wisdom" but I'd sure like to NOT accidently hit the F1 key and have it pop up in the way!
I usually set the F1 key to "hiding". It's been a keybinding I've been using for years and years, and old habits die hard.
Sometimes I hit "log out" without hiding in my house first, but you can still use bound keys while the log out confirmation is up, so I quickly hide then click okay.
If I don't have the key bound, it brings up the codex of wisdom on top of the log out confirmation gump, and you then have to close the client fully, since you can't get to the log out confirmation, and can't close the codex which is blocking it.
I don't like the codex very much
Sometimes I hit "log out" without hiding in my house first, but you can still use bound keys while the log out confirmation is up, so I quickly hide then click okay.
If I don't have the key bound, it brings up the codex of wisdom on top of the log out confirmation gump, and you then have to close the client fully, since you can't get to the log out confirmation, and can't close the codex which is blocking it.
I don't like the codex very much
Basara
UO Forum Moderator
Moderator
Professional
Governor
Stratics Veteran
Stratics Legend
Wiki Moderator
UNLEASHED
Campaign Supporter
It's VERY easy to disable the codex of wisdom. I did it 8 years ago when I first started playing, even before I started using UOAssist.
Go into the UO (not UOAssist) macros. Define the F1 key as whatever you like (I did mine as saying "All follow me"). Apply. Close the macro gump, then reopen it. Click through your assigned macros to make sure your new meaning of F1 is the only one present (deleting any others).
and the Codex is gone from F1.
As long as you don't click the button to revert to defaults, you're good.
Also, look for the the box for passing the keystroke info to UO, in each UOA keybinding.
Usually, you DON'T want to pass the keybinding on, for anything not one of the basic 36 keys (A-Z, 0-9).
However, it's possible to create some nice double-macros (a combination of a UOA macro and a UO macro, running at the same time) this way, such as one to disarm and rearm in UOA, with a potion use timed (using delays in each) to occur between them.
Go into the UO (not UOAssist) macros. Define the F1 key as whatever you like (I did mine as saying "All follow me"). Apply. Close the macro gump, then reopen it. Click through your assigned macros to make sure your new meaning of F1 is the only one present (deleting any others).
and the Codex is gone from F1.
As long as you don't click the button to revert to defaults, you're good.
Also, look for the the box for passing the keystroke info to UO, in each UOA keybinding.
Usually, you DON'T want to pass the keybinding on, for anything not one of the basic 36 keys (A-Z, 0-9).
However, it's possible to create some nice double-macros (a combination of a UOA macro and a UO macro, running at the same time) this way, such as one to disarm and rearm in UOA, with a potion use timed (using delays in each) to occur between them.
Thx Basara, I'll do that... I hadn't tried lately because somewhere in the back of my mind - I seemed to remember that the "Codex" came up no matter what I tried. I probably didn't think to check on the "pass on" option.
