-
Member
Mirai instead of using FUD about new things, why not think it through and say what fundamentally is required to happen outside that can’t possibly happen inside the turing complete game lua engine.
isboxer suite export only exports a partial subset of what is configured by the user, it doesn’t have to be that limited by a static binding. The current way is indeed simpler for the isboxer addon implementation until mine but as I demonstrate it doesn’t have to be.
How about you try it and tell me what doesn’t work and I (or others, hopefully too, it’s open source) can add/fix it (if it requires change to the generator of isboxer suite, which is likely, as I already would need some to avoid some ugly workaround, I think Lax indicated that’d have to be in isboxer2, which it seems I have to learn
)
And yes I do think going from static to dynamic is potentially a game changing innovation, not something so minor 
And to get back on topic: 0.1.5 is out, and is now available directly from curse client !
changes since 0.1.4:
- Fix for lua error when not running in multiboxing setup (Issue #3)
- Fix duplicate join event/messages
- Debug output now has multiple verbosity level, use /dbox debug 9 for most verbose (new MoLib support for it)
- Cleanup retries
- Handle message send failure
Last edited by Moorea : 06-11-2019 at 04:18 PM
Posting Rules
- You may not post new threads
- You may not post replies
- You may not post attachments
- You may not edit your posts
-
Forum Rules
Connect With Us