When you give these fixes, you ramp up dilution of consistency. This means, you create more work for yourself later by not really knowing what code-base people are using anymore. It confuses users basically because it appears hastily written, like not enough testing was done. You have run-on posts, where you yourself merely post again (ie, post bumping), rather than just editing your post to add more, if you are the last one to post this will not show (edit) beacons to others like a revised post would. Doing it this way can go cleverly below radar.
And yeah, I am clearly an asshole at times and I agree. At least that's something we can agree on. I know caeser agree's with me. He thinks I didn't catch that post he "junked" on my behalf. But to be honest, that was a "pre script". It was a "warez" script. Rules are rules not just to look pretty. I thought they were to be enforced, but this is taking me off topic too far... So let's stray back..
I meant no disrespect to what you are doing. Go ahead and keep right up doing that, split thread is easier for me to understand exactly what I am fixing and keeps conversations from merging and cluttering up my build table.. heh
This is why my version shall always be "v2.01x" always that same version, over and over. Because ramping isn't what I'm intending to do. To know if you have the most recent copy of it, simply check the release date and compare against your own. If it's newer take it.
And about that unreleased version. To clarify a bit, it is live, anytime you want join efnet and #roms-isos and try various things against it. The one-boxes I still have yet to fix, there is more to the script than simply google.
Hopefully you are using something similar to webby to do all your work. This is why webby exists primarily. To help me fix the google script. And on that I'm out.. Sorry if I pissed anyone off, sometimes I do that... enjoy the scripts even if you wish you could launch a brick into my face.<speechles> !webby http://www.google.com/search?q=ixtreme% ... f-8&nfpr=1 --regexp class="g"><div.*?<a href="(.*?)".*?">(.*?)</a-- --override
<sp33chy> regexp: capture1 ( http://www.ixtreme.net/open-forum/16382 ... cutor.html )
<sp33chy> regexp: capture2 ( iXtreme Burner Max Official Tutorial from Team Xecutor )
<speechles> tuh duh
<speechles> !webby http://www.google.com/search?q=ixtreme% ... f-8&nfpr=1 --regexp class="g"><div.*?<a href="(.*?)".*?">(.*?)</a.*?class="g"><div.*?<a href="(.*?)".*?">(.*?)</a.*?class="g"><div.*?<a href="(.*?)".*?">(.*?)</a-- --override
<sp33chy> regexp: capture1 ( http://www.ixtreme.net/open-forum/16382 ... cutor.html )
<sp33chy> regexp: capture2 ( iXtreme Burner Max Official Tutorial from Team Xecutor )
<speechles> 3 differing results plz
<sp33chy> regexp: capture3 ( http://www.ixtreme.net/console-news/162 ... orial.html )
<sp33chy> regexp: capture4 ( iXtreme Burner Max Tutorial )
<sp33chy> regexp: capture5 ( http://www.ixtreme.net/ixtreme-lt-lite- ... nload.html )
<sp33chy> regexp: capture6 ( iXtreme Burner Max Download )
<speechles> kk, thats how it should work
<speechles> webby is bombastic
<speechles> thanks webby, i just fixed google usin' u
I can promise that the url: http://ereader.kiczek.com/incith-google.tcl
This will contain my unreleased copy later tonight. My physical copy differs far from the actual production copy I release. My physical copy has extensive debug it sends me so that I can tell when one-boxes are caught incorrectly, and the whole she-bang. I just haven't released it because it slows the entire script down 10x and is only useful to know which parsers pick up what.