|
Really looking to see more from this, you got me really interested by the media
I've just recently implemented a Kotlin DSL for drop tables to assist in the development of NPC drops. The design for this API was taken from an implementation that Scu11 has previously shown, and I thought it worked out quite well, so all credits to the idea are to him. These drop tables have access to the current mob that is dying, and as well as the killer, which allows for dynamic drops based on that state (such as if an NPC is in the wilderness, or if the player has a defender in their inventory then we should give them the next available one). This also has support for shared and nested drop tables as you can see with the herb drops:
I've also recently begun rewriting the networking of Arios to make use of Netty and coroutine contexts where appropriate. Incoming and outgoing messages are defined as Protobuf messages, with their encoding details and ordering built into the message as field annotations. This allows us to autogenerate both the structure and the codec of a message without cluttering up the server's code. Of course this solution isn't perfect and there is still some exploration required for more complex messages such as GPI, but for now I think it serves as a good starting point.
cant say ive experienced that. my only advice is to look at the cs2 functions, theres like 10 of them that are utilised on that interface. similarly you should utilise all the enums that those cs2 scripts do, and itll save you duplicating loads of configuration (e.g. the mappings of the styles/colors)
Just a few visual updates today! I've managed to get the OSRS Context Menus (with support for switching back to the 667 context menus) and the OSRS login box added. Here's some sneak-peekery!
« Previous Thread | Next Thread » |
Thread Information |
Users Browsing this ThreadThere are currently 1 users browsing this thread. (0 members and 1 guests) |