Jump to content

Voldemmort

Members
  • Posts

    157
  • Joined

  • Last visited

    Never
  • Donations

    0.00 GBP 

Everything posted by Voldemmort

  1. Thanks for the patch, I'll test it tomorrow. Do you know how to implement the max time for each BG? For example the max time in Blizz to win WG is 30 min.
  2. I have an account at offi, but not enought lvl to test that out, but I'm pretty sure it is not Client Fault, cause if it was client fault, the client would crash too when having or trying to use more than 1 unique equip item, and this bug has some time on the server. I'll ask a friend to test that out and see if it is or not client bug.
  3. The bug is that you got Client Crash, instead of an error or advice in-game, the problem is that I dont know what is exactly blizzlike the error you have to get . Maybe something like "You can´t equip more than 3 Jeweller Gems"?
  4. Yeah I suggest adding the wowhead powered tooltips, many users doesnt know how to enable tooltips with GreaseMonkey, and it will ad some users friendly front end to the forum for all the links related to wowhead, and it is very easy to implement.
  5. Rev: 9729 When you try to equip 4+ Gems of any jeweller gem you get a client crash, instead of receiving an error, you socket correctly the first 3 Gems, and when you going to try to socket the next gem client crash with Error #132: Fatal Exception ACCESS_VIOLATION. For example try to equip 4 http://www.wowhead.com/item=36767 and you get client crash. Or equip 3 http://www.wowhead.com/item=36767 + 1 http://www.wowhead.com/item=36766 and again client crash. I know you must use only 3 Jeweller gems but to properly report the bug
  6. Yeah I just realize it was missing the apt-get update ty
  7. I just install Debian. Already modify the sources.list and when I try to do the command > apt-get install mysql-server-5.1 It says there unable to find mysql-server-5.1 packetor something like that
  8. It has something to do with the battleground_template for the arenas that has min max team players of 0/2, just change the 0 with a 1 and they will work like before (I'm not sure of the 5v5 but the 2v2 and 3v3 will work)
  9. It was the DBM Add0n -.-, thanks for the info @cyrex: yeah I know my drawing skills are over 450, the best over the world
  10. Ok I start downloading the Debian netinst amd64 version, it is the smalles and will not install unnecesary packets, just install what I need it to install. http://www.debian.org/distrib/netinst Any recomendations would be great
  11. I'm not good working at *nix OS, I'll start working on a Virtual Box in my machine to start developing at it and to know what I have to do. What *nix system do you recomend me to start with? Thanks in advance for your suggestions =)
  12. That script is for *nix and I'm using Win Server 2008 Any other ideas please?
  13. Hello. I recently realize that the defaults configs for MySQL Server isnt as good as they should be. so I start configuring here and there with some guides here in the forum and with Google, but I guess it is not as good configured as it should be. My Current Dedicated Machine is Windows Server Standard 2008 64 Bit OS, with 12 Gb Ram, Core i7 920 @ 2.67 Ghz. Can someone help me telling what are the best configs for my machine? with my current configurations it is using 4,866,972 K. Here is the configs I'm currently using. [client] port=3306 [mysql] default-character-set=utf8 [mysqld] # The TCP/IP Port the MySQL Server will listen on port=3306 max_allowed_packet = 256M #Path to installation directory. All paths are usually resolved relative to this. basedir="C:/Program Files/MySQL/MySQL Server 5.1/" #Path to the database root datadir="C:/ProgramData/MySQL/MySQL Server 5.1/Data/" # The default character set that will be used when a new schema or table is # created and no character set is defined default-character-set=utf8 # The default storage engine that will be used when create new tables when default-storage-engine=INNODB # Set the SQL mode to strict sql-mode="STRICT_TRANS_TABLES,NO_AUTO_CREATE_USER,NO_ENGINE_SUBSTITUTION" # The maximum amount of concurrent sessions the MySQL server will # allow. One of these connections will be reserved for a user with # SUPER privileges to allow the administrator to login even if the # connection limit has been reached. max_connections=100 # Query cache is used to cache SELECT results and later return them # without actual executing the same query once again. Having the query # cache enabled may result in significant speed improvements, if your # have a lot of identical queries and rarely changing tables. See the # "Qcache_lowmem_prunes" status variable to check if the current value # is high enough for your load. # Note: In case your tables change very often or if your queries are # textually different every time, the query cache may result in a # slowdown instead of a performance improvement. query_cache_size=367M # The number of open tables for all threads. Increasing this value # increases the number of file descriptors that mysqld requires. # Therefore you have to make sure to set the amount of open files # allowed to at least 4096 in the variable "open-files-limit" in # section [mysqld_safe] table_cache=1024 # Maximum size for internal (in-memory) temporary tables. If a table # grows larger than this value, it is automatically converted to disk # based table This limitation is for a single table. There can be many # of them. tmp_table_size=369M # How many threads we should keep in a cache for reuse. When a client # disconnects, the client's threads are put in the cache if there aren't # more than thread_cache_size threads from before. This greatly reduces # the amount of thread creations needed if you have a lot of new # connections. (Normally this doesn't give a notable performance # improvement if you have a good thread implementation.) thread_cache_size=8 #*** MyISAM Specific options # The maximum size of the temporary file MySQL is allowed to use while # recreating the index (during REPAIR, ALTER TABLE or LOAD DATA INFILE. # If the file-size would be bigger than this, the index will be created # through the key cache (which is slower). myisam_max_sort_file_size=100G # If the temporary file used for fast index creation would be bigger # than using the key cache by the amount specified here, then prefer the # key cache method. This is mainly used to force long character keys in # large tables to use the slower key cache method to create the index. myisam_sort_buffer_size=738M # Size of the Key Buffer, used to cache index blocks for MyISAM tables. # Do not set it larger than 30% of your available memory, as some memory # is also required by the OS to cache rows. Even if you're not using # MyISAM tables, you should still set it to 8-64M as it will also be # used for internal temporary disk tables. key_buffer_size=1024M # Size of the buffer used for doing full table scans of MyISAM tables. # Allocated per thread, if a full scan is needed. read_buffer_size=1024K read_rnd_buffer_size=1024K # This buffer is allocated when MySQL needs to rebuild the index in # REPAIR, OPTIMZE, ALTER table statements as well as in LOAD DATA INFILE # into an empty table. It is allocated per thread so be careful with # large settings. sort_buffer_size=1024K #*** INNODB Specific options *** # Use this option if you have a MySQL server with InnoDB support enabled # but you do not plan to use it. This will save memory and disk space # and speed up some things. #skip-innodb # Additional memory pool that is used by InnoDB to store metadata # information. If InnoDB requires more memory for this purpose it will # start to allocate it from the OS. As this is fast enough on most # recent operating systems, you normally do not need to change this # value. SHOW INNODB STATUS will display the current amount used. innodb_additional_mem_pool_size=32M # If set to 1, InnoDB will flush (fsync) the transaction logs to the # disk at each commit, which offers full ACID behavior. If you are # willing to compromise this safety, and you are running small # transactions, you may set this to 0 or 2 to reduce disk I/O to the # logs. Value 0 means that the log is only written to the log file and # the log file flushed to disk approximately once per second. Value 2 # means the log is written to the log file at each commit, but the log # file is only flushed to disk approximately once per second. innodb_flush_log_at_trx_commit=2 # The size of the buffer InnoDB uses for buffering log data. As soon as # it is full, InnoDB will have to flush it to disk. As it is flushed # once per second anyway, it does not make sense to have it very large # (even with long transactions). innodb_log_buffer_size=16M # InnoDB, unlike MyISAM, uses a buffer pool to cache both indexes and # row data. The bigger you set this the less disk I/O is needed to # access data in tables. On a dedicated database server you may set this # parameter up to 80% of the machine physical memory size. Do not set it # too large, though, because competition of the physical memory may # cause paging in the operating system. Note that on 32bit systems you # might be limited to 2-3.5G of user level memory per process, so do not # set it too high. innodb_buffer_pool_size=6G # Size of each log file in a log group. You should set the combined size # of log files to about 25%-100% of your buffer pool size to avoid # unneeded buffer pool flush activity on log file overwrite. However, # note that a larger logfile size will increase the time needed for the # recovery process. innodb_log_file_size=124M # Number of threads allowed inside the InnoDB kernel. The optimal value # depends highly on the application, hardware as well as the OS # scheduler properties. A too high value may lead to thread thrashing. innodb_thread_concurrency=8
  14. MaNGOS Rev: 9725 Hello, I have been having this problem for some time now. When I want to activate any command on me or for example I want to give an item to a player, and another player walk near me, instead of giving the item to the first player (and the player i have selected) I give the item to the second player, the one that walk near me. Here is an example, I have player 1 and player 2 near me, I have player 1 Selected and I'm closer to player 1, when I'm about to do ".item 9999" the player 2 walk near me, and instead of giving the item to player 1, I give the item to player 2. A pic to explain http://img406.imageshack.us/img406/8149/commandsbug.png The same keeps happening with any command in game.
  15. Confirmed too in Rev 9725. Tried to buy http://www.wowhead.com/item=10648 from some vendors and unable to buy it from any of those.
  16. Ok then I dont understand why it was working before. Could you please tell us what are the right values for that Arenas?
  17. I haven't touch anything from my BD and if it was working some Revs back and in latest rev it stop working, it is clear not a DB problem, the min and max team for Arenas are 0/2, so I have no idea of what should I modify in there.
  18. Can someone confirm the Arena Bug??
  19. I'm getting that error too, and I guess it has something to do with Arenas cause at this moment in Rev: 9725 players are unable to do any arena, when they try to enter they get an error that you need to be higher level to enter and they are all 80. This is the error I'm getting in the console when a player try to get into Arena. ERROR:Battleground: template bg (all arenas) not found And this is the error I got in the startup console. ERROR:Table `battleground_template` for id 5 have wrong min/max players per team settings. BG not created. ERROR:Table `battleground_template` for id 6 have wrong min/max players per team settings. BG not created. ERROR:Table `battleground_template` for id 8 have wrong min/max players per team settings. BG not created. ERROR:Table `battleground_template` for id 32 have wrong min/max players per team settings. BG not created.
  20. Rev: [9723] DB: YTDB I update to rev 9723 from 9709 and I'm unable to see any player from other faction, and also have problems with BG System. I revert again to Rev 9709 and it worked.
  21. Also for example you take one eternal fire, disarm it and rearm and you take 2, and you can keep exploiting that.
  22. Testers told me that when they try to create for example http://www.wowhead.com/item=38425 with leatherworking, they are now creating 2 items instead of only 1, and also with some Alchemist spells and so on. Other items like http://www.wowhead.com/item=43565
  23. I use Win Server 2008 x64 Bit Edition.
×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue. Privacy Policy Terms of Use