Beiträge von Fire.

    how we can fix it?

    You have to delete the value 97 from query


    Like this:


    85008 ¸íÀÎÀÇ ¾×¼¼¼­¸®(Àü¼³) Meisterband (maßgef.) 28 3 0 1 128 9216 0 1000000 0 0 0 0 0 0 0 0 0 97 20 0 0 0 0 0 0 0 0 0 0 -1 -1 -1 -1 -1 -1 100 0 0


    To:


    85008 ¸íÀÎÀÇ ¾×¼¼¼­¸®(Àü¼³) Meisterband (maßgef.) 28 3 0 1 128 9216 0 1000000 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 -1 -1 -1 -1 -1 -1 100 0 0

    Check the query of sash and remove the applytype 97, same as clientside.
    You are initializing this bonus but you don’t use it in your source

    You can fix easily your antiflag with a simple query


    UPDATE item_proto_new INNER JOIN item_proto_old
    ON item_proto_new.vnum = item_proto_old.vnum
    SET item_proto_new.antiflag = item_proto_old.antiflag


    Replace item_proto_new with the name of your item_proto and put a backup of your old item_proto and rename it likes item_proto_old and run the query ;)
    The query will copy all Antiflag of your old proto into the new

    Following this guide you will be able to change the collection time of the items


    Video:


    Bitte melden Sie sich an, um dieses Bild zu sehen.
    Bitte melden Sie sich an, um dieses Medienelement zu sehen.


    Code:


    Client Source /UserInterface/PythonPlayer.cpp



    Try to check your disk space and if you got some free memory.
    You can see the max connections values by putting in the command line this:

    Shell-Script
    1. show variables like "max_connections“


    Update your connections with this command:
    Keep in mind that increase of the number of connections will increase the amount of RAM required for MySQL to run.


    Shell-Script
    1. set global max_connections = 150;