Howdy, Stranger!
Categories
- 6.2K All Categories
- 3.1K Everything Achaea
- 1.5K North of Thera
- 26 Archives of the Terraformer
- 257 The Matsuhama Arena
- 885 The Golden Dais of Creation
- 299 The Scarlattan Theatre
- 149 The Blank Canvas
- 2K Getting Help
- 412 General Questions
- 258 Quick Class Questions
- 1.3K Tech Support
- 313 Client Help
- 486 Curing Systems and Scripts
- 841 Off-Topic
- 255 The Wander Inn
- 586 The Universal Membrane
- 298 Class Discussions
- 298 Individual Class Sections
- 20 Alchemist
- 9 Apostate
- 30 Blademaster
- 9 Depthswalker
- 14 Druid
- 4 Infernal
- 20 Jester
- 19 Magi
- 34 Monk
- 11 Occultist
- 8 Paladin
- 7 Priest
- 29 Runewarden
- 18 Sentinel
- 26 Serpent
- 20 Shaman
- 9 Sylvan
Comments
Results of disembowel testing | Knight limb counter | GMCP AB files
Once that's complete and I finish up a few other housecleaning tasks I'll release it an "official" version 1.2. Will pop some documentation on the GitHub around that time as well, finally.
Please report any issues you find either on the GitHub repository itself or via WBUG -- sends a message to me directly.
Thanks as always, folks.
I do not currently have any new features planned for WunderSys. That being said, this should be a decent baseline for newer players interested in a system that they can easily adjust and learn from. Still have some documentation to put up -- coming together slowly but steady on the repository's wiki section.
As always, please feel free to contact me here, via Discord or in-game with any bugs, questions or concerns and I'll be happy to help out.
Just to be on the safe side, do you have any formal upgrading instructions to better facilitate the switch over? Don't want to break anything!
- Zip up your profile and keep it somewhere safe.
- Uninstall the old package.
- Install the new one. Once it reads your settings, QQ and then close Mudlet.
- Open Mudlet back up, say a quick prayer to the hurricane gods and all should be well.
This all comes with a caveat, though. If you've modified core WunderSys functionality (in the WunderSys folders) -- and have custom aliases/triggers/scripts outside the WunderSys folder that rely on that modified functionality -- that will probably break.If you made huge, breaking changes on your WunderSys installation ages ago it might not be worth having to rip out all the custom stuff you've created. The specific, larger changes I'm responsible for can be added in separately with maybe an hour or two of work.
My version of WunderSys is around the 1.1.3 area so I would not want to use the system itself right yet.
I kept the docs as simple as possible (they are in plain html and unminified css).
http://zpaav.github.io/WunderSys/
WunderSys v1.2.1
Hey all. It's been a while, but I've started working on this again. I've already rolled @Anze's 1.2 version changes back into my github and re-released that as is. And then building from that, I've made some more fixes and improvements, and now have a 1.2.1 maintenance release (hopefully) ready for use.
See https://github.com/tynil/WunderSys/releases for the latest release.
The release page lists the biggest changes made here. This one wasn't too major, but did fix a lot of small things. Special thanks to @Rakkaro for finding all sorts of ways a serpent can abuse your priorities, and @Oblive for sharing a lot of knowledge on various new classes. This release does include better default priorities for air lord, and some (un-tested) default priorities for the new priest changes. If you're upgrading, in order to get the new default priorities, you'll want to do WCONFIG PROFILE RESETAFFS ALL CONFIRM. If you omit the CONFIRM bit, it'll do a dry run to show you what prios would change, without actually changing any.
I'm still working on things, so as long as I don't fade away for another 3-4 years, expect more releases in the coming months. The next major update I have planned is to move to relying fully on GMCP (except where unable), for at least affs to start, defs second. Currently, WunderSys has GMCP aff tracking, but it was added as an afterthought, and all the old trigger-based aff tracking is still there. I plan to scrap all the triggers (I may leave them around, and just gut wsys.affadd() to only do the affprint call if people use that, and nothing else). The only thing some triggers may be needed for are the odd stackable affs, which I'll want to handle in a clean shared manner. Related to some comments above, my long-term goal would be to create a light-weight framework that really is just tracking things (aff, def, balance, etc.), and maybe some utility functions for helping to build a system, without necessarily doing any priority shifting on it's own. That still may be a ways off though. For now, I'll just see where I get cleaning up WunderSys in it's current incarnation.
Let me know if anyone has any issues. To be on the safe side, I would echo Anze's comment about backing up your mudlet profile before loading, just in case. If you don't want to back up the whole thing, you may just at least want to back up the wsys_settings.lua in your profile folder. While testing the 1.2 version changes from Anze, I somehow ended up losing my settings (though I had some other custom stuff in place that I've since removed). The good news is that reconfiguring settings really isn't that hard. It's mostly just customizing your prompt, then setting up defense keepups.
You still have to switch profiles when you switch class, but you can have the same bashing triggers or target alias or whatever between profiles.
So anyway, stick with svo if you want, or if you want to try wundersys again (or general info for anyone wanting to get started with it), I recommend taking a look at https://github.com/tynil/WunderSys/wiki/Basic-Setup. Create a profile, set up your defences using wshow keepup/defup and clicking what you want, then wshow defprio to shift those. The related aliases for those commands are:
- wconfig defup/keepup <profile> <defence> (I should probably add an option to do this without needing to specify profile. I'll add that for the next release version)
- wconfig defprio <defence> <#>
It does not read/import anything from your current defenses. And testing a little myself, it looks like it won't clear out anything that you already have added (Also probably something I can eventually add, but that's a longer-term effort, not for the next version). So you'd probably need to manually clear out all the defences that you don't want, then configure what you do want with the wconfig/wshow commands.
Once you have it setup for one class, switch to your next class and 'WCONFIG PROFILE COPYCLASS <previous_class>". That'll copy all the setup you just did with one class to the next, though you'll probably still need to configure your new class defences again.
As for k bashing, did you explicitly set kconfig bashing system wundersys? Alternatively, if you're uninstalling svo, make sure you close mudlet after doing so. Uninstalling a script doesn't clear out all the functions/event listeners it may still have running, so you'd want to close and re-open mudlet to be sure it's clean. I played around with that a little and did get it to work with the latest prerelease versions, though I made some small changes to make it play nicer (it was clearing my doqueue when I get un-prone even when I had it disabled). I'll see about committing my changes there sometime soon as well.
there seems to be some sort of trick to making it start appear, I usually fuss around with it until the command works but for some reason I'm not able to stumble upon the right sequence today:
Also, to follow up, I helped @Jethan figure out some issues with configuring defences, and it turns out that using the "wconfig defup/keepup" aliases probably isn't recommended at this point. We found a bug where if you try to configure something that isn't a valid defence, you might hit errors. Configuring using the WSHOW KEEPUP/DEFUP/DEFPRIO tables and clicking what you need is safer, until I've fixed some of the odd cases and made those aliases more robust.
WunderSys v1.2.2
WunderSys v1.2.2 is now available. See https://github.com/tynil/WunderSys/releases for details. It's mostly just small changes. I'm still testing the changes to switch to (near) pure GMCP aff tracking. One change I want to note is that I've moved releases to the production/stable branch. If you install a copy of WunderSys from that branch, or any of the stable releases, it will only check for updates on that branch, which should be less frequent and only after they've been reasonably tested.If instead, you're interested in the latest changes that I'm working on, which may not always be 100% tested yet, you can download any of the pre-releases (I don't have any up yet), or download WunderSys.xml directly from the master branch (https://github.com/tynil/WunderSys/blob/master/WunderSys.xml). These versions will check for updates on the master branch, which I may be releasing more frequently and with less testing. If you're willing and interested in testing these, then check these out and let me know if you find any issues!
Also, since I'd like to make it easier for people to update WunderSys, let me know if there are any things that you typically have modified for your own preferences within the system. If possible, I'd like to try and provide ways to make those modifications outside, so it's less of a hassle to update. For example, thanks @Gilliam for suggesting the changes to customize the aff tag short names and colors.
- 1 insanity gave dementia
- 2 insanities gave stupidity, dementia
- 2 insanities gave stupidity, confusion
I didn't see any consistent pattern from that.I plan to release a 1.3-beta build in the next couple of weeks (this Tide event thing may delay progress some). The main goal for this upcoming release is to make the jump from the current trigger based aff tracking to nearly pure GMCP aff tracking (with some triggers for stackables, including unweaves and pressure), using the WunderSys Foundation.xml script that I've quietly put up. I've been working with and using it myself for at least a couple weeks now, but I'm still finding and fixing things I've missed (thanks for breaking me @Santar ). After I think it's in a reasonably good place, I'll push it up and do a beta release for others to start testing with as well. As this will be a significant change, I can't guarantee everything is perfect in the first go, so hopefully others can help with testing when it gets to that point.
If you wanted to try out just the aff tracking piece, you're technically free to download and install WunderSys Foundation.xml separately (it only tracks things and puts them in tables/raise events. It does not perform any actions). Then change your affTags call to use wsysf.affs instead of wsys.aff. That'll change the prompt tag to reference the new table. It will not use the new table to change curing priorities yet though.
Note that if you want to be notified when the first 1.3 beta is out, in the "Check for Updates" script, change the branch = "production/stable" to branch = "master" (or install WunderSys.xml directly from the master branch)
I'm wondering if this will eventually grow to replace my existing gmcp parser that drives my gauges/consoles/antitheft/etc.