This is epic, thx very much for sharing
Yep. Anyone can, at any time, walk up to the plant and press Q. It’ll catch fire and be gone.
Why?
No, seriously, I’m not trying to be flippant.
It takes 10 seconds to plant a plant, and 10 seconds to tend it after a couple of minutes (or it dies!), so you have to invest 20 seconds per plant during a planting session.
If people are willing to put in the time, why not let them?
Sure, if it turns out that the performance tests were all wrong and it’s going to be a laggy nightmare when you pass 10000 plants on the map, I’ll look into some sort of limit. If your concerns are not about performance, I’d love to hear your concerns, as you’re probably coming at it from some different angle.
2 years ago someone actually went with my idea and did something, gratz, it’s nice to see people doing nice stuff and sharing it.
Keep up with the great work.
Yes, “your idea”; even though I’ve never seen you, your video or your planting thing before.
Clearly still “your idea”, seeing as you’re the one that invented plants, planting and, most especially, weed.

Oh well, glad you like it. Would you kindly edit your post so that people don’t assume it’s a video of the script released in this thread?
The script has been made specifically to interface with ESX as little as possible, so it’s easier to change to use any framework. I don’t know VRP at all, but it shouldn’t be super hard to do.
Hi!
Any suggestions on scripts to sell the drugs you get from this? I tried a few NPC scripts but I don’t get them to work without bugs.
Thank you so much for creating a fantastic resource!
I’ve been thinking about making another script to cover that too. There are some really good ones, but they seem to all be private.
can i change the chances of dropping the seeds ?
Kind of.
In config.lua, look for YieldSeed = {0,1},
This means that harvesting will yield between 0 and 1 seed. If you set this to {0,2} it will yield between 0 and 2 seeds. If you set it to {1,1} it will always give one seed.
Adjusting the chances of getting a single seed without any chance of getting more than one, and retaining the chance to get none, is not supported.
Can’t you change row 180 in cropstate.lua to instead of
local seeds = math.random(Config.YieldSeed[1], Config.YieldSeed[2])
do something like:
math.randomseed(os.clock()*100000000000)
local seeds = math.random(0, 10)
and change numbers to what is preferred to ensure somewhat randomness?
I don’t understand the problem with the current implementation.
Randomness is automatically seeded by OS clock anyway. I don’t understand what reseeding does to ensure more random randomness here.
Besides, I like the fact that the from-to is configurable.
Please elaborate on what the upside to your implementation is.
Hi! This script is very nice.
I tried to see the config.lua and growth.lua and I wonder how I can change so the process for everything will be a little bit faster. Do I change TimeMultiplier = 1. or do I change every step in growth.lua? thank you
Continuing the discussion from [Release] [ESX] UteKnark - Grow weed outdoors:
hi i have problem i can’t use the seed
cfx> start esx_uteknark
Creating script environments for esx_uteknark
Started resource esx_uteknark
cfx> [08:54:31] <esx_uteknark> Uteknark loaded 0 plants
no error << i don’ know where is the problem.
You can adjust the time multiplier. Higher number = more time. If you want everything to take half as much time, you set a TimeMultiplier of 0.5
Please note that if you set the multiplier too low, you’ll likely have trouble planting as the first tending step will expire too fast, and the plant dies. For more detailed control, you can edit growth.lua - it’s only 6 steps.
Due to the way ESX is structured, you’ll probably need to restart your server and then make sure esx_uteknark is started before joining the server. The “UseItem” registration in ESX is a bit of a mess, and is not very robust.
Have fun!
If you make a copy of one of the files in locales/ you can make your own translation.
Just look at how the English and Swedish ones are structured, and make your own version.
Yep, this is a known issue. It checks for the items in ESX too early, so ESX hasn’t had a chance to load items yet.
This is an issue introduced by a fix to another issue, and because it’s not critical I haven’t gotten around to fixing it yet.
Thanks for the reminder, though!



