Hmmm where do I begin.
Using distro 095 and having that issue with items in buy/sell windows being named their graphic name rather then their itemdesc name. What is the fix for this in 095? I know this is an issue with 096. I tried UOFeatureEnable=0x20 in servspecopt.cfg but I think that caused more problems (all spells in spellbook were gone, tooltips did NOT work nor did the basic clicking on an item to get it's name work) ... didn't fix anything.
Currently I'm using the .aos script to set AOS on my account. I'd like to "hardwire" for server to send out to the client. On one post from oldngrey, he said something about "UOExpansion set to acctref.set_uo_expansion("AOS") in the login script" ... not sure what the login script is. I know I don't have one... unless I have to make one.
Onto the client side. My client reads "UO Version 5.0.3 (patch 67)" on the login screen, yet my vercfg.cfg reads "current version 2D Client: 4.0.0p". Not sure if that's an issue.
Second and possibly a somewhat related question -
Are tooltips possible at all with 095? Not that I care too much. I will eventualy move on to 096/097 once I understand escript more... and or learn what in gods name packethooks are as in how they relate to everything. I know what packets are... just trying to understand the whole packethook feature as a whole I guess. Maybe I need to know what hooks are first. hehehe
Anyway, thanks much!!!!!
Buy / Sell window issue ... tooltips ... stuff like that...
I think in order to use UOFeatureEnable 0x20 you'll have to also use the account.set_uo_expansion("AOS") for the spellbook to work which doesnt exist in 095. The issue with buy/sell windows has also only been fixed in 096 with the addition of the flag VENDOR_SEND_AOS_TOOLTIP in the SendBuyWindow/SendSellWindow commands and the flag doesnt require any UOFeatureEnable.
So basically, its probably permanently broken in 095 due to it being out of date.
So basically, its probably permanently broken in 095 due to it being out of date.
Ouch... so I'm guessing the only way to avoid the limitation is to "patch" a 2.0 client and use it with the shard? Must be, because all pol095 shards I've been on use custom clients.. and I've never noticed this issue with them. So I'm guessing with an old client I wont have access to any of the newer weapons/monsters as well? If I try to create a giant beetle I'll probably get a green llama named "a giant beetle" and things along those lines. I love that.
So what about all that mega cliloc stuff? What's that all about? Only 096? Wait.. I still don't know what packethooks are...
Yesterday I actually downloaded pol096 (via the SVN option, which might I say is awesome)... compiled all the available scripts for it and actually got it running!! However... there are no NPC's and or Monster spawns yet... as of right now, is this normal? I understand it's not an official distro yet... just wondering. I loved how 095 was somewhat populated out of the box.
So what about all that mega cliloc stuff? What's that all about? Only 096? Wait.. I still don't know what packethooks are...
Yesterday I actually downloaded pol096 (via the SVN option, which might I say is awesome)... compiled all the available scripts for it and actually got it running!! However... there are no NPC's and or Monster spawns yet... as of right now, is this normal? I understand it's not an official distro yet... just wondering. I loved how 095 was somewhat populated out of the box.
well, the distro is unfinished as far as I know for 097. The 096 distro was never finished and just pushed up to 097 instead. To get the buy/sell window running correctly on newer clients, you only need to add the flag to every instance of those 2 commands and nothing more. Note also, that flag will crash or freeze anything before 4.x.
Mega Cliloc errors are problems with your cliloc files. Either they're not updated correctly or they were modified the wrong way. Clilocs store almost all text on OSI gumps and messages client side so they only send codes instead of the entire text message to the client.
You can use 4.x clients which will give you stuff up to AOS without the buy/sell window problems. My site is old and outdated but it still has those clients. Just dont use the login.cfg from the zip otherwise you'll be logging into my shard
(keeps hotlinking out) www.cwo333.com/clients
Mega Cliloc errors are problems with your cliloc files. Either they're not updated correctly or they were modified the wrong way. Clilocs store almost all text on OSI gumps and messages client side so they only send codes instead of the entire text message to the client.
You can use 4.x clients which will give you stuff up to AOS without the buy/sell window problems. My site is old and outdated but it still has those clients. Just dont use the login.cfg from the zip otherwise you'll be logging into my shard
(keeps hotlinking out) www.cwo333.com/clientsAre you refering to your AoS Guide and scripts? I have that. Installed, compiled and used it even though my client is 5.x it wasn't displaying any of the newer graphics. I don't know what was wrong but the .aos script worked for me however it did not fix the BS window thing (pun definately intended) because again my client is 5.x. But it's a great package thanks!
Which 4.x version should I use? I downloaded 4.0.3c ... which I'm assuming is the latest 4.x version and not an earlier one as you say?
My asking about mega cliloc was in reference to Shinigami's post where he stated, "u'll not have this side effect, if u just send mega cliloc for all "transferable" items in front of opening B/S Window." I'm just wondering what a "mega cliloc" is. CWO you said it's some kind of error so now I'm totally lost...
Oh and btw thanks CWO for that link. This client will no doubt help.
Thanks!!
Which 4.x version should I use? I downloaded 4.0.3c ... which I'm assuming is the latest 4.x version and not an earlier one as you say?
My asking about mega cliloc was in reference to Shinigami's post where he stated, "u'll not have this side effect, if u just send mega cliloc for all "transferable" items in front of opening B/S Window." I'm just wondering what a "mega cliloc" is. CWO you said it's some kind of error so now I'm totally lost...
Oh and btw thanks CWO for that link. This client will no doubt help.
Thanks!!
Well since I'm formerly and I guess... still the client tech for my shard mostly when I hear of mega cliloc, its about an error.
I explained though that mega cliloc is your cliloc.*** files. Basically theres cliloc files for quite a few languages in your path. Its completely used for text on the client side. Almost everything from OSI gumps to vendor sayings, to system messages can be sent to use a cliloc instead of sending the whole message which cuts down majorly on bandwidth usage.
Random Example:
Message:
You find the scroll, but can't pick it up because your pack is too full. Come back when you have more room in your pack.
Cliloc number:
1049146
All OSI does is send the number and the client displays all of the text. But the other major advantage is if the client determines what language to display too. So if you have a German speaking person for example on the shard who has German set as his language, the client will read number 1049146 from the cliloc.deu to get the german form of that text and display it.
I explained though that mega cliloc is your cliloc.*** files. Basically theres cliloc files for quite a few languages in your path. Its completely used for text on the client side. Almost everything from OSI gumps to vendor sayings, to system messages can be sent to use a cliloc instead of sending the whole message which cuts down majorly on bandwidth usage.
Random Example:
Message:
You find the scroll, but can't pick it up because your pack is too full. Come back when you have more room in your pack.
Cliloc number:
1049146
All OSI does is send the number and the client displays all of the text. But the other major advantage is if the client determines what language to display too. So if you have a German speaking person for example on the shard who has German set as his language, the client will read number 1049146 from the cliloc.deu to get the german form of that text and display it.