Originally Posted by Rosethorn
About collaboration with Vulajin, I truly hope he decides to take my sheet and update it instead so I don't have to produce a new one every time he does, but we have not talked about it.
|
This is not going to happen for three reasons:
- It breaks OO compatibility.
- I consider such features unnecessary fluff; I'd rather spend my time developing the actual calculations to be accurate. Other people are perfectly free to add such features, but I prefer they do so separately because I would rather their features did not become part of the updating process. As it is, I can churn out an update to the sheet very rapidly because I know every nook and cranny of it, and also because I don't have to go through someone else's work to make sure my changes don't break anything. I'm not interested in losing that.
- Saving talent builds is completely against the point of the sheet, which is to encourage people to figure things out for themselves. It's the same reason why the sheet doesn't just model specific cycle permutations such as 2s/5r, but rather entire classes of cycles for which you can specify any number of CP. If you have a bunch of saved talent builds, you're more likely to just choose one of them rather than do even the most rudimentary experimentation to figure out whether there might be a more optimal arrangement.
With that said, I'm extremely appreciative that people seem to like the sheet enough to develop modified versions or additions to extend its functionality to include these types of features. As long as the calculations are accurate and are being used in some fashion, be it through my original version or through anyone else's modified version, to help rogues gear and perform optimally, I'm happy.
(edit) I realize that my third point addresses something that isn't actually implemented in Cherubael's version of the sheet. Still, the argument can be generalized. :p