Free-form field entry suggestion - Printable Version
+- STO Academy Forum (http://forum.stoacademy.com)
+-- Forum: Skill Planner (http://forum.stoacademy.com/forumdisplay.php?fid=25)
+--- Forum: Skill Planner Bugs & Feedback (http://forum.stoacademy.com/forumdisplay.php?fid=28)
+--- Thread: Free-form field entry suggestion (/showthread.php?tid=5562)
Free-form field entry suggestion - Tritium - 12-27-2018
The skill planner doesn't use item properties to calculate anything. It doesn't use anything about the item, really, except for the picture and that doesn't even show on the summary page most people share. The planner is always going to lag behind reality, that's just a given. I would suggest a few small changes that will allow someone to create any build, even when game patches add new properties, items or traits.
My suggestion is this: a free form field for properties, and an "Unknown" item in each category where the user can change the name. Give it a question mark icon perhaps.
As it stands, there is really no reason other than convenience why item properties (Dmg, CrtH, DrainX, etc) have to be selectable from a drop-down. In fact, there are so many properties that I find the drop-down selection process is actually more tedious. I would suggest that all item properties be changed to a free-form format where you can just type in the property and then select the multiplier. At the very least, perhaps it can be a drop-down that also has text entry/edit capability.
Secondly, if you put in an Unknown item in each category where the name is editable, then anyone can add items to their build which are currently missing in the planner. As a bonus, periodically the maintainer can search for all the item names that people have used the unknown entry for and then you will have a list of items that are missing that need to be added. This will mean people don't need to make a forum post for each missing trait, weapon, item, or property.
RE: Free-form field entry suggestion - Attilio - 12-28-2018
Thanks for the suggestion! I'll take it into consideration for future updates.