-
Notifications
You must be signed in to change notification settings - Fork 772
Add F_MesItemInfo function to show item name with description link #2068
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
fb11920 to
29766ef
Compare
|
bump @Emistry , why you add item slot to the function ? |
hmm, I didnt modify anything to this PR? anyways, if you're asking for opinion, I find that showing the item slot of the item make more sense and accurate to display the item. RO has too many redundant item due to the different amount of item slots.
Previously, similar case only happen when the message in the
no idea, i never really paid any attention to this. If you asked me, all I need are just the item description to be displayed there in the popup. |
|
Also, can someone check with different clients? |
|
use |
|
you are right test in-game not sure when this happens |
|
I not sure is client using |
|
and |
29766ef to
bc9bbe1
Compare
|
script_commands.txt says the Navigation system was implemented on 20111010 ... tested with |
bc9bbe1 to
4ff2b67
Compare
|
Yes |
4ff2b67 to
0272f97
Compare
|
btw, how about adding the slot display too?
|
|
some time ago I was digging my old harddisk, I couldn't test this very old hexed client right now, this old client now throw me char info size mismatch maybe just do it, for the sake of 'old me' EDIT: interesting note, |
also fix OldGlastHeim ITEMLINK display incorrectly
0272f97 to
7b48fee
Compare
| If you're using client from 2013-01-30 onwards, you can also use <ITEMLINK> to show | ||
| the item's description. Gravity changed this into <ITEM> since 2015-07-29 onwards. | ||
|
|
||
| mes("Bring me an <ITEM>Apple<INFO>512</INFO></ITEM>."); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think this line shall be removed, since not every client version support the <ITEM> tag. It could be confusing.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
hard to define this, many members said its harder and harder to use older hex client
because client translation project always keep itself up to date with no backward compatibility
I have some older hexed client just simply because when I inactive, and active back
I always install newer stuffs, and the old stuffs just kept inside external harddisk
we should always encourage members to use latest client revision ... isn't it ?
and removing that line ... is just like hide this method from public
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
No, I mean we should encourage them to use the F_ItemMesInfo and not <ITEM> or <ITEMLINK>.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
my opinion is show them both methods ...
ok 1 vote for showing 1 method (Emistry)
1 vote for showing both methods (AnnieRuru)
any one else vote for showing 1 method or showing both ?
| if (.@itemname$ != "null") { | ||
| .@itemslot = getitemslots(.@item); | ||
| if (.@itemslot) | ||
| .@itemname$ = sprintf("%s [%d]", .@itemname$, .@itemslot); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
the equipment slot should check for item type is EQI_ARMOR / EQI_WEAPON or not.
If its not armor/weapon then it shall not show any postfix of equipment slot in the item name.
If the item were armor/weapon then it shall show the equipment slot even if its [0] slot.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I knew you going to say this, I have tested this in my getitemname2 function
all items are default to 0 slots
Def: Defense (int, defaults to 0)
Range: Attack Range (int, defaults to 0)
Slots: Slots (int, defaults to 0)
Job: { (defaults to all job)
All: true/false (boolean, defaults to false)
Novice: true/false (boolean, defaults to false)
Swordsman: true/false (boolean, defaults to false)
Magician: true/false (boolean, defaults to false)
and no, items with [0] slot doesn't show in-game
please test it,
and WHY the fuck I have to upload a screenshot every time ????
sigh...
OK I upload screenshots because you think it work your way but it doesn't work like that
prontera,155,185,5 script asdasdad 1_F_MARIA,{
getitem 1201, 1;
getitem 1203, 1;
mes(F_MesItemInfo(1201));
mes(F_MesItemInfo(1203));
close;
}



Pull Request Prelude
Issues addressed
too many members doesn't even know this exist
simply because it is not documented
Changes Proposed
Add
F_MesItemInfofunction to show item name with description linkAffected Branches
Tested with
Known Issues and TODO List
although unrelated, but my hexed client doesn't show the
www.google.comproperly