Jump to content

Xenithar

getMaNGOS Staff
  • Posts

    1395
  • Joined

  • Last visited

  • Days Won

    3
  • Donations

    0.00 GBP 

Bug Comments posted by Xenithar

  1. DPS is cake. 1000 is 1sec, 500 is 0.5sec, 1500 is 1.5sec. I forget the column, but the DPS is in milliseconds.

    *EDIT*

    Also, if something is displayed many times (normally this would be mana), you have an invalid stat type in one of the ten stat type fields. The stats are NOT sequential. Hang on and I will list the stats for you.

    *UPDATE*

    Here's the list of base stats.

    [list]
    [*]Mana = 0
    [*]Health = 1
    [*]Agility = 3
    [*]Strength = 4
    [*]Intellect = 5
    [*]Spirit = 6
    [*]Stamina = 7
    [/list]

    ALso, there is MUCH more help in src/game/ItemPrototype.h for things including enchantments and triggers.

  2. The client level is "unsigned char", which ranges from 0 to 255, so yes 255 is the max. I would like for GM's to be able to do what they want. I would prefer the cap to stop normal players at the specified level, but if a GM does ".levelup ", whether on himself or a player, the server should abide by that decision. Along with that, it would require level stats up to 100 to be in the database even for Zero. I believe the cap in Draenor is 100, right? Either way we'd need to put in the data for all of the KNOWN levels.

  3. No, in Zero I do not remember crew. I will do an image search to confirm though. Remember, in BC/LK I know they buried a transport underground and this transport is where the players really were while onboard them. This allowed players and NPCs to remain in the correct locations after zoning.

    *UPDATE*

    I forgot, an awesome thing to do in LK was to get a DK to use Death Grip on you while on a boat or Zep right before zoning. When you spawned in, you would fly under the world and land safely on the "ghost ship". It was amusing as heck to me!

  4. I see that. I tried it and 8250dps daggers are, shall we say, OP? I must have been remembering information pertaining to LK. Still, if those items existed in vanilla, they SHOULD be in our DBC files. Peep was added in BC. Flying phoenix mount given to some kid dying of cancer. The Blizzard team had him out to their place and played with him all day. Gave him Peep and also some rad gear. Made me all blurry-eyed when I first read about it.

  5. Well it works like this. You can't create an item server-side which is not in the client. If the server says item 7000 is on a corpse and your DBC files do not have an entry for item 7000, it will either show up as a red question mark on a black background and be useless, or it won't show up at all. Antz or Reaper could probably explain this better than I can, but it boils down to things matching up on the client and server.

  6. These were in MaNGOS years back, along with Peep the phoenix and others. No clue why we don't have them now. In Zero, and One I believe, the items were tied to the area death spell and killed everything in a 30 yard radius. Somehow these items made it onto a live server so they changed it to kill the caster. In Zero it should kill everything in a 30 yard radius around the caster In Lich King it should be suicide. Not sure about BC, but I know at one point in BC it was the same as in vanilla, though they may have been changed prior to the final version of BC.

    *EDIT*

    Alex's Ring of Audacity and Alex's Text Beatdown Staff are in-game, along with the Ring of Critical Testing 2.

  7. I updated again last night and noticed something. The Eluna crash is gone, and I now get this.
    [code]
    Next game event check in 1200 seconds.
    server shutdown 10
    CLI command under processing...
    Server is shutting down in 10 Second(s).
    Command: server shutdown 10 [Account: 0 from Console]
    mangos>[Thread 0xb18efb70 (LWP 3095) exited]
    Network Thread Exitting
    Network Thread Exitting
    [Thread 0xb10eeb70 (LWP 3096) exited]
    [Thread 0xb08edb70 (LWP 3097) exited]
    [Thread 0xb20f0b70 (LWP 3094) exited]
    [Thread 0xb6e4cb70 (LWP 3087) exited]
    [Thread 0xb765db70 (LWP 3084) exited]
    Halting process...
    [Thread 0xb664bb70 (LWP 3090) exited]

    Program received signal SIGPIPE, Broken pipe.
    0xb7fe1424 in __kernel_vsyscall ()
    (gdb) backtrace
    #0 0xb7fe1424 in __kernel_vsyscall ()
    #1 0xb77d32eb in write () from /lib/i386-linux-gnu/i686/cmov/libpthread.so.0
    #2 0xb7b7bf0d in vio_write ()
    from /usr/lib/i386-linux-gnu/libmysqlclient.so.18
    #3 0xb7b6a06e in net_real_write ()
    from /usr/lib/i386-linux-gnu/libmysqlclient.so.18
    #4 0xb7b6a2c8 in net_flush ()
    from /usr/lib/i386-linux-gnu/libmysqlclient.so.18
    #5 0xb7b6a5e0 in net_write_command ()
    from /usr/lib/i386-linux-gnu/libmysqlclient.so.18
    #6 0xb7b675f8 in cli_advanced_command ()
    from /usr/lib/i386-linux-gnu/libmysqlclient.so.18
    #7 0xb7b643a1 in mysql_close ()
    from /usr/lib/i386-linux-gnu/libmysqlclient.so.18
    #8 0x08989217 in MySQLConnection::~MySQLConnection (this=0xbd1c910,
    __in_chrg=)
    at /home/---/zero/src/server/src/shared/Database/DatabaseMysql.cpp:80
    #9 0x08989269 in MySQLConnection::~MySQLConnection (this=0xbd1c910,
    __in_chrg=)
    at /home/---/zero/src/server/src/shared/Database/DatabaseMysql.cpp:81
    #10 0x08983cf4 in Database::StopServer (this=0x8e215a0)
    at /home/---/zero/src/server/src/shared/Database/Database.cpp:158
    #11 0x0898912b in DatabaseMysql::~DatabaseMysql (this=0x8e215a0,
    __in_chrg=)
    at /home/---/zero/src/server/src/shared/Database/DatabaseMysql.cpp:65
    #12 0xb769022f in ?? () from /lib/i386-linux-gnu/i686/cmov/libc.so.6
    #13 0xb769029f in exit () from /lib/i386-linux-gnu/i686/cmov/libc.so.6
    #14 0xb7677e4e in __libc_start_main ()
    from /lib/i386-linux-gnu/i686/cmov/libc.so.6
    #15 0x085c0c11 in _start ()
    [/code]
    It looks like something is breaking when attempting to disconnect or save data to the MySQL server upon shutdown. Perhaps this is related to why realm servers no longer work for me? Maybe something was saved incorrectly and now it causes that thread to crash. Either way this is still happening.

×
×
  • 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