3rd job class item can not be worn

[Claod]

Hi everyone !

 

Sorry if i'm in the wrong section, It may not be a database issue ...

I've been searching for a long time today and I can't found a solution ....

 

When my character job is 4061 : it means I'm Warlock rebirth, right ? So it's trans 3rd job, right ? Maximum Base lvl 175, Maximum Job Lvl 60.

My Ribirth Warlock 175/60 try to wear diabolus Robe : "Cannot be worn".

 

Item_db :

2374,Diabolus_Robe,Diabolus Robe,4,20,,300,,57,,1,0x00098B1C,18,2,16,,55,1,0,{ bonus bMaxSP,150; bonus bMdef,5; bonus bHealPower,6; bonus bDelayRate,-10; },{},{}

0x00098B1C is for job restriction, right ?

It's hexadecimal sum ... In description it says that that robe can be worn by trans archer, mage, acolyte.

 

Then I saw this :

(S.) Novice (2^00): 0x00000001
Swordman (2^01): 0x00000002
Magician (2^02): 0x00000004
Archer (2^03): 0x00000008
Acolyte (2^04): 0x00000010
Merchant (2^05): 0x00000020
Thief (2^06): 0x00000040
Knight (2^07): 0x00000080
Priest (2^08): 0x00000100
Wizard (2^09): 0x00000200
Blacksmith (2^10): 0x00000400
Hunter (2^11): 0x00000800
Assassin (2^12): 0x00001000
Unused (2^13): 0x00002000
Crusader (2^14): 0x00004000
Monk (2^15): 0x00008000
Sage (2^16): 0x00010000
Rogue (2^17): 0x00020000
Alchemist (2^18): 0x00040000
Bard/Dancer (2^19): 0x00080000
Unused (2^20): 0x00100000
Taekwon (2^21): 0x00200000
Star Gladiator (2^22): 0x00400000
Soul Linker (2^23): 0x00800000
Gunslinger (2^24): 0x01000000
Ninja (2^25): 0x02000000
Gangsi (2^26): 0x04000000
Death Knight (2^27): 0x08000000
Dark Collector (2^28): 0x10000000
Kagerou/Oboro (2^29): 0x20000000

LOL ... x) Can you explain me where is the warlock here ? And show me the sum of the hexa values please because I don't understand.

How can you find this result  : 0x00098B1C  #WarlockIsMagicPoof

 

Refering to this :

16 + 2 = 18 so it means Transcendent classes and transcendent 3rd classes ?

Class: Equippable upper-types. Uses the following bitmasks:
     1: Normal classes (no Baby/Transcendent/Third classes)
     2: Transcendent classes (no Transcedent-Third classes)
     4: Baby classes (no Third-Baby classes)
     8: Third classes (no Transcedent-Third or Third-Baby classes)
    16: Transcedent-Third classes
    32: Third-Baby classes

If 98B1C means trans archer and upper jobs, trans mage and upper jobs, trans acolyte and upper jobs.

