The following warnings occurred:
Warning [2] Use of undefined constant SAPI_NAME - assumed 'SAPI_NAME' (this will throw an Error in a future version of PHP) - Line: 3388 - File: inc/functions.php PHP 7.4.33-nmm7 (Linux)
File Line Function
/inc/functions.php 3388 errorHandler->error
/showthread.php 116 build_archive_link
Warning [2] Use of undefined constant IN_ARCHIVE - assumed 'IN_ARCHIVE' (this will throw an Error in a future version of PHP) - Line: 3331 - File: inc/functions.php PHP 7.4.33-nmm7 (Linux)
File Line Function
/inc/functions.php 3331 errorHandler->error
/inc/functions.php 3324 build_forum_breadcrumb
/showthread.php 195 build_forum_breadcrumb
Warning [2] Use of undefined constant IN_ARCHIVE - assumed 'IN_ARCHIVE' (this will throw an Error in a future version of PHP) - Line: 3331 - File: inc/functions.php PHP 7.4.33-nmm7 (Linux)
File Line Function
/inc/functions.php 3331 errorHandler->error
/showthread.php 195 build_forum_breadcrumb






Post Reply 
 
Thread Rating:
  • 0 Votes - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Warnings while compiling 56c and default combat messages
Author Message
Mad Gunther
Apprentice
*

Posts: 45
Likes Given: 11
Likes Received: 5 in 5 posts
Joined: Oct 2015
Reputation: 1



Post: #5
RE: Warnings while compiling 56c and default combat messages
Hello Coruja, Thanks for the info.

I´ve been trying what you said and itemdamagelayer works pretty good. I can get the layers easily but i have noticed that info on sphere_defs doesn´t fit too much with the info that i get ingame. For example ingame i get 3 layers that are not listed in sphere_defs, they are:
layer_neck=0x0a
layer_waist=0x0c
layer_innertorso=0x0d

Other strange seen i have checked out is that the higher layer i get is 18. if we look through source or sphere_defs layers are organized like this:

Code:
layer_hand1       1
layer_hand2       2
layer_shoes       3
layer_pants       4   // bone legs + pants.
layer_shirt       5
layer_helm        6
layer_gloves      7
layer_ring        8
layer_talisman    9   // talisman (se and ml)
layer_collar     10    // gorget or necklace.
layer_hair       11
layer_half_apron 12
layer_chest      13   // armor chest
layer_wrist      14   // watch
layer_light      15   // a itemid_light_src equip item can be put here.
layer_beard      16   // try to have only men have this.
layer_tunic      17   // jester suit or full apron.
layer_ears       18   // earrings
layer_arms       19   // armor
layer_cape       20   // cape
layer_pack       21   // only used by itemid_backpack
layer_robe       22   // robe over all.
layer_skirt      23   // skirt or kilt.
layer_legs       24   // 0x18 = plate legs.

Doesn´t make sense really... i had the idea to check the runuo core source, and voila!

Layer List
Code:
        Invalid      = 0x00,

        FirstValid   = 0x01,

        OneHanded     = 0x01,
        
        TwoHanded     = 0x02,
        
        Shoes         = 0x03,
        
        Pants         = 0x04,
        
        Shirt         = 0x05,
        
        Helm         = 0x06,
        
        Gloves        = 0x07,
        
        Ring         = 0x08,
    
        Talisman     = 0x09,

        Neck         = 0x0A,

        Hair         = 0x0B,

        Waist         = 0x0C,

        InnerTorso     = 0x0D,

        Bracelet     = 0x0E,

        Unused_xF     = 0x0F,

        FacialHair     = 0x10,

        MiddleTorso = 0x11,

        Earrings     = 0x12,

        Arms         = 0x13,

        Cloak         = 0x14,

        Backpack     = 0x15,

        OuterTorso     = 0x16,

        OuterLegs     = 0x17,

        InnerLegs     = 0x18,

        LastUserValid= 0x18,

        Mount     = 0x19,

        ShopBuy     = 0x1A,

        ShopResale     = 0x1B,

        ShopSell     = 0x1C,

        Bank         = 0x1D,

        LastValid    = 0x1D

These ones contrast well with what i get ingame, and i suppose i don´t get some of them because i´m using a 2.x.x version client (like bracelet for example). By this i mean the info available is not accurate right? because if not i don´t know whats really going on here lol. i´m planning to set layers manually when @gethit is called, so i´m planning to use the last ones and add the messages with them.

About the 56d, it sounds good. If it is less buggy and perfomance is better then let´s give it a try. I just changed a couple minor things in source that are hardcoded like parrying or adding styles to the attacks, so yea looks like the better option.
(This post was last modified: 06-18-2016 10:42 AM by Mad Gunther.)
06-18-2016 07:38 AM
Find all posts by this user Like Post Quote this message in a reply
Post Reply 


Messages In This Thread
RE: Warnings while compiling 56c and default combat messages - Mad Gunther - 06-18-2016 07:38 AM

Forum Jump:


User(s) browsing this thread: 1 Guest(s)