Originally posted by darncat
let me add something to complete this idea:
not only do we need "or"
we need "NOT"
as in, for example:
tagged Passer QB, tagged Speedy RB, NOT Blocker TE
thats just an example, im tired of having to make identical sets of outputs over and over
Yes +1
Definitely necessary. A Not option would save me a lot of time on QB inputs, and the or option would save me time on every other position. This is a simple fix and needs to be done. Dcing is a headache... especially for 2 TE sets, the amount of inputs needed to satisfy a team with 3 different TE tags is staggering, especially when you add in combination of FB, HB, and QB. I did it once, and made a shell, but filling the outputs out for it is horrendous. I honestly think about killing myself whenever I am filling it out, just because it would be easier than filling out all of the outputs. Making the shell for all of the inputs took me upwards of 4 hours, especially since I have 3 seperate QB, and HB tags.
let me add something to complete this idea:
not only do we need "or"
we need "NOT"
as in, for example:
tagged Passer QB, tagged Speedy RB, NOT Blocker TE
thats just an example, im tired of having to make identical sets of outputs over and over
Yes +1
Definitely necessary. A Not option would save me a lot of time on QB inputs, and the or option would save me time on every other position. This is a simple fix and needs to be done. Dcing is a headache... especially for 2 TE sets, the amount of inputs needed to satisfy a team with 3 different TE tags is staggering, especially when you add in combination of FB, HB, and QB. I did it once, and made a shell, but filling the outputs out for it is horrendous. I honestly think about killing myself whenever I am filling it out, just because it would be easier than filling out all of the outputs. Making the shell for all of the inputs took me upwards of 4 hours, especially since I have 3 seperate QB, and HB tags.
