heRO-Server Forum

(for the tl;dr version, skip to the part in blue)
So when I came back to heRO I noticed all these wonderful changes and improvements that have happened during my absence, not the least of which is the @whosells/@ws feature.

However, I noticed that some items don't show up when I check them with @ws, with a notable example being Black Leather Boots. The @ws tells me that no one is selling BLBs, but that is a lie!

Edit: So, when this happens, as Zaratus pointed out, the best thing to do is use the item's 4-digit ID # which can be found by typing "@ii black leather boots," "ii orlean" and so on.

For example, here is a little list of items that go by different names with the @ws command. Feel free to post @ws names and IDs too!

@ws clarification list:

Issue: @ws Black Leather Boots always says "Nobody is selling that right now," even when people are selling it. Solution: use "@ws 2425"

Issue: @ws Orlean's Plate says "An item with that name can not be found." Solution: Type "@ws Orleans' Server" and it works.

Issue: @ws Antique Firelock Card says "An item with that name can not be found." Solution: Type "@ws Firelock Soldier Card" and it works.

(I will update this list as more correct names/IDs are found.)

Just use @ws ID to fix all those problems. You get the ID via RMS or @ii Name.

It's no @whosell problem, it's a problem with how items are named in RO and in the database itself.

Only @ws Bug I see is that there show crosses up on the map if you're on the wrong map in completely random spaces. Like I was checking for an item in Pront like forever near the cross till I saw that it was sold in Payon.

Zaratus Wrote:till I saw that it was sold in Payon.

Also, learn to read.

Zaratus Wrote:Just use @ws ID to fix all those problems. You get the ID via RMS or @ii Name.

It's no @whosell problem, it's a problem with how items are named in RO and in the database itself.

Only @ws Bug I see is that there show crosses up on the map if you're on the wrong map in completely random spaces. Like I was checking for an item in Pront like forever near the cross till I saw that it was sold in Payon.

Good advice, but this still doesn't fix the issue with BLBs. I think I saw this same issue with other items besides BLBs where it says no one is selling the item when people are actually selling it, but I'll have to do some testing later because I can't remember what they were.

Also, it can still be useful to make a list of items that use a different name for @ws than the name that shows up in inventories, so maybe it can be fixed someday.

Yeah, it just takes a simple @ii to figure it out, but since there are noobs out there that just give up after they @ws the first time with the wrong name and don't know how to @ii, the economy is being denied the money of said noobs! I want that noobmoney!

My @ws for BLBs works just fine.

Maybe you picked the wrong (aka slotted) ID, but only unslotted are sold?

Edit: Oh, it works for BLBs with the right ID number, I just saw the slotted one. I guess when you @ws with the name just assumes they're slotted. Silly @ws, slotted are for kids!

Anyway, I know I'm going to forget that ID number and have to @ii it a bunch. Laziness thwarted again

The issue is that the database names are kinda fucked up. Just use the IDs and it works fine.

Black_Leather_Boots just works fine.

Yeah you must use the item ID and not by name, because kRO/iRO uses different names in the databases (ice_heart vs glacial heart). Whosells is pretty flawless but you have to use @ii to find the item ID first.

Indeed.
These aren't bugs.
As the command searches for items via their name in the database (from which it obviously reads), then it needs to be supplied with the exact names in the database.

Recoding it to accept all the names that players regularly call each item would be near impossible.

GM-Circe Wrote:Indeed.
These aren't bugs.
As the command searches for items via their name in the database (from which it obviously reads), then it needs to be supplied with the exact names in the database.

Recoding it to accept all the names that players regularly call each item would be near impossible.

Ah, I see. Well, it's still a great command so that's ok. Changed my original post accordingly