Jump to content
Search In
  • More options...
Find results that contain...
Find results in...


  • Content Count

  • Joined

  • Last visited

Community Reputation

8 Neutral

About MSO

  • Rank


  • Sex

Recent Profile Visitors

2,040 profile views
  1. Seems like an issue with the script itself. If not, I know with some VPS services, the actual specs that they list aren't always constant. Some servers will "borrow" virtual RAM or CPU (etc..) power from other VPSs and "lend" it to other ones that may need it more, especially if the VPS they are "borrowing" from is not fully using the virtual hardware it was set up with. Your issue could be that you're allocating too much RAM and since the clients may not be using all the allocated memory at one time, it may be erroring when it's trying to use RAM that isn't there. Maybe not, but it's still an
  2. I don't remember if we have access to only the data we upload ourselves or if we get priority access to all available data. Anyways, here's some more files: http://www.mediafire.com/file/4rcq36m33w9s6mo/mouse_data.7z
  3. Oops, that's my bad. I thought you were still a mod.
  4. Okay, @Todd appears to be ignoring my questions and the issue is still unresolved. @TRiLeZ @Usa @Fluffee @Mute
  5. Just so I don't leave this unaddressed: You asked me what I was going to give to the master and I answered. I never said that that is the only thing I wanted coded in and never said that I wanted manual input removed. Also, when I said I had nothing to test it on: I was referring to a separate script to use with the Mule script, something I still don't have today. Now onto this: The summary of all of my disputes is that the scripter's ToS will be used against you at every turn and held in high regard, unless it is inconvenient to the scripter. This is exactly the response I was ex
  6. Directly after you force-refunded my 3rd script, you told me that you would be willing to add support for scripts made by other scripters for $25 each script. All you needed was their source. Shortly after, I paid Leespiker to re-create the White berry script. I've messaged Assume the Skype chat logs between October 1st - 3rd, the time where there was an update to the Mule script. The updates on December 10, 11 and 16 are all for the Air Orb script.
  7. Do you have proof that you tested the Mule script? Do you have proof that it ever fully worked? I don't remember you ever telling me that the script was finished. You did not 'explicitly' say that I could not add Mule support to scripts that weren't your own. You said the opposite, and I will supply a screenshot once I'm back at my computer. Again, I will happily share the full Skype history of October 2014 in private.
  8. A excellent observation. What does this have to do with the point I made? You can't claim something without proof and then say it was an assumption when I call you out on it. Throughout the entire month of October 2014, I never tested the Mule script nor did I post any bugs in Skype chat. Why? I couldn't and I've addressed this already... If a staff-member wants to see the entire Skype Chat history of October 2014, I will send it through PM. Absolutely untrue. I've addressed this claim multiple times now. Once again, I cannot fully test the Mule script without another fu
  9. Yes, and I did 'test' it with the Air Orb script - I let the staff-members know that I have a 4-hour recording of both the scripts running side-by-side. Except that, I could test very little of the actual script because the script spends almost all of those 4-hours in the log-in screen, and all it does after that is log in, attempts to communicate with the 'slave' and ends the script. It does not try to buy supplies, it does not try to pick items up off the ground, and it does not attempt to trade with the 'slave'. There is also no indication whatsoever that the 'slave' recognized the communic
  10. That should not and does not matter. I specifically requested this feature from the start so that it wouldn't have to be added later, and you never added it. There is nothing to argue here; the scripts are unfinished. That's partially true, but then you can't argue that I could've filed a dispute earlier because I had no way to know the full extent of what is working and what is not; or what is added and what is not - you actively refused to supply a way for me to know this. It is impossible to test every part of the scripts as is, which is why I asked you to create a test scrip
  11. This is what Assume's response was, in case he tries to edit it in the future. Assume, I have been asking you to work on the scripts since September of last year - you had refused to do anything anytime I asked. You admit that I had Lifetime Support, and also by extension admit that you had been ignoring my bug-fix requests for over a year. You will say that you were busy with school, and yet you will pump out updates for your other scripts in that same time. Just look at your past week, for example. Had you not force-refunded my 3rd script you were making, maybe. As s
  12. 1. Script Author: @Assume2. Link to Script's Thread: Deleted3. Date Purchased: August 29, 2014 (Two Scripts)4. What type of duration did you purchase: Lifetime5. Proof that you have tried contacting the author about your issue(s): One, Two, Three6. Issue(s): Re-opening because I have further proof that I had payed for Lifetime support, and that my scripts were never finished ... Still refuses to work on either of my scripts. Some Context: There are two scripts: A Mule/farm manager and an Air Orb Charging script (The Air Orb script was originally a White Berry script, but was chan
  13. 1. Script Author: @Leespiker 2. Link to Script's Thread: Deleted 3. Date Purchased: January 4, 2016 4. What type of duration did you purchase: LifeTime 5. Proof that you have tried contacting the author about your issue(s): One, Two (most recent) - Three, Four, Five, Six (earlier) 6. Issue(s): Inactive twice, back-to-back, for 3+ weeks each (and still ongoing). I asked Leespiker to specify a limit for how long he can be inactive for since it wasn't specified before (and was causing issues)... he said "three weeks" - which he has broken multiple times since specifying. He
  14. @Assume so you're saying 90-days, correct?
  • Create New...