Jump to content

Vianna

Members
  • Posts

    47
  • Joined

  • Last visited

Profile Information

  • Gender
    Male
  • Location
    Rio de Janeiro, Brazil

Recent Profile Visitors

2214 profile views

Vianna's Achievements

Poring

Poring (1/15)

8

Reputation

  1. @edit: Here's an updated version
  2. I've worked with the Fimbulwinter Client in C#/XNA and everything was doing OK, but we found out there was no reason to use XNA. We can't use its Content Pipeline, and it was taking a little while to load everything from the GRF (I think the main reason is because Texture2D.FromStream doesn't support .bmp files). Also, it looks like Microsoft isn't going to update XNA anymore.
  3. Change your etcinfo.txt loadingscreen# 4# 4 is the amount of loading screens you have.
  4. Isn't it already done? Last time I checked, they changed it so <yellow> accounts have the suit and <admin> accounts have the right click commands. Unless <admin> accounts only trigger the menu if they are also <yellow> accounts, but then it would be pretty easy to change. If no one else wants to make it, I will as soon as I have enough time.
  5. make sure that different client include this WDGForceClientHashPacket.dll on his diff. or else it cannot connect to the server if the client_hash_check is on what i mean is i want to change the "error" that client given if they're using different client. It's somewhere in msgstringtable.txt
  6. Make sure there isn't a line like this in your clientinfo.xml <readfolder></readfolder>
  7. You must change // Units types affected by max_lv and aura_lv settings. (Note 3) // Note: If an unit type, which normally does not show an aura, is // set it will obtain an aura when it meets the level requirement. // Default: 0 (none) client_limit_unit_lv: 0 to // Units types affected by max_lv and aura_lv settings. (Note 3) // Note: If an unit type, which normally does not show an aura, is // set it will obtain an aura when it meets the level requirement. // Default: 0 (none) client_limit_unit_lv: 1
  8. I think he said he wouldn't do that one because rAthena already supports it.
  9. Why don't you add a new data section to the PE with all the translated strings, so there's no limit to the character count? It'd take longer to patch because you would have to search for all references to the string, but wouldn't it be work the effort? Or maybe you could use the same functions the client uses to access strings from msgstring_kr.lua, using custom indexes (that would look less hacky)
  10. Vianna

    HP/SP formula

    They use a generic formula to generate the table... It's not like the exp table, where every level has an arbitrary amount of exp. Well, if you're going with the fixed table format, it would be nice to include documentation on how the tables can be generated and maybe a new tool to the /src/tool/ folder, so it would still be easy to buff/nerf classes HP and SP while preserving the original increase patterns. AEGIS probably uses a table only to allow the publishers to modify the values without having to ask for recompiled binaries
  11. IMO..for now yes..but once they add a new function to support sending of modified Hash code to server..well that's a hole.. They already do, and it's been a while since it had been implemented. It's still undocumented, though. *coughs* clientHash *cough* servers.txt ~
  12. Enabling/not disabling HackShield using only a diffpatcher wouldn't work. First of all, it would only block packet editors and other cheats that require the original client to be running. OpenKore would still work. X-Kore wouldn't work, but X-Kore Proxy would. And it could be simply disabled by modifying the client to remove it and then intercepting the checksum checks. You need server-side checks.
  13. I meant these settings: // Account data storage configuration // SQL //account.sql.db_hostname: 127.0.0.1 //account.sql.db_port: 3306 //account.sql.db_username: ragnarok //account.sql.db_password: ragnarok //account.sql.db_database: ragnarok //account.sql.codepage: //account.sql.case_sensitive: no //account.sql.account_db: login //account.sql.accreg_db: global_reg_value
  14. Did you change the account database settings in login_athena.conf?
  15. +1 and/or an option to completely disable aura Lv 99/150. max_lv: 98 aura_lv: max level Characters with level 1~(max level - 1) will be sent as level 97 and characters with level (max level) will be sent as level 98: no aura.
×
×
  • Create New...