IMHO if it's for your own use and you plan to keep it private you should always feel free to play with a script to adapt it to your goals -- that's how you improve your scripting skills.
If you wanted permission to republish someone else's script with your modifications TM has some rules around that, and some people can get sensitive -- pride of authorship and such. I try to welcome feedback on pretty much anything I do and don't feel particularly touchy about your taking a cut at improving of expanding on one of my scripts as long as you give credit and do that in the thread where I published it originally. Most people are cool with that sort of thing as long as you are adding to their original publish thread.
That may be a more generalized response than you were looking for, but figured I would put it out there.
Responsive to your specific question, this is a pretty simple script and I am happy to have you play with it. I used a series of checks on the property parse I used to pull the hammers paired with "GoTo" commands that restart the process for each hammer type. I used item property instead of item types so that it would not take much to add other runic types -- although using item types would eliminate the need for some safegaurds. You could simply add to this series of property checks (below) to get the script consolidating more hammers or other runics. If this script is expanded to deal with other runic types this process ought to be reconsidered. As written the script looks at every item in the container for the property it is considering in sequence, which is not very efficient for the properties later in the que. Adding more will mean a slow start up.
I left the question of adding more runic types unresolved while I considered the best process for consolidating runics with fewer charges because of a couple of considerations, but primarily the limit of 100 uses on the consolidated runic. This script will only consolidate one runic with another and put the resulting runic in another container as written, and it doesn't optimize to the maximum 100. I was not sure that was worth doing and figured I would play with the script for a while before deciding. I stopped at copper hammers as a first cut because bronze is the first hammer that looked to me like optimizing might be worth doing. I only set up this script to combine two hammers. Optimizing and more than two hammers would require some significant changes.
That was my thought process, which I share thinking it might help if you decide you want to work on this script. NoBama has a more developed script doing the same thing that I think includes optimization and has menus, so its not a huge need. Regardless, I think there is value in looking at different ways to do things. If you want to make this script work through a bag of higher end hammers, combining two into one, just add the hammer type to the series below. If you want to go in another direction with it have at it. Happy to help if I can. Some issues to be aware: script has no check to make sure you can combine the hammers (i.e. a check for max uses), no full container, overweight checks and safeguards for random items in the source bag that have the same names as runics.
The real reason I wrote this was that I constantly toy with an unpublished script for moving items from one container to another trying to refine my understanding/scripting of that process. The property check and move process in this script is from that script and I think I left some noise code in this when I posted it.
If %NecessaryProperty = Dull
{
Set %NecessaryProperty Shadow
Goto Start_Consolidation
}
If %NecessaryProperty = Shadow
{
Set %NecessaryProperty Copper
Goto Start_Consolidation
}
If %NecessaryProperty = Copper
{
Set %NecessaryProperty Bronze
Goto Start_Consolidation
}
