Jump to content

nemoma

MU ToolKit (Premium)
  • Posts

    18
  • Joined

  • Last visited

  • Days Won

    3

nemoma last won the day on October 14 2022

nemoma had the most liked content!

Profile Information

  • Gender
    Male

Contact Methods

  • OICQ
    1472676207

Recent Profile Visitors

788 profile views

nemoma's Achievements

Explorer

Explorer (4/14)

  • Reacting Well
  • Collaborator
  • Dedicated
  • First Post
  • Conversation Starter

Recent Badges

4

Reputation

1

Community Answers

  1. As one may know that there are various rings you can equip to change your skin to that of a Monster/NPC. (The CashShop Panda Rings, etc) How about customized items that allows the same function, but can be configured to be any given monster/applicable NPC instead, any added stats/options are also optional. Sure, item model and entries wise it can be a bunch of reskins of the existing rings, but one can always change their model and description into something else since rings don't show outside of inv screen anyways. in S17, the high-end Sets kinda made Custom Sets obsolete, so I'm thinking if a WoW styled Transmogrification system would be better fared. Combined with a custom monsters/NPCs system (which I heard is already a WIP?) I think this can be emulated well.
  2. Currently in Season 17 client, to add new items, ItemTRSData.txt in lang.mpr needs to be changed, and the client seems no longer read Local/itemtrsdata.bmd. However this is the only file that needs to be changed there and each time we do so, a new lang.mpr needs to be generated and shipped - based on the rest of the files in lang.mpr, there shouldn't be any need to generate this file after the interface is localized, since other custom item related strings are all stored in /local anyways. Is there a way to include a configuration that restores this setting so ItemTRSData is read from /Data/Local instead of lang.mpr?
×
×
  • Create New...

Important Information


We use technologies, such as cookies, to customize content and advertising, to provide social media features and to analyse traffic to the site. We also share information about your use of our site with our trusted social media, advertising and analytics partners. See more about cookies and our Privacy Policy.