No good reason but I forgot to have it check it also. It only checks the real requester name and real title. I'll make it search the friendly options also in the next update. Not sure when the next update will be because I'm testing a few new things I added.
Be sure to read the help menus. It explains a lot and gives some great tips. Also there are a lot of tips in this thread as well. I am not sure if a video tutorial would help much but I'll think about it once I have finished the script completely.
First be sure the border around the job box is solid. If it's dotted then it's muted. Right click on the job box to unmute it or unmute in the details window. Also be sure the volume slider at top is all the way to the right. Be sure tab is not muted also. If all that is good go to the alarm options and press the play buttons on the alarms to see if any of those work. If it doesn't work then click the change button and choose a sound file. Any sound file will do. It should play that sound after you choose the file. The default alarms is just a url directly to the sound file on a server. Just click on those and save it to your computer. Then use the file you just downloaded to change the alarm. The @connect stuff is only if the alarms don't work when you first install it. All the sounds are put into memory and saved on your computer. If it still doesn't work you can try pressing [ctrl] [shift] [J] which will bring up the console and if you see any red errors then that could be a problem.
@Johnnyrs This is very impressive. Thank you!
The search mode will go to the requester search page for any of their hits with highest paid first. It will only save the first 3 hits found and panda each one. It will actually change the group id # each time it tries a panda. Once it finishes all the stuff it found it will go back to the requester search page again and repeat the process. If it found only one hit then you can make it only do that one hit without going back to searching by clicking on the job box so the border turns red. This makes it only panda the found hit until you restart the script or click the box again so the border goes to regular color. This feature can also be automated if you put the job in delayed ham mode. In delayed ham mode it will only panda the hit found if it found 1 hit until it can't collect anymore. Once out of ham mode it will start searching again. It could be useful for C-Sats but sometimes they will drop a few hits so it will only try the 3 highest paid hits. If you already capped on those then you might have to add the rest of the panda's.
I didn't see anything about it, but is it possible to save requester searches? You used c-sats as an example since they use different ids. so is it possible to save a search for c-sats (or any other requester) like the watch this requester feature on TM? or do I just have to search their requester id every time I want to look out for them?
Yes It's a bug. I'll have a fix for it today sometime. You can go back to the earlier version 0.3.1 or 0.3 from the history tab on greasyfork if it gets too bad. You can also press the pause button and resume which starts the timer working again.
I have no idea why thais would be happening. I didn't change anything in the tabs for this version. If you have a screenshot of it I might be able to understand what is happening. Could also go back to an older version like 0.3.1 or 0.3 from the history tab on greasyfork. Could also try exporting everything and importing it again. See if that fixes something.
You can send it to my email address in the script source. It's on line 5 starting with // @author. The email address is at the end of the line. You can go to Panda Script Source Code on Greasyfork.
Yeah, I tried to print page and save it as a pdf, but it wasn't showing the issue as it was displaying the ones I had at the top which were fine. (it wanted to print 2 pages)
by any chance does it look like this? or different issue?
