Jump to content

Neo-Mind

Members
 View Profile  See their activity

  • Posts

    806

  • Joined

  • Last visited

  • Days Won

    18

 Content Type 

Posts posted by Neo-Mind

    4th Job Class Sprites!

    in Ragnarok News

    Posted

    On 3/2/2022 at 3:31 PM, Antares said:

    Nice, but this is just becaming ridiculous. Even at 3rd job you could pretty much solo 90% of the MVPs, so they added new bosses and arenas with even more ridiculous stats. So what will happen at 4th job? You will be even more powerful and they add even more powerful enemies? You will only see 999 999 as damage and still it will take half an hour to kill the new MVPs, while the old mobs and MVPs will be single hitted? ? If they continue on this path, they will not only cause a ton of INT overflows, but perhaps even run out of double number range as well ?? 

    Well technically they raised the attack damage display maximum with K & M suffixes

    increasing the '/memo', warp skill

    in Source Requests

    Posted

    24 minutes ago, Functor said:

    Since versions "2017-05-02aRagexe" and "2017-04-19bRagexeRE" there is no need to modify the code of EXE. These EXEs support the new network packet 0xABE. I will check the code of the latest rAthena after arriving at home.

    Well I do see the following inside packets_struct.hpp. 

    #if PACKETVER_MAIN_NUM >= 20170502 || PACKETVER_RE_NUM >= 20170419 || defined(PACKETVER_ZERO)
	skilWarpPointType = 0xabe,
#else
	skilWarpPointType = 0x11c,
