Leaderboard

just change the catalogue effect then. *searchstores <uses>,<effect>; Invokes the store search window, which allows to search for both vending and buying stores. Parameter uses indicates, how many searches can be started, before the window has to be reopened. Effect value affects, what happens, when a result item is double-clicked and can be one of the following: 0 = Shows the store's position on the mini-map and highlights the shop sign with yellow color, when the store is on same map as the invoking player. 1 = Directly opens the shop, regardless of distance. Example: // Item Universal_Catalog_Gold (10 uses, effect: open shop) searchstores 10,1;

what is the merit of still using this command when we already have better option? https://divine-pride.net/database/search?q=Catalogue

MO_EXTREMITYFIST,1,3,-60 try this.

L1nkZ, first of all, thank you very much for your hard work on this! I 've been willing to use SSO for a while and I will finally do that inspired by your patcher! I am not sure how your priority list is atm, but I'd like to recommend one thing I consider vital and still makes me miss thor patcher (not sure, though, how hard it is to implement: the hability to match the CRC of (at least) the ragnarok executable and if they dont match, to re-download it. in thor main.ini config file: [Patch] //use CheckSum tool, hash for client & patcher // used to make sure exe is up to date // (leave empty to disable this feature) ClientSum= PatcherSum= //This is compressed file for patcher & client update // To make these work, ClientSum and/or PatcherSum can't be empty // Note: these files should put same place as patch file (file_url in internal config) //Relative address, not FULL URL! ClientPath= PatcherPath= I find this very useful to avoid people from connecting using older clients. I use this along with the login-server hash control: // Client MD5 hashes // The client with the specified hash can be used to log in by players with // a group_id equal to or greater than the given value. // If you specify 'disabled' as hash, players with a group_id greater than or // equal to the given value will be able to log in regardless of hash (and even // if their client does not send a hash at all.) // Format: group_id, hash // Note: see 'doc/md5_hashcheck.txt' for more details. client_hash: 0, xxxxx and that is a perfect combo to force people to play whe the latest client and also to do that in a very user-friendly way. again, than you very much for your hard work and for sharing this with us! Best,