Welcome!

Join our community of MMO enthusiasts and game developers! By registering, you'll gain access to discussions on the latest developments in MMO server files and collaborate with like-minded individuals. Join us today and unlock the potential of MMO server development!

Join Today!

Recent content by Yuuroido

  1. Yuuroido

    Official-Like Mob Spawn Rate

    Thank you for the reply :) Well... I'm sure that at least in JMS, the formulas for the map size and the capacity are still the same as BMS's, as I've confirmed it in 30 hunting maps (btw I got actual map size from SetField packet to compare). (If anyone is interested, here is a list of...
  2. Yuuroido

    Official-Like Mob Spawn Rate

    I was just wondering why 'MapSize' and 'MobCapacity' in my server didn't correspond with official server's. So I decided to investigate what's wrong with my server and have achieved reproducing the official-like mob respawn system. *Disclaimer* It doesn't include full source code but pieces of...
  3. Yuuroido

    Gms v117 Arkarium Skill(AmplifyDamage)

    Oh, I don't know about that. Hmm... it's just a guess, but possibly it uses 'Buned' (aka 'VENOMOUS_WEAPON'?) to show DoT but you'll need to implement a function that can find mobs in an area and reduce their hp in each second on server-side... if there's no related packet sent from client to...
  4. Yuuroido

    Gms v117 Arkarium Skill(AmplifyDamage)

    oh sorry I don't know what you are talking about.
  5. Yuuroido

    Gms v117 Arkarium Skill(AmplifyDamage)

    BanMap(46), //0x4000, 2 You must be registered for see element.
  6. Yuuroido

    Gms v117 Arkarium Skill(AmplifyDamage)

    uh, here you are //GMS 117 DeathMark(195), //0x8, 7 Lapidification(199), //0x80, 7 VenomSnake(200), //0x100, 7 PainMark(231), //0x80, 8 Magnet(232), //0x100, 8 MagnetArea(233), //0x200, 8 VampDeath(234), //0x400, 8 *this is basically 'VampDeathSummon' //TMS 149 DeathMark(191), //0x80000000, 6...
  7. Yuuroido

    MobSkill of Cygnus(Sleep and wakeup)

    It's a monster buff. TMS v147 ExchangeAttack(37), //(0x20, true)? GMS v117 ExchangeAttack(38), //(0x40, true)? The buffstat structure is NOT 4+4+2 bytes but just a byte which indicates 'sleep'.
  8. Yuuroido

    MobSkill of Hilla(Deadly Alfter)

    I just forgot how I convert it to odin style(?) but here are buffstat numbers for Magnet and MagnetArea //GMS v117 Magnet(232), //0x100, 8? MagnetArea(233), //0x200, 8? //TMS v149 Magnet(226), //0x4, 8? MagnetArea(227), //0x8, 8?
  9. Yuuroido

    MobSkill of Hilla(Deadly Alfter)

    hmm you might have named a wrong buffstat as Magnet/MagnetArea then. by the way which version is this?
  10. Yuuroido

    MobSkill of Hilla(Deadly Alfter)

    It needs two buffstats, Magnet and MagnetArea. MagnetArea should be next to Magnet (which you showed). nValue for the Magnet is x position of a mob, and nValue for the MagnetArea is 'x' value from wz (or I thought so. it indicates a range that players will be captured by the effect ...or it...
  11. Yuuroido

    WZ Item Drop Filter - Icon background transparency issue

    HaRepacker/Converter/BitmapToImageSource.cs BitmapEncoder enc = new PngBitmapEncoder();//BmpBitmapEncoder ... bitmap.Save(stream, System.Drawing.Imaging.ImageFormat.Png);//Bmp correct me if I'm wrong
  12. Yuuroido

    about skill 'Call of the Hunter'

    I'm not sure what LinkCID is, I meant the debuff's "x"(?) value. (it's called as 'nDazzle' in official) You need to set it to character id. (since post-bb(?))
  13. Yuuroido

    about skill 'Call of the Hunter'

    Did you set the stat value to character id instead of 1?
  14. Yuuroido

    Official Has the system requirements for MapleStory been increased recently?

    I really appreciate your reply, but I'm sorry to say I wanted v193.1 or v193.2 (or v193.3) or v195.1 to be exact, so... Thank you anyway. Thanks to ahnlab; I could check v193.2, v193.3, v195.1 and confirmed the dll was not listed.
  15. Yuuroido

    Official Has the system requirements for MapleStory been increased recently?

    So, I've just compared 37 executable files (v354-v378) using Exeinfo PE and found that there's a common point between ones which were considered to had this issue and the others weren't. Could someone please explain to me what does the difference imply? or is it just a coincidence? oh no it...
Back
Top