Some addition suggestions:
Pathing tab
Add a Clear all Nav Points button
Assign an auto feature (button/checkbox) and distance there. (huge help)
Perhaps add a feature to walk through the points, allowing someone to stop on a point and assign them labels so you can check your path.
Perhaps add test window listing points in order from Start to Finish that you could select and travel to.
Perhaps add an option to reload from the pathing file in case you screw up and want to go back to the previous version befor you save your changes.
Other tab
Seems interesting, but I'm unsure what the bottom two are for. (Black List & Friends List)
Collection would be nice if it only held on to those collections you were missing items from. If you could query it, that would be a bonus so it autoupdated.
Options menu
I really like this one. You did a great job here. Only think I can think of is maybe better organization, but that's nitpicking.
Main
Very well laid out.
Perhaps add an option to specify that a cluster be harvested, but only rares kept. (or make it clear this is done when harvesting is checked but keep amount is set to 0, etc.)
Non-Tab specific
Perhaps add a [?] with some context help on each screen to help with possible configuration examples or explanations of features per tab.
Maybe add another tab to track a list of names of people of interest. If someone is mining a node and you programatically skip it, add their name to the list or if it exists already for the same reason - increment the count on them. Reason field could be things like: GM tell, CS Tell, Node Proximity Avoid, etc. Of course you would need a clear button for these names as well.
Perhaps add an option to check if packs are full and invoke the destroy/cleanup routine to try to make space before forcing a end to the harvesting session.
Perhaps you can check the harvest target's Z-axis value when you initially find you can't get to it. If the difference in the Z-axis is > a configured x amount, consider the node bad due to things like overhangs, cliffs, etc. This would keep people from dancing along the bottom of cliffs and walls, etc. until the node fails while possibly trying to get you suck in somewhere.
That's all I can think of for now. It's great you keep developing this script. I really like the update to it so far.
~Cosmo
Pathing tab
Add a Clear all Nav Points button
Assign an auto feature (button/checkbox) and distance there. (huge help)
Perhaps add a feature to walk through the points, allowing someone to stop on a point and assign them labels so you can check your path.
Perhaps add test window listing points in order from Start to Finish that you could select and travel to.
Perhaps add an option to reload from the pathing file in case you screw up and want to go back to the previous version befor you save your changes.
Other tab
Seems interesting, but I'm unsure what the bottom two are for. (Black List & Friends List)
Collection would be nice if it only held on to those collections you were missing items from. If you could query it, that would be a bonus so it autoupdated.
Options menu
I really like this one. You did a great job here. Only think I can think of is maybe better organization, but that's nitpicking.
Main
Very well laid out.
Perhaps add an option to specify that a cluster be harvested, but only rares kept. (or make it clear this is done when harvesting is checked but keep amount is set to 0, etc.)
Non-Tab specific
Perhaps add a [?] with some context help on each screen to help with possible configuration examples or explanations of features per tab.
Maybe add another tab to track a list of names of people of interest. If someone is mining a node and you programatically skip it, add their name to the list or if it exists already for the same reason - increment the count on them. Reason field could be things like: GM tell, CS Tell, Node Proximity Avoid, etc. Of course you would need a clear button for these names as well.
Perhaps add an option to check if packs are full and invoke the destroy/cleanup routine to try to make space before forcing a end to the harvesting session.
Perhaps you can check the harvest target's Z-axis value when you initially find you can't get to it. If the difference in the Z-axis is > a configured x amount, consider the node bad due to things like overhangs, cliffs, etc. This would keep people from dancing along the bottom of cliffs and walls, etc. until the node fails while possibly trying to get you suck in somewhere.
That's all I can think of for now. It's great you keep developing this script. I really like the update to it so far.
~Cosmo
Last edited: