Jump to content

madmax

Community Manager & Security Lead
  • Posts

    2064
  • Joined

  • Last visited

  • Days Won

    75
  • Donations

    0.00 GBP 

Everything posted by madmax

  1. Hey, Any update on this?
  2. Closing this. If needed please reopen.
  3. Bump for devs.
  4. Bump. Needs confirming.
  5. Bump for devs
  6. Is this still bugged in the latest develop21 branch?
  7. [URL="https://www.getmangos.eu/members/ascentu/"]ascentu[/URL], can you check this again for us with the latest release?
  8. Could do with someone double checking this? Will assume this is fixed if no one replies with any issues in a few days.
  9. Ok, thanks for confirming. Will mark this as completed and closed.
  10. This still happens but not as bad now. The fish do seem to jump around but under the ground now, they no longer appear above ground. Could you confirm the correct [COLOR=#3E3E3E]Inhabit_type in creature_template for me ?[/COLOR]
  11. Character DB not have 'character_db_version' table 19:03:59 Account: 1 (IP: removed) Delete Character:[Jyotin] (guid: 1410) 19:03:59 SQL: SELECT * FROM character_db_version LIMIT 1 19:03:59 query ERROR: Table 'characters-classic_cosmicray.character_db_version'doesn't exist 19:03:59 Character DB not have 'character_db_version' table, revision guard query not added to pdump.
  12. Setting realm name in config.wtf bypasses "allowedSecurityLevel" Setting a realm in the database to 3 under "allowedSecurityLevel" currently does the following: Makes the realm appear offline to those below the security level... That is all! This can be bypassed with a simple edit to the config.wtf and adding the realm name (which you can get as it appears as offline in the list. Two things are needed to fix this. The realmlist being sent should be checked, i.e "allowedSecurityLevel" should be considered by realm-daemon before sending the realm list to the client. If they don't meet requirements no need to send the realm name/ip or data to the client. Mangos-daemon should double check incoming clients GM level. I suggest that any non-GM user attempting to connect / login to a security protected realm be treated the following: Not have permission to create characters - Be told character creating is disabled. If characters exist they should be sent the "world server down" message (preventing them logging in). Kicked or gracefully disconnected after 30 seconds by mangos-daemon. Please discuss
  13. Confirmed as fixed. Closing. [IMG]https://i.gyazo.com/00064138125441f41e325ea4acca6c56.gif[/IMG]
  14. Look into and if possible implement optimizations into the movemap-generator Currently generating movemaps is very time consuming. This task is to look into further optimizing the .exe Things to look into: Multicore Threads Are tiles independent?
  15. dbdocs SQL update 22 to 25 will not apply - work around until fixed Current SQL updates do not apply to the database / update the version table. [LIST] [*]Rel21_1_22_dbdocs_updates.sql [*]Rel21_1_23_more_dbdocs_updates.sql [*]Rel21_1_24_dbdocs_updates.sql [*]Rel21_1_25_dbdocs_updates.sql [/LIST] Current work around for this: Change 21 in the content field to 25. you will be able to pickup from update 26.
  16. Any update on this?
  17. @xfury is this still an issue?
  18. Confirmed as still an issue. [IMG]https://www.getmangos.eu/attachment.php?attachmentid=305[/IMG]
  19. Fixed by commit - [url]https://github.com/mangosone/server/commit/231128df3519fe53d68ac14aca7e38798894c863[/url]
  20. @antz any update on this?
  21. Reopening as its not clear in the messages if this issue is fixed or not. Will need someone to confirm.
  22. Merged and closed.
×
×
  • 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