-
You are under 24 hours muted for trashtalking our stuffs in general chat. And recommending other developers while everything is working fine for you. We never block or ban anyone.
-
You are buying an encrypted resource, and went out of your way, nit picked problems to have stuffs open so you could modify. As developers, we have the rights to say no to such requests. Scripts are delivered as it is, and is functioning as it should, encrypted. You know what youre buying.
-
How about the last time I spent the whole hour in the morning before breakfast, helping you fix a single problem. Youve said no to all my debug suggestions. Just because youre so logical and im not that you refuse to replace your inventory with mine. All that to find out you havent ensure the script? And thats after you have said mean things to us as well.
Cropped screenshots that donât show the full scope of the interaction between myself and âsleeping.â
No one was trash talking in your general chat. A conversation was had between me and another customer of yours about a different weed script and housing script. There was not a single slight to your weed script that was said. Was shade thrown? Absolutely. You closed a support thread and deleted it because there was truth being told in that thread.
As I have stated before, when it comes to communication and support, the dev working on this script was arrogant and combative when issues came up regarding the script. You even go as far as apologizing for him in one of the screen shots. It was unprofessional and did not help the situation, which caused me to become frustrated with both of you because of the responses I was given.
The troubleshooting methods you wanted me to try made zero sense. a base qb-inventory install would have made 0 difference as the inventory I was using, had the same open inventory function. Word for word. It was redundant and would have wasted time. You kept insisting and I denied as the step did not make logical sense. It was the same function.
I fully understand what encrypted entails. Yes, as the developer or what ever it is that you are for Rep Scripts, you have the right to deny anything be un-encrypted. But when you have multiple issues and inconsistencies like you weed script has shown, people get to the point where they are frustrated with a product they have bought and want to try and fix it themselves. You act like we were asking for the whole thing to be opened, which is not the case. We asked for inventory events to be un-encrypted to solve a very big exploit with you weed script (opening the inventory at the same time a slot is used to dupe the seed). You keep blaming the inventory but there are work arounds that can be done to prevent the exploit that you guys refuse to acknowledge or solve.
But none of this really matters. I have since left your discord and wonât be purchasing or using anything that Rep Scripts has to offer. You can get better functionality with more access in several different places in the community.
Hey, thats your customers rights man we dont have no power over it.
Im glad we tried our best to satisfy your needs until we couldnât anymore. Thank you very much for your feedback. If you ever needed any further help, weâre always here with open arms!
Edit: You will never be banned!!
yikesâŚ
Its a long time ago and Iâve explained to warden. 
Superb Script !! good job 
Why didnât you mention that the script is a bit buggy? Itâs not until youâve bought it (53.55$) that you find out that there are some inventory issues. Do I have to wait until you have written a new inventory script and then buy that too?
I wouldnât buy or use anything from them. One of the dudes use to deobfuscate scripts.
Why do I have to hear that itâs bad for my economy instead of someone fixing the script?
I think itâs my own decision how to use and set up the script on my server.
I really recommend nobody to buy this broken script!
The seller knows about the error but does not try to fix it! Absolute scam and was reported!!
PLEASE DO NOT BUY THIS BROKEN SCRIPT!
PLEASE DO NOT BUY THIS BROKEN SCRIPT!
PLEASE DO NOT BUY THIS BROKEN SCRIPT!
PLEASE DO NOT BUY THIS BROKEN SCRIPT!
you might have an installation problem, thats why your weed not drying thats it. I responded to you on Discord 
Read your own readme.txt. Check out my screenshot above⌠You mentioned there is an issue with the inventory. Believe me there is no installation problem. Iâve been developing in multiple languages ââfor 21 years. I have enough knowledge to install a simple script. Please donât make excuses, mention your readme.md in your Tebex store and just be honest! You have a problem with the script, you canât solve it and you hide it to make money! If you want to keep your honor then fix the script or at least let those who know do it! Open the code and at least give those who paid you the money and gave you the trust you broke, an opportunity to mend your lack of knowledge!
Just be honest and stop selling people broken stuff. Stop claiming that the customer has a problem with their system when they complain! You made a video which shows itself that itâs bugged!
To everyone else: Here is the original readme.md of the script, where the developer explains in the first lines that there is a problem with the inventory and shows a video with a suggested solution to dry the weed.
README.md (2.3 KB)
GIVE EVERYONE BACK THE MONEY YOU LIED TO MAKE PROFIT!
The fact that there are customers who complained about exactly the same problem a month ago shows that the developer is unable to solve the problem!
As already said: Place an NPC somewhere that triggers the event, to which you have to give the weed to dry it and you have to pick it up after time X and thatâs it! That would be a temporary solution and the script would work for now! So nobody has to buy a broken script and have it lying around for months until you make a new inventory, which you will definitely have to sell again for overpriced money!
By the way, if you used markedbills with item info. Items wont be able to stack. Its just how the inventory works and we made it work around it.
The readme clearly says that. It doesnt mean weed wont dry or script not working or anything. It should work like how the other hundreds of customers are enjoying.
Do you trolling me? For real bro, do you? You sell broken scripts and you are not able to fix it in a whole month!! Maybe the earlier version worked, but not this, iâve bought!
It doesnât mean, that the script works, if you have to put the wet weed 100 times in my stash, until it will be recognized and start to dry!
Fix it, open the source and let others do or refund!!!
AGAIN TO ALL OTHERS: THIS SCRIPT DOESNâT WORK, PLS DONT BUY IT FOR NOW!!! STOP BEING SCAMMED
You took 9hours to respond to our message but only a few minutes to make such a feedback.
If you see this, please provide us with further information as seen in the photo and we will see whats going on!
Here is a simple concept to understand. If you donât want negative reviews, donât make a shitty product.
Sorry, that my mate sleeps at night bro. Please show the whole messageâŚ
You know the problem! There is no error code, your wet weed did not dry in stash! It is, how you have written it in your readme. Place a NPC which one dries the weed and the player can pick up after a time. That is the temporary solution for your problem!
Invest your time to fix the problem to avoid just such negative info.
I would never say anything if I was to blame for something! Especially since there are other customers here who have exactly the same problem and have not received a solution to this day. Just please do your work or give it to someone who can. Otherwise there will also be other customers who complain. Itâs up to you how this looks like. Nobody spreads false news, only negative ones because they are true.
I have no issue with this script. Script works great, just follow readme files to install script. You have to edit your inventory script to be able to dry buds, but there was no problem while using ox_inventory.
Update 2.0, officially supporting ESX now, enjoy guys!
wateringcan does not work.
