#Proficiencies Stuff
1 messages ยท Page 1 of 1 (latest)
hey, howdy! so, I imagine there's a better way of doing this, maybe?? else it's a suggestion to raise ahah basically all that crap I am doing on the proficiencies code is just to get the Base Item name, because there doesn't seem to be any other way to link them ?
before the weapon types updates I could use game.dnd5e.config.weaponProficiencies to get the already localized names of the proficiency types to show the user, but when weapon types became a thing, that stopped been accurate
So, the way core gets those names is the ProficiencySelector#getBaseItem, which takes an identifier in xxxIds and produces data on the provided item
That works for each individual entry, or you could use ProficiencySelector#getChoices to get all of the individual proficiencies for a certain type and then reformat that into whatever format works best for your module
hmm let me investigate that real quick. this is why I wanted to ask you directly, I imagined you guys were doing stuff on a more proper way
basically I berserker'd my way to make it work xD
Well, you came to the right place since I implemented all of this nonsense ๐
I recall hahah
chesus flying christ, this is absolutely what I wanted
(hmm I don't see the image appearing)
For now you'll have to import ProficiencySelector directly, in 1.6. it should be available in game.dnd5e.applications.ProficiencySelector
now ?
Yep, that's the stuff
yeah yeah, just wanted to leave some "evidence" for anyone peeking around. Oh good notice, I think im actually on 1.6.x on my test bench, wanted to look at Calego's work for the advancements asap. I will check on 1.5.x now
thanks a bunch! just taking advantage of this little moment, do you happen to have any other application you suggest I look at ? I think so far I have used literally no 5e apps on the module, it's all getting maps and arrays and keys from the game.dnd5e.* objects
(i will try to investigate them on my own, but any "start here" suggs are appreciated ๐ )
I think everything else is pretty straightforward, the rest of the CONFIG stuff is pretty straight key/label enums that you should have no problem with
Though you'll have your work cut out when the advancement stuff comes along ๐
I know ๐ though honestly that would make everyone's lives easier, including mine after I rework whatever is needed
you dont want to know the lenghts I've gone to fill in class and race features on the module ๐
Oy
thanks again!