05-07 Shinigami
Added : flag VENDOR_SEND_AOS_TOOLTIP in
uo::SendBuyWindow( character, container, vendor, items, flags := 0 )
uo::SendSellWindow( character, vendor, i1, i2, i3, flags := 0 )
to send Item Description using AoS Tooltips in any case (this will correct problems
with Item Descriptions in newer Clients, but maybe freeze ancient Clients...).
05-04 Austin
Added : LISTEX_FLAG_CONCEALED support for ListMobilesNearLocationEX()
04-11 MuadDib
Change: Starting Gold will no longer be newbied (blessed). Can still be set newbied if you choose in
the create scripts for new characters.
04-09 Shinigami
Added : uoconvert.cfg element option added, TileOptions, in the following form:
TileOptions
{
ShowRoofAndPlatformWarning 1
}
it's a flag and defaults to 1 (shows a Warning if you use both Flags in same Tile).
04-05 MuadDib
Changed: Added servspecopt.cfg flag SingleCombat. This is a 0/1 flag for allowing players to attack
themselves. 0 will disable it (default). Per request.
Fixed: Crash involving invalid serial data sent with Target Cursor from client.
Fixed: Bug blocking non-harmful targeting of Players in NoCombat zones.
Fixed: Optimized NoCombat Target check.
03-19 MuadDib
Fixed: Will now correctly send AOS Tooltips if features are combined with 0x20 in the
UOFeatureEnable setting in servspecopt.cfg file.
03-18 MuadDib
Added: Servspecopt.cfg entry StartingGold=#. This will default to 100 gold. However, it can be
used to override the core's initial starting gold amount to this setting. Enjoy.
StartingGold=# feature DOES accept 0 to disable the creation of starting gold, unlike discussed before. Starting gold is also no longer newbied so it will combine with normal piles of gold. If you wish it to remain newbied, just handle in the create script for characters.
05-07 Shinigami
Added : flag VENDOR_SEND_AOS_TOOLTIP in
uo::SendBuyWindow( character, container, vendor, items, flags := 0 )
uo::SendSellWindow( character, vendor, i1, i2, i3, flags := 0 )
to send Item Description using AoS Tooltips in any case (this will correct problems
with Item Descriptions in newer Clients, but maybe freeze ancient Clients...).
and the modified uo.em u have to recompile all your scripts... so, just do it!
Just a suggestion for when you recompile. It is always good practice in my experience, to delete all ecl files before recompiling, and to save ecompile results to a text file so you can search it to make sure there was no compiling errors (thus, causing an ecl to not be generated). You can do this by adding the following to the end of the ecompile command.
Yes Maud. I agree with both your observations. I have found that eCompile will sometimes erroneously assume that a file is up to date even if it is from a previous POL version.
as said: try to understand that it is not needed to use a special slackware build on a slackware linux distro. in normal case u can use every build on your slackware linux DISTRO... there are tons of linux DISTROs available. all of'em use "same" linux kernel and a lot of additional tools. this set it called DISTRO. and one of'em is slackware.
if u don't understand this (that u can use the gentoo build on your slackware), go 2 buy a book like "linux 4 dummies"...