Reply to thread

Message

<blockquote data-quote="Margaiaman" data-source="post: 311488" data-attributes="member: 2134">Thats my problemI suppose I don't get it.Hardwired class features make no sense to me.&nbsp;&nbsp; I don't see why they had to be designed that way.&nbsp; Could they not make the classess in such a way that they drew from a pool of class features without forcing those class features to be linked forever and inexplicably to those classess?If they are so hardwired to the classess why even have all of the seperate data bases at all?&nbsp; The wizard and fighter class both use the Bonus Feat class feature.&nbsp; What is so magical about the words Bonus Feat that force them to be used only with Fighter or Wizard classess.&nbsp; Is it 100% absolutely impossible to make that Bonus Feat actually be a free floating feature that could be added to any other list on the class features data base?&nbsp; I don't believe it.It seems so easy to implement.&nbsp; I can see it in my mind at least.&nbsp; The program itself won't even let one enter a feature that is not listed on their list of special class features.&nbsp; So one would think that drawing from this list would implement said feature in the new location as well.If I have legos and use a red brick while making a house, this does not prevent me from using an identical red brick when making a car.&nbsp; This is the way I see it.The way the data base is set up, it appears to be a pool of class features that could be added together easily enough.&nbsp; In practice it is all a lie.&nbsp; It makes one feel scammed, cheated, or even abused.I know programming is complicated.&nbsp; I know it is beyond my patience.&nbsp; But I can not see how it is so integral to the program that the class features be so tightly attached to the classess that the program began with that they cannot be used with any other classess.&nbsp; That seems to be the most ineffectual way to develope a program that is supposed to be upgradeable and may even have to reuse such prelisted class features in other classess.This rant could continue forever I suppose, though it does make me feel a little better to actually vent my feelings as opposed to destroying my computer.&nbsp; I hope the Fluid boards are up again soon so I can ask Fluid exactly why they chose to design the program this way.</blockquote>

[QUOTE="Margaiaman, post: 311488, member: 2134"] [b]Thats my problem[/b] I suppose I don't get it. Hardwired class features make no sense to me. I don't see why they had to be designed that way. Could they not make the classess in such a way that they drew from a pool of class features without forcing those class features to be linked forever and inexplicably to those classess? If they are so hardwired to the classess why even have all of the seperate data bases at all? The wizard and fighter class both use the Bonus Feat class feature. What is so magical about the words Bonus Feat that force them to be used only with Fighter or Wizard classess. Is it 100% absolutely impossible to make that Bonus Feat actually be a free floating feature that could be added to any other list on the class features data base? I don't believe it. It seems so easy to implement. I can see it in my mind at least. The program itself won't even let one enter a feature that is not listed on their list of special class features. So one would think that drawing from this list would implement said feature in the new location as well. If I have legos and use a red brick while making a house, this does not prevent me from using an identical red brick when making a car. This is the way I see it. The way the data base is set up, it appears to be a pool of class features that could be added together easily enough. In practice it is all a lie. It makes one feel scammed, cheated, or even abused. I know programming is complicated. I know it is beyond my patience. But I can not see how it is so integral to the program that the class features be so tightly attached to the classess that the program began with that they cannot be used with any other classess. That seems to be the most ineffectual way to develope a program that is supposed to be upgradeable and may even have to reuse such prelisted class features in other classess. This rant could continue forever I suppose, though it does make me feel a little better to actually vent my feelings as opposed to destroying my computer. I hope the Fluid boards are up again soon so I can ask Fluid exactly why they chose to design the program this way. [/QUOTE]

Verification