Jump to content

SweeTs

Legendary Member
  • Posts

    8,941
  • Credits

  • Joined

  • Last visited

  • Days Won

    25
  • Feedback

    0%

Posts posted by SweeTs

  1. Umm, I didn't look into the code, just read some posts and it seems like the PLAYER, actually, is "triggering" the update? If so, that's plain stupid, lol. I would simply put the update under the thread pool and update list each X time. I see no reason for any timestamps and so on.. Thread pool updating itself. It could not be simpler. 

    • Thanks 1
  2. 1 hour ago, L2RAPTOR said:

    I hear opinions..I want facts to support them.. I guess go check L2jorion.com and see if these files are as good as any other...and if not, tell me why not..

    Are you retarded or what? It's NOT about "does it work or there are bugs", "how good the features are". It's all about the code aspect. So.. crawl back to your hole and don't talk as you are not a developer, just an admin.

     

     Admins and players pov in this subject... doesn't matter.

     

    Read the topic once again.

     

    On 3/13/2021 at 10:56 AM, TehBot12 said:

    Java side primely.

     

    ----

     

    Yoo fellas. @Kara,╭∩╮(︶︿︶)╭∩╮

  3. More like, if you want a ready to go server, take Lucera. Otherwise, aCis, yet you will have to implement all what you need and fix potential issues.

     

    People are using Lucera since ages and say it's good enough, no major bugs and have shitload of customs.

     

    Everything depends what you really want. A project to worn on or you want to open a ready to use server.

     

    --------

     

    Btw, hello fellas. Long time no see*.

     

    * - not coming back, no time for mxc bullshits, just saying hello 😄

  4. Simplest solution. Before you do revive, make a zone check.. Sounds obvious, right.

     

    Whatever you like. Could be assigned to some method, variable as suggested. But it's not like it's a must, nor the whole code is super duper. Keep it simple stupid.

  5. As from time to time I see people searching for time limited items and/or questions about how to modify the shadow items system, I decided to code one.

    There is nothing modified from vanilla code, everything is custom.

     


     

    Q: So, how does it work?
    A: All you have to do is to add a new XML line to your item. The time value is in minutes.

    <set name="time" val="1" />

     

    Q: When the time-task is triggered?
    A: The task is triggered on item acquisition.

     

    Q: Is it limited to weapon/armor type items?
    A: No. You can add it to ANY item, whether if it's a weapon, armor or etc item.

     

    Q: Is it possible to display remaining time on client as it's done with Shadow Items?
    A: Yes, of course. The only requirement, as in Shadow Items case, is to modify the client armorgrp/weapongrp/etcitemgrp file, durability row.

     

    Q: Can I put some restriction on the item?
    A: Yes, you can. You can use restrictions as on any item via XML.

     

    Q: But is it safe to allow trading or dropping the item?
    A: Yes, it is. If you drop the item and someone pick it up, it's gonna be removed as well (once picked up, item is not removed from the ground).

     

    Q: Are there any hard-coded restrictions?
    A: Yes, the only restriction that is hard-coded is, you can not drop the item on death nor refine it.

     

    Q: What about items in warehouse?
    A: Items in warehouse are also checked, so if the time is over, they will be removed as well.

     


     

    uJqD6ev.png uJqD6ev.png

     


     

    PsDDDtm.png

    • Like 5
    • Upvote 2
×
×
  • Create New...