Well the script does warn you what the variable got renamed to, doesn't it? If you can write a small remote like that and know what a "remote" is, you would surely know how to make a simple edit such as to add "(2)" to the end of your variables, right?
This variable name is dynamic. It could be %variable(2) one time and %variable(3) another. I dont care if it warned me. It doesnt change my code. If I write code and when I test it I see a warning, "I rewrote your variable so now your code doesnt work". Should I go rewrite my code for that one dynamically changed variable?
It's a nice idea and a good attempt, please don;t think Im flaming you or putting it down, but the cons definitely outweight the pros in this case. The case that hixxy brought up about not being able to use /var and the halt sealed the deal for me though.
I and I'm sure everyone else appreciates your effort for tackling an issue. I agree with the person who said name your variable so it wouldnt get overwritten. Thats the best idea.
Also, my script has a hash table with switches and such in it. General informationthe script needs, I use this in place of variable many times. Not saying this is THE WAY, but it is a way I can secure that people will not mess up my switches and code.
