tposney / midi-qol

Other
5 stars 0 forks source link

Is there any technical reason that the non edition specific code cannot be used in 3.5? #958

Open tposney opened 2 years ago

tposney commented 2 years ago

In GitLab by @MyRealUsernameWasStolenByRentSeekersAtGitlab on Aug 19, 2022, 18:09

What it says on the tin. I wanted to use some of the item macros in my 3.5 campaign because well, it's the only way I've ever been able to find to attach any kind of code to a weapon without writing my own custom module to handle the on-hit properties of a single weapon that my player is going to throw away in 3 levels anyways.

Is the problem technical? Legal (Did wizards threaten you with legal action if you supported 3.5)? What's going on?

tposney commented 2 years ago

There is no legal reason and I've received no threatening messages.

The way that midi is implemented is that it relies on some specific features of dnd5e to operate. Having said that dnd 3.5 is probably not so different that it would be impossible to make midi work with dnd 3.5, it's just that I don't play dnd3.5 and so the effort to make it work with dnd3.5 is not something I'd get value out of.

Having said that the module IteMacro is not (as far as I know) tied to dnd5e so you could write itemMacros for dnd3.5, they just get different data when the macro is called.