should we migrate to an actual object for weaponskills?

[TeoTwawki]

we have an object for items and for spells, but not for weaponskills. the idea has come up before, even as far back as the early days of darkstar. There wasn't an immediate need in order to implement anything so it stayed only an idea. But more and more, I'd like to be able to have functionality and values attached direction on the weaponskill itself, rather than only having its ID available. Checking if the weaponskill closed a skillchain and (if so, which one) comes to immediately mind, as I have seen several people try to determine this in script land where there is basically no logical framework to do so. I'd really like to bake that right into onWeaponskillHit (sidenote: baking in "did this magic burst" for magic hit seems like a good idea as well).

[CatsEyeXI]

as one of the people who's 'tried to determine this in script land', i'd love to see this. it opens the door for coding proper mechanics for vagary and omen (5-step skillchains), as well as other custom stuff we've been imagining lately.