Talisman problem

Results 1 to 5 of 5
  1. #1
    Member selocan is offline
    MemberRank
    Mar 2008 Join Date
    51Posts

    ! Talisman problem

    Hi everyone :)

    I just ran up into kinda interesting problem that I can't solve myself :)

    Some of talismans work, and some doesn't... well, actually they work, but they set a wrong prefix on item after success... so that's what i can't figure out..

    Prefix.txt, Prefix.dat
    Code:
    (prefix (index 135)(level 10)(sell 290)(str 20) (Int 20) (Wis 20) (Dex 20) (hp 1000) (mp 1000)  (hit 30) (attack 400 600) (magic 400 600) )
    (prefix (index 300)(level 3)(sell 0)(str 7) (Int 7) (Wis 7) (Dex 7) (hp 300) (mp 300) (attack 80 130) (magic 80 130)  (hit 5) )
    Inititem.txt
    Code:
    (item    (name 531)(Index 10000)(Image "item017")(class general charm)(code 3 5 12 0)(country 0 1 2)    (use 1)(plural 1)(buy 0)(sell 1500)    (specialty    ​(Changeprefix weapon 50 135 )))
    (item    (name 531)(Index 10009)(Image "item017")(class general charm)    (code 3 5 12 0)    (country 0 1 2)(use 1)(plural 1)(buy 0)(sell 1500)    (specialty    (Changeprefix weapon 50 300 )))
    Item 10000 (prefix 135) works fine, but
    Item 10009 (prefix 300) after success puts another talisman (prefix 44) -> (Dex 4)

    What I managed is that prefix 300 sticks on item after success until relog (although I only see 4 agility added), but stats are increased as it is pimped with prefix 300, but after relog it adds only 4 agi....

    Hope you understood my problem :)
    Any help would be appreciated, cheers!


  2. #2
    Banned Kallyanna is offline
    BannedRank
    Jul 2007 Join Date
    Spamzilla CrewLocation
    1,672Posts

    Re: Talisman problem

    I think 1) you need to double check that there is not another prefix 300 (It SHOULD give an error if there is server side) but if it hasnt been removed in the config.pk it will not kick an error, it will just roll the prefix back to the 1st prefix 300.... best way to explain it would be.. open messag-e.day and add a double key example (npcname key 1001 "bob the NPC" .....etc...etc and then below it do the same line copied but change the name (npcname key 1001 "big bobs beepers the NPC" .....etc...etc ... it will still show up with the first one :P

    If that isnt the issue you could also try double checking your Languagemap.. make sure they go WELL over 100009 - not sure why you are using such high values... I have run into probs in the past for example, an NPC's file name cannot be N1000_b1.gb the highest you can have is N999_b1.gb :P so its VERY important to find out the number limits you can go to before it starts causing problems.

  3. #3
    Account Upgraded | Title Enabled! blub95 is offline
    MemberRank
    Oct 2012 Join Date
    Germany :PLocation
    283Posts

    Re: Talisman problem

    max prefix is 255 if you go over 255 it start again with prefix 1.

  4. #4
    Member selocan is offline
    MemberRank
    Mar 2008 Join Date
    51Posts

    Re: Talisman problem

    Thank you, blub!
    Why the hell couldn't I figure that out myself huh? what an idiot :D

  5. #5
    Modeler / C++ Coder Matynator is offline
    DeveloperRank
    Feb 2008 Join Date
    NetherlandsLocation
    577Posts

    Re: Talisman problem

    Quote Originally Posted by blub95 View Post
    max prefix is 255 if you go over 255 it start again with prefix 1.
    +1 prefix in the mainserver is an unsigned char / BYTE :) 0 - 255 is the value range limits..



Advertisement