#endif

    But it's not being used anywhere (or Visual Studio is fooling me).

    Translating Palette names

    in Client-side Support

    Posted

    You would need to change the format string being used for making the palette file path.

    For the body palettes, you would need to modify the code to use the job ids directly instead of fetching corresponding strings from a table, or alternatively set the table to use number strings like 4001 => "4001".
     

    WARP - A Successor to NEMO

    in Client Releases

    Posted

    FYI, I have also added Custom Shields & Custom Jobs patches in WARP and yes it supports all clients from 2010 - 2021.

    New features
    Custom Shields:

    • Maximum Shield count can be customized now (limited to 127 for now).
    • You can also validate a shield id based on the job id by modifying ValidateShieldID function in ShieldTable_F.lub.

    Custom Jobs:

    • All the Lua files are now in a different folder called 'JobInfo' to avoid mixing in with others.
      The tables have gone through some changes as well.
       
    • You can specify different strings based on servicetype. For e.g. "korea" and "america" can have different strings. 
      To achieve this, you need to specify an override table with the name LT_<servicetype number>.
      For e.g. LT_0 specifies overrides for korea servicetype. Check PCNames.lub to get a clearer idea. 
      At present it is only used for name changes & palette path changes.
       
    • Scaling for Baby Jobs can be changed. You can change this in Shrink_Map inside PCIDs.lub.
      There is one caveat though, due to client limitation, the factor needs to be specified as an IEEE hex string.
      (no floating point support in Lua function calls ?)

    For both:

    • You get the option to copy the files to your patched client area. The files are copied only if you apply the patch.
    • For Custom Shields, the max shield value also gets updated in the copied file automatically.
       

    I was planning on more amount of changes in Custom Jobs, but it's on hold for now.

    • Love 4
    • MVP 1

    Help || Regarding Weapon Job Sprites With Description of Job Classes || Future reference

    in General Support

    Posted

    14 minutes ago, AinsLord said:

    ohh so eventhough i put it here ÇåÅÍHunter weapon sprites the sprite will be inherited on sniper correct??

    Yes, sniper would inherit from hunter. The name for both would look like 

    data/sprite/Àΰ£Á·/ÇåÅÍ/ÇåÅÍ_<gender suffix><item suffix>.spr

    where
    gender suffix => ³² (for male) and ¿© (for female)
    item suffix => the one you have set in datainfo/weapontable.lub file.

    • Upvote 1

    WARP - A Successor to NEMO

    in Client Releases

    Posted

    On 1/23/2021 at 4:44 PM, sapibuntinx said:

    keep getting error when running the warp.exe, is there any dependencies I need to install first?

    do you have any Visual Studio installed? 
    You would need Microsoft Visual C++ Redistributable for Visual Studio 2019
     

    11 hours ago, Adimgar said:

    Great work Neo.

    I've been testing your software with so many different patches in a few clients (2020 and 2021) which i've previously patched seccessfully with nemo, but i haven't been able to make them work with warp, it always gives me the CTwitterDataMgr error, no matter the langtype and the external settings config i choose.

    My external settings are ok and working on my actual server/client.

    Is there something i could be missing or something that has changed regarding external settings vs nemo's?

    EDIT.

    Starting with a fresh set of patches got rid of Twitter message, but now it gives me "Failed to connect to server" when accessing map server.

    Keep up the greak work you do!.

    Please post an issue in Github . I am also available at the Discord server for any discussions.

    • Popular Post
    • Popular Post

    WARP - A Successor to NEMO

    in Client Releases

    Posted · Edited by Neo-Mind
    Updating snapshot and adding few details

    Happy Thanksgiving everyone. Since I couldn't get the turkey, I thought I would bring this instead. 

    Without further ado, Let me introduce...

    WARP (Windows Application Revamp Package)

    • Why this name?
      Because I like using acronyms and this name sounded apt. Plus it's the function & features that matter more.
      And no, I am not gonna change the name.
       
    • Why not just fix up NEMO?
      The codebase for NEMO is pretty much ancient at this point. So rather than fixing it up, I decided to go the route of creating it fresh from scratch. The end result is a far superior product. 
       
    • OK, but what if you end up AFRO (Away From RO)again?
      Well, I can't promise that I will be around forever. However, this time around, I am releasing the source code for the tool as well.
       
    • So, exactly what has changed?
      Well, quite a few things. Let's start off with how the GUI looks now.

      Warp.PNG.cf9adb9c606048bdf5e8d2498eadeeef.PNG
       
      • As you can see, the GUI is much more modern and aesthetically pleasing thanks to @Haziel & @Hadrias .
         
      • The package comes with 3 tools - Console version (for simple patching), Main GUI, and Tester GUI (for batch testing).
         
      • A big salute to @4144  for keeping NEMO alive while I was AFRO ?.
        Ok, jokes aside, I discussed with him about the changes he made and I have incorporated almost all of them but with some differences. 
         
      • Language & Styles are now on the bottom as you can see. All the remaining menus have now been shifted to drawers (moving side panels). To reveal them you can either swipe from the respective edge or click the button at the top. 
         
      • The right side drawer houses all the Extensions (Used to be called 'Addons' in NEMO).
        They are now loaded independently of the client. This avoids unnecessary redefinitions and now you can also use Extensions for activities that don't need a loaded client.
         
      • All the common functions have been added to the 'Quick Actions' group and all the remaining ones are in the left drawer, which is not many. If you have suggestions for more features let me know.

        Moving on to the Back end (This is of no use to the regular user. So you can skip this part if you want)
         
      • It was high time for us to have a proper input file format. Enter YAML. Love it or hate it but it's here to stay.
        Frankly, I like it more than libconfig and INI. You would be seeing YAML being used for almost every file in WARP.
        This includes input files for Patches & Extensions, Files defining those two, Session files, etc.
         
      • Writing patches is far more flexible now. Say goodbye to PTYPE_HEX and \xAB.
        Now we can do wild card searches with the actual wild cards inside hex codes. Of course, we still need to have some well-defined characters for that.
        Currently, we have 2 forms of wildcards -
        • Nibble wise - For e.g. => A? , ?? , ?3
        • Bit wise - For e.g. => [1.0...01] 
           
      • If you have any suggestions about it let me know.
         
      • Speaking of writing hex code, I have provided functions looking almost identical to Assembly instructions for generating their equivalent hex code. This helps in making the hex code more human-readable and adds a little more flexibility.
         
      • User inputs have a few more types and little more flexibility in specifying constraints now. 
         
      • Scripts have proper segregation now. Please follow them when adding your own.
        Only the scripts inside the 'Init' folder gets reloaded each time the client is loaded. This avoids unnecessary reloads.
         
      • exe has now become 'Exe'.  But in addition to this, you get 2 more objects - System (for filesystem activities) & Warp (whatever is outside the scope of the other two)
         
      • Many of the functions used for retrieving some constant information in the 'Exe' have become properties now. For e.g. PEoffset, ImageBase, BuildDate, etc.
         
      • During patching, the Diff section is only added if you have inserted any code using one of the 'Add' functions. Also, the Diff section now grows dynamically as per requirement (in increments of Section Alignment of course).
         
      • In addition to the Patched Exe, The tool also generates an (Extra Patch Info) file with the suffix '.epi'. It holds just enough info for the tool to recognize existing patches in an exe from a previous patch session. 
        So how is it useful? Let's say you have a patched client and its EPI file. But you don't have the original anymore.
        Now you can remove 1 or 2 patches and keep the rest OR even restore the original from the patched exe.
         
      • Last, but not least, I am providing documentation about everything including the API. But bear with me for a bit, as I am still working on the documentation part.
         
      • I probably forgot more points to add here, but I think this pretty much covers the important stuff. Anyways you can read in detail at the Wiki
         
    • Is it ready to be used now?
      • The tool is definitely ready. I have added most of the patches but not all just yet.
         
      • But I was not able to test all the patches in-game. So please don't attack me if something failed.
        I would appreciate a Bug Request in Github instead. You can also come to Discord as well, if you prefer that.
         
      • Also note, that some patches are still failing for new clients, and some failing for old ones. However, I saw the same behavior in NEMO, so that would be part of the next stage of operations - Updating Patch scripts.
         
    • So, where do I get it from?
      https://github.com/Neo-Mind/WARP
       
    • How to use it?
      There is a User Guide in the git repo (best viewed from Github itself). Everyone is used to NEMO by now, so it shouldn't be difficult to use this even without the guide. Plus the Github wiki is pretty detailed. 
       
    • Any last words before we close this?
      Just like in the case of NEMO, my intention with WARP is to create a common tool for patching without being restricted to RO or which OS you use it in.
      For this reason, you will be seeing multiple branches in the Git repo.

      If you are planning to use WARP for patching some other application, Create a branch using the 'win32' branch as a starting point

      That's about it from me for now.

      warp-speed-mr-sulu-destination-beer.jpg.1be1cd98df6017f6f95ff67eb4a081db.jpg
    • Upvote 10
    • Love 13
    • MVP 8
    • Like 2
    • Popular Post
    • Popular Post

    Successor to NEMO [WIP] - Need UI Suggestions

    in Project Concepts & In Progress

    Posted · Edited by NeoMind
    highlighting 2 important lines

    missme.gif.add71d72f90c833b2df97bcf2c788457.gif

    Probably not xD
    Anyways, I am working on development of a new patcher as a successor to the original aka NEMO. 

    Initially, I was planning to just release the source for NEMO but is quite outdated.
    So I decided to just start off fresh utilizing concepts from the original along with new ideas (Already have some implemented, which I will explain later)

    Also this time, I will be keeping it open source. I will publish to Github once there is a solid foundation.
     

    I am building it using the latest version of Qt (5.15) and utilizing QML for creating the GUI. I want to give it a more modern appearance, however, I am a "novice" on this front. So I am inviting suggestions for the UI from the talented individuals here.

    • Upvote 5
    • Love 15
    • MVP 5
    • Like 2

    [WIP] Native Ragnarok Client

    in Abandoned Projects

    Posted

    To settle the question of open source once and for all: I'm planning to release the full source code sometime in the future. When the code is released, anyone who wishes to do so will be free to fork the project, add renewal features, organize their own development teams and whatever. As I've already stated, I will not be interested in collaboration. I will release when I've reached my milestone for feature completion, and this will be the first and final release.

    music to my neko mimi :D

    • Upvote 1
×
×
  • Create New...