-
Posts
37 -
Joined
-
Last visited
Posts posted by veza
-
-
10 hours ago, MisterJay said:
Hey G, could I get a reset on the trial? I didn't realize the account I wanted to use was not yet 82 magic so I did not try further- account is ready now. Much appreciated!
Thats been reset now
-
19 hours ago, turk4life321 said:
Can I get another reset please? I couldn't manage to get a successful run, I kept dying even with good gear on. I need to figure out settings. Unfortunately the 2 hours wasn't enough for that.
Ok, its been cleared
-
2 hours ago, turk4life321 said:
Can I get a refresh on the trial? It was bugged for me and I couldn't get a run in.
You can use a trial again now
-
6 hours ago, its fatalgoat said:
i cant get it to work, i click start and it tried to load a mage load out then have melee in the bags and my bag fills up and it just keeps empty and reloading em
Please submit a bug report in our discord
-
9 hours ago, scum x said:
script must be bugged. teles to chasm then uses house tele. over & over again. have been using the same settings for the last few days.
Please submit a bug report in our discord
-
2 hours ago, secret dipper said:
6:10:15 AM: [SCRIPT] Missing supplies: Fairy Ring Staff near bank: true, Cycle Diff: 25, Sys: 1747372215289
Fixed in latest release
-
38 minutes ago, 2name said:
** 2025-04-25 14 h 04 min 34 s (renewals enabled) 3 minutes Unlimited
i wish an refund , barbarian assault , he's not workin well good ,i go join world 306 ,to find an party ,buti think all are used bot and are still busy , because all player waiting on square 1 , i saw many player waiting like busy with this bot or other ,because im config it correctly "and the bot still on "null" option so everyone around are busy of this step , so yes bot are using but less 5minute.. -,- its really not working
World 306 is the official barbarian assault world, real players go to that world to do the minigame. The script will never log in to that world. All you have to do is start the script and wait. I am not sure how you would be able to identify that the script is broken in only 3 minutes of runtime.
-
What is misleading?
-
Yeah, lamps were the best, as we previously did not consider volume.
-
Can confirm that Duke works properly, we're waiting for a video to figure out what's going on
-
Turn noob mode off, under antiban settings.
-
I added a scroll pane for the next release, will be resizeable to any size. Should resolve this issue.
Sorry for delay, I was on vacation and I typically do the GUI work. Due to the delay, @Nuclear Nezz I believe we should add 7 days of instance time
-
None of us directed you to submit a refund.
In the picture provided it completed wave 1 and started wave 2, what is the issue?
-
"after days of tickets being closed or ignored"
Your ticket was open for a total of 26 hours. That is not even close to being ignored.
You get a private message on discord from the bot after your ticket closes explaining everything.
You refused to read the message sent to you from the bot multiple times. The exact message sent is as follows:
Since you apparently submitted 4 tickets, and 3 of them were closed, you would have received this message 3 times. -
"Ignore you for hours" correct, we are humans & sleep.
You submitted a report yesterday & it was handled yesterday. Your issues were: Not enough gold on the account, hence why it was using the GE more often - as there was not enough gold to buy sufficient supplies.
As for not selling loot keys, that issue has not been reported.
Though, from your logs, it would appear that it's because you were consistently stopping the script - prior to the script being able to sell loot. When the script then starts again, how can it know that the loot is from a loot key?
-
-
Please submit a bug report, we will fix any and all issues
-
Bans arent a valid reason to get a refund.
Though, I would like to know what kind of inefficiencies you have noticed. Both of those scripts perform exceptionally well. Please make a script suggestion in our discord about potential improvements you would like added.
-
Also, that is expected behavior.
The script is functional, it's selling loot, it set your gearset with our dynamic gear, and it's restocking. Nothing is broken. As mentioned above, you can customize all of this.
-
Hi,
GBlastFurnace does make bars at the blast furnace
-
We've had tons of fire cape completions, and no bug reports on it in months.
I am skeptical to believe that you've been unable to complete a single cape in 31 attempts with 90 range.In any case, assuming your screenshot is from a recent failure:
- 702 tokkul means you died on wave 27.
- Wave 27 has 1 melee, 1 ranger, 1 45 and 2 bats, which the bot would most definitely have no problems completing, even on a pure with significantly worse stats.
- Your screenshot also has zero prayer, while having super restores in the inventory, which definitely would not have happened under normal circumstances. There's nothing that takes priority over restoring prayer in the script.
- There's significant supply usage for such a short period of time in the cave. Especially given that you're using a blowpipe, you shouldn't even be using any food until wave 53.The only reasonable explanation that I can think of, to be dying this often & early would be immensely high ping, severe lag and or fully disconnecting.
Please submit a bug report in our discord: https://discord.gg/gscripts preferably with a video so we can identify how it is failing. -
We haven't heard about any issues with woodcutting until now.
Muling:
All of our scripts use the same muling logic, and muling is definitely working fine. Most likely user error - would need to see logs to know.Can't run more than an hour:
There's nothing I can say without seeing logs, which have not been provided.As for nests, we'll add that in. You can also make script suggestions in our discord, all of which are read and implemented if they make sense and are reasonable.
-
What is the mistake?
-
Discussed on discord, user has already had scripts swapped.
Refund request - GZombiePirates
in Request a Refund
Posted
This issue is fixed in the next release.