If you're going to give examples, please let them be informative descriptions about the broken randoms, so that we can update this list. ^.^

were you not aware of the random event error section? i've posted at least 5 random event errors in there, with pictures and detailed evidence and somehow the whole thread seems to have been replaced by this, easy way to say 'cba let's just stall a bit more'

were you not aware of the random event error section? i've posted at least 5 random event errors in there, with pictures and detailed evidence and somehow the whole thread seems to have been replaced by this, easy way to say 'cba let's just stall a bit more'

 

link me to the random bug reports you made and ill add them in, at least 5 of them ^_^

link me to the random bug reports you made and ill add them in, at least 5 of them

the thread seems to have been deleted (surprise surprise), if people are going to delete my reports i cba giving reports anymore lmfao, i'll just watch this fall apart.

the thread seems to have been deleted (surprise surprise), if people are going to delete my reports i cba giving reports anymore lmfao, i'll just watch this fall apart.

 

then dont complain if you're not going to help.

 

The previous thread was hidden, so as to reduce the confusion between having the two threads open.

I looked, and it seemed the latest random reports were for version 2.2.10, as we are now on v2.2.12 I'd like to see some recent reports on the randoms. I don't want to add a broken random report from version 2.1.7.

 

If you have recent broken random reports (on the current version) then post them.

If you'd like to see them fixed, then doing this will help. Not sure why you're so against it. I went through the last two pages on the previous random report, and added the common errors that I saw. (max random being most prevalent)

I can unhide the thread if you need to go through and find your previous bug reports, but again, I'd like to see more current reports (2.2.12) as to avoid saying something is broken, if it really isn't.

 

I can unhide the thread if you need to go through and find your previous bug reports, but again, I'd like to see more current reports (2.2.12) as to avoid saying something is broken, if it really isn't.

i really cba anymore, it seems like all of you try to sweep issues under the carpet

no offense but there's no point in this, there's a random event error section which NOBODY reads, with ALL the errors there, yet NOBODY has fixed ANY random.

there's nothing we can do, we've reported everything, we just need one person to actually do something

@FrostBug said he would help out once he gets access to the randoms. Not many of the scritpers have access to the randoms, or we would help out. The developers are rarely on themselves to fix it.

then dont complain if you're not going to help.

 

you're precisely right tbh it's my fault for even trying to speak up and get something done about randoms, i won't say anything anymore

Edited August 16, 201411 yr by Realist

edited OP to have client version and changed colours so it is easier to differentiate. ^_^

i really cba anymore, it seems like all of you try to sweep issues under the carpet

I'm sorry

could "Please post any bug reports on this thread here, so that we can update the list." be more clear?

I went through the last few pages of the previous thread. Do you know how many posts there were about 2.2.10?

5.

4 of which were about the maze random.

 

Do you know what the maze random is labeled as on this thread?

Buggy.

 

Do you know why?

Because the reports said it was broken, while I've also seen it work perfectly fine (I've also been on the not working end)

Therefore, it works sometimes, but is not fully functional. Hence - Buggy.

 

So explain more why we're trying to sweep this under the rug?

Could you tell me which randoms are broken, and why?

If you can, we will update OP.

If you can't, could you tell me why not? Something more than "nobody is trying" considering we clearly are trying with this thread that you're bashing instead of helping.

You're literally complaining about having to post three lines of info

I want to reiterate that.

You're complaining because scripters won't look through hundreds of lines of code

while you won't even post three lines of information.

 

I'd like people to refrain from posting negative answers to this thread, if you're going to post, please let it be an informative bug report about a broken random, or "I experienced random X, and it worked fine." so we can change it from Broken to Buggy, or from Buggy to Working.

Thanks.

I'm sorry

could "Please post any bug reports on this thread here, so that we can update the list." be more clear?

I went through the last few pages of the previous thread. Do you know how many posts there were about 2.2.10?

5.

4 of which were about the maze random.

 

Do you know what the maze random is labeled as on this thread?

Buggy.

 

Do you know why?

Because the reports said it was broken, while I've also seen it work perfectly fine (I've also been on the not working end)

Therefore, it works sometimes, but is not fully functional. Hence - Buggy.

 

So explain more why we're trying to sweep this under the rug?

Could you tell me which randoms are broken, and why?

If you can, we will update OP.

If you can't, could you tell me why not? Something more than "nobody is trying" considering we clearly are trying with this thread that you're bashing instead of helping.

You're literally complaining about having to post three lines of info

I want to reiterate that.

You're complaining because scripters won't look through hundreds of lines of code

while you won't even post three lines of information.

 

I'd like people to refrain from posting negative answers to this thread, if you're going to post, please let it be an informative bug report about a broken random, or "I experienced random X, and it worked fine." so we can change it from Broken to Buggy, or from Buggy to Working.

Thanks.

cba reading any of that, but yes you are right sir

Frogs:

• Status: Unknown.
  
• Client version: none.
  
• Issue(s): none.
  
• Last updated: 14/08/2014
  
• ​Don't work  on 16-8-2014 it ignore the frog to long than the frog teleports you to the cave and than it logs out and stop the script.​
  

Surprise Exam:

• Status: Buggy.
  
• Client version: none.
  
• Issue(s): NA.
  
• Last updated: 16/08/2014
  
• ​Don't work get the radome than straight away it stops the script and log out 16-08-2014
  

 

Thanks

Should probably add that it's easier to fix if we have access to accounts stuck in the broken random.

Niles does not work

 

Giles does not work

 

Miles does not work

 

Drunken Dwarf (ignores him) does not work

 

Genie does not always work

 

Frog Princess buggy, has to get teled to the weird frog place

 

Maze (doesn't touch the shrine)

 

If anybody has an account stuck in the maze random, please drop me a PM (If you're willing to let me access it)