Junior Member
Join Date: Mar 2021
Posts: 6
|
So I've actually managed to take your notes and the latest printing of the PDF and combine them into a rough 2.0 version of the mod. All that's left are about five or so eval scripts that I'm struggling to understand and then sorting everything into rule groups that people can enable separately. Since it's only that much left instead of 60 plus items, think I could pick your brain on putting the finishing touches on it?
|
#151 |
Senior Member
Join Date: May 2013
Posts: 240
|
Certainly, go ahead. What problems have you run into?
Sorry for not responding faster. I usually get a notification email when the thread gets replied to, but that didn't happen this time. Perhaps that's related to the recent forum issues. |
#152 |
Senior Member
Join Date: Feb 2010
Posts: 125
|
One big thing I would request here as a user, assuming the updated version of the rules gets incorporated, would be a clear rules toggle between the 'original' and 'updated' versions - since the games I've been a part of have specifically avoided using the newer version, because of how much more they change compared to the original.
|
#153 |
Junior Member
Join Date: Mar 2021
Posts: 6
|
The big things are figuring out how to change feats that normally select individual weapons to ones that let you choose weapon groups, like point blank master. The other thing I've not figured out how to do is for Agile Combatant, have it check that the player is wielding a finesse (or light) weapon.
As for having a toggle, I can try throwing in a WiS Blog option to have it give the "original" version as an option, but I'm gonna keep a few optimizations and fixes I've come up with that would apply to the old ruleset, and I'll need some assistance reprogramming the .1st file to give a radial option between "blog" and "document" |
#154 |
Senior Member
Join Date: Nov 2009
Location: Jonesboro, AR (USA)
Posts: 858
|
I would also request that either there be a way to toggle or that this be set up as a completely separate option, with its very own update source and all. This would be especially true if you're planning to incorporate changes that you've made to the original but that were not part of either ruleset.
I've adopted the WiS rules in some of my games, and some of my GMs have as well, but we're are pretty conservative bunch when it comes to house rules and I'd hate to see changes made that eliminate the originals as an option. |
#155 |
Senior Member
Join Date: May 2013
Posts: 240
|
I'm inclined to think the best path is to fork the two and treat them as separate modules. I suspect it would be complicated and error prone to try implementing both versions of the ruleset as a series of checkboxes in the hero configuration screen.
On a related note, it would probably be best to set new IDs for the the things in WiS v2. That way, in the event that someone needs both -- say, WiS v1 for one game, and WiS v2 for another -- they could install them side-by-side and just turn them on for the requisite characters. Changing all the IDs through the editor would be horrifically tedious, not to mention you'd have to comb through all the scripts looking for references to things that have changed IDs. It'd be way faster (and more reliable) to open the .user and .1st files in a text editor and do a search-and-replace for each ID that needs changing. Regarding implementing a feat that picks a weapon group instead of a weapon, the best I can do is point you at the code I did for v1. I wrote a bunch of comments in there as it goes through. The gist is that it:
See if you can use the feats from v1 as a model to make it work for v2. If you hit a wall, post your code so we can poke at it. Regarding Agile Combatant -- it's basically Agile Maneuvers, except that they've made a global change specifying that you can use your DEX mod on CMB checks for disarm, sunder and trip when you're wielding a finesse weapon. To implement that I would probably use a Mechanic and write an eval script that checks whether they have a finesse weapon equipped, then substitutes the DEX mod for the STR mod for those maneuvers. The mechanic would also need to check whether they took Agile Combatant and just quit doing things if they have the feat, since it should do all CMB checks. I would be happy to provide hosting for WiS v2 once it's ready, but unfortunately my web host's bizarre rules make that impractical. The issue is that they only allow one FTP user per account. So I would either have to give you my password (and thus grant you complete and total access to everything in all of my sites), or else you would have to send the files to me every time you have an update so I can upload them. Which would be annoying for both of us. EDIT: Oh, and I'm still not getting emails when the thread gets posted to. I'll try re-subscribing to it. Maybe that got lost in an update or something. |
#156 |
Junior Member
Join Date: Mar 2021
Posts: 6
|
so I took your advice and made it a separate module with different IDs (mammoth island or mi instead of world is square/wis) so that they can be installed side-by-side.
Currently, what I need help with is converting this custom expression for selection to just let you choose the weapon groups instead of weapons from those weapon groups: Code:
component.BaseWep & !Helper.NoSelect & !component.Specific & !wCategory.Amm? & !IsWeapon.wCrsRp? & (wFtrGroup.Crossbows | wFtrGroup.Thrown | wCategory.Firearm | Custom.RapidRel) |
#157 |
Senior Member
Join Date: May 2013
Posts: 240
|
Good, I'm glad you did that. Treating them as separate modules just makes sense.
Let's take a look at that custom expression: Code:
component.BaseWep # It has to be a weapon & !Helper.NoSelect # It can't be marked as not selectable & !component.Specific # not sure what this one does & !wCategory.Amm? # It cannot be any kind of ammunition & !IsWeapon.wCrsRp? # not sure what this one does & ( # It must have any one of the following tags: wFtrGroup.Crossbows # Part of the crossbows group | wFtrGroup.Thrown # Part of the thrown weapons group | wCategory.Firearm # A firearm | Custom.RapidRel # Weapon is compatible with rapid reload ) I just spent a bunch of time trying to figure out how to make the select box show a limited selection of weapon fighter groups, and came up blank. That part was pretty easy with the feats I did, like Weapon Focus etc, because they let you pick from ALL weapon groups. All I had to do was select "Weapon Groups" from the drop down and then the select box was set to fShowWhat.WeaponsGrp and they were all there. I suspect you need to use a custom expression to populate the list, but I'm not sure quite what it would be. Anyone else care to chime in on that? As for checking whether a finesse/light weapon is equipped, wouldn't it be something like: Code:
foreach pick in hero where "wCategory.Melee & (wClass.Light | Helper.Finesse)" # Code to do something goes here nexteach |
#158 |
Junior Member
Join Date: Mar 2021
Posts: 6
|
Got the Agile maneuvers mechanic working properly now, just needed a bit of syntax help with figuring out how to check for specific weapons. I did have to add in a check to see if the matching weapon is equipped though, otherwise what you started with would give them the bonuses just for owning a finesse weapon
Code:
if (#attrmod[aDEX] > #attrmod[aSTR]) then foreach pick in hero where "wCategory.Melee & (wClass.Light | Helper.Finesse)" if (each.field[gIsEquip].value <> 0) then perform hero.child[manDisarm].assign[CMBOver.aDEX] perform hero.child[manSunder].assign[CMBOver.aDEX] perform hero.child[manTrip].assign[CMBOver.aDEX] endif nexteach endif Last edited by Shadow_Hawk; June 3rd, 2021 at 12:35 PM. |
#159 |
Junior Member
Join Date: Jan 2016
Posts: 25
|
Hi There,
Trying to reinstall HL on my new machine, including the WiS Square rules. When I try to install the WiS Rules ... Herolab throws up a certificate error. looks like the certificate for meliogeny.net may have expired on July 25th, 2021. |
#160 |
|
|