The result : Warlock should be able to wear it, right ? [i'm searching the headshot emot*]

 

 

 

By the way I tried this to debug :

 

in my C:\ServeRO\trunk\db\re\item_db.txt I changed the diabolus robe's line to this 

2374,Diabolus_Robe,Diabolus Robe,4,20,,300,,57,,1,0xFFFFFFFF,63,2,16,,55,1,0,{ bonus bMaxSP,150; bonus bMdef,5; bonus bHealPower,6; bonus bDelayRate,-10; },{},{}

And [ here comes the database ] in my item_db_re I did the same except for the hexa value, changed it to "4294967295" (It's the same but I converted the hexadecimal value).

 

0xFFFFFFFF means all jobs

63 is the sum of all

Everyone should be able to wear it now ...

 

After those changes I recompiled the server, refresh all, close the client etc ... Still cannot be worn.

 

 

 

So what ? 4061 is not transcendant job ?

 

Can you explain me please, where is the problem ? :/ And more important how to fix it ^^'

 

Thanks if you can teach me

 

 

EDIT: Wow super weird... I manually added exactly the same item : diabolus robe + banshee master card. And I can wear it... But the last Robe still can't be worn. x) what the ... Before the "can not be worn issue" I died. After that it was removed from equiped items, and un-wear-able ... Is this normal ?

 

Edit 2 : This is why, I closed the client while I died... During the equiped item process the packet was not received... and voila ... I broke this item.

Edited November 11, 2015 by Claod

[Haziel]

Couldn't understand because of the edits, but, your problem persists?

[FXFreitas]

Hi everyone !

 

Sorry if i'm in the wrong section, It may not be a database issue ...

I've been searching for a long time today and I can't found a solution ....

 

When my character job is 4061 : it means I'm Warlock rebirth, right ? So it's trans 3rd job, right ? Maximum Base lvl 175, Maximum Job Lvl 60.

My Ribirth Warlock 175/60 try to wear diabolus Robe : "Cannot be worn".

 

Item_db :

2374,Diabolus_Robe,Diabolus Robe,4,20,,300,,57,,1,0x00098B1C,18,2,16,,55,1,0,{ bonus bMaxSP,150; bonus bMdef,5; bonus bHealPower,6; bonus bDelayRate,-10; },{},{}

0x00098B1C is for job restriction, right ?

It's hexadecimal sum ... In description it says that that robe can be worn by trans archer, mage, acolyte.

 

Then I saw this :

(S.) Novice (2^00): 0x00000001
Swordman (2^01): 0x00000002
Magician (2^02): 0x00000004
Archer (2^03): 0x00000008
Acolyte (2^04): 0x00000010
Merchant (2^05): 0x00000020
Thief (2^06): 0x00000040
Knight (2^07): 0x00000080
Priest (2^08): 0x00000100
Wizard (2^09): 0x00000200
Blacksmith (2^10): 0x00000400
Hunter (2^11): 0x00000800
Assassin (2^12): 0x00001000
Unused (2^13): 0x00002000
Crusader (2^14): 0x00004000
Monk (2^15): 0x00008000
Sage (2^16): 0x00010000
Rogue (2^17): 0x00020000
Alchemist (2^18): 0x00040000
Bard/Dancer (2^19): 0x00080000
Unused (2^20): 0x00100000
Taekwon (2^21): 0x00200000
Star Gladiator (2^22): 0x00400000
Soul Linker (2^23): 0x00800000
Gunslinger (2^24): 0x01000000
Ninja (2^25): 0x02000000
Gangsi (2^26): 0x04000000
Death Knight (2^27): 0x08000000
Dark Collector (2^28): 0x10000000
Kagerou/Oboro (2^29): 0x20000000

LOL ... x) Can you explain me where is the warlock here ? And show me the sum of the hexa values please because I don't understand.

How can you find this result  : 0x00098B1C  #WarlockIsMagicPoof

 

Refering to this :

16 + 2 = 18 so it means Transcendent classes and transcendent 3rd classes ?

Class: Equippable upper-types. Uses the following bitmasks:
     1: Normal classes (no Baby/Transcendent/Third classes)
     2: Transcendent classes (no Transcedent-Third classes)
     4: Baby classes (no Third-Baby classes)
     8: Third classes (no Transcedent-Third or Third-Baby classes)
    16: Transcedent-Third classes
    32: Third-Baby classes

If 98B1C means trans archer and upper jobs, trans mage and upper jobs, trans acolyte and upper jobs.

The result : Warlock should be able to wear it, right ? [i'm searching the headshot emot*]

 

 

 

By the way I tried this to debug :

 

in my C:\ServeRO\trunk\db\re\item_db.txt I changed the diabolus robe's line to this 

2374,Diabolus_Robe,Diabolus Robe,4,20,,300,,57,,1,0xFFFFFFFF,63,2,16,,55,1,0,{ bonus bMaxSP,150; bonus bMdef,5; bonus bHealPower,6; bonus bDelayRate,-10; },{},{}

And [ here comes the database ] in my item_db_re I did the same except for the hexa value, changed it to "4294967295" (It's the same but I converted the hexadecimal value).

 

0xFFFFFFFF means all jobs

63 is the sum of all

Everyone should be able to wear it now ...

 

After those changes I recompiled the server, refresh all, close the client etc ... Still cannot be worn.

 

 

 

So what ? 4061 is not transcendant job ?

 

Can you explain me please, where is the problem ? :/ And more important how to fix it ^^'

 

Thanks if you can teach me

 

 

EDIT: Wow super weird... I manually added exactly the same item : diabolus robe + banshee master card. And I can wear it... But the last Robe still can't be worn. x) what the ... Before the "can not be worn issue" I died. After that it was removed from equiped items, and un-wear-able ... Is this normal ?

 

Edit 2 : This is why, I closed the client while I died... During the equiped item process the packet was not received... and voila ... I broke this item.

 

To show the third jobs in rms you need to click in "renewal" button.

 

Searching...

 

Everything looks fine... tested here and worked

Edited November 11, 2015 by FXFreitas

[Claod]

Hey ! excuse me by telling "Edit 2 : This is why, I closed the client while I died... During the equiped item process the packet was not received... and voila ... I broke this item."

I mean : the item was broken, (only this one was a problem). It was broken, and not repairable. I closed the client while I died... and it did something. I fixed the situation by puting the same item again from my DB, and this new one was working, I just trashed the older one. So now it's working, and no more problem. Couldn't reproduce the bug again...