Hello There, Guest! Login Register


QuestingDebug
#1
[Important Notice]
1. Kanto should be fixed now, as no more issues were posted. I myself didn't encounter problems that are within the scripts capabilites. As such I have requested a pull into wiwi's master.
2. Regarding the other 2 regions, I am unsure when or if I can provide them in the near future. The last two weeks I solely coded for the comunity's needs, which is/was quite exhausting.
[Sidenote] Many users permanently asked me how to get things done or pm'ed me with error messages, instead of trying to solve the problem themselves or at least read the error message. I know this is asked alot of users that don't code, but everyone should at least be able to read error messages. They are written in english dammit Big Grin
I don't mind explaining, but explaining something obvious is not really much fun and wastes alot of time, in this case mine.

3. Which is why I tend to my personal scripts/projects for the time being. Kanto seemed to be a good start, where everyone surely could find some tasks for theier bots.
4. As such all issues should now be addressed towards wiwi's git project again Wink

----------------------------------------------------------------------


[Link Collection]
[QuestingDebug]

[Description]
As some already pointed out on the discord channel, I am currently updating wiwi's Questing script. Since testing those fixes, features or behaviourial changes is quite taxing doing those myself, I thought about letting everyone join the project as beta testers if interested.

Advantages:
  • you can enjoy fixes or features a little earlier than most
Disadvantages:
  • when adding features, unforeseen events are a common occurence, as such exceptions (bot stopping, looping, ...) are unavoidable
  • when using I would like you to report encountered issues, in a specfic format on top of that (see below)
  • you eventually need to manage multiple questing scripts at the same time (depends on your workspace)
  • you probably will see debug prints
All finished releases will be pull requested into wiwi's questing project, as he is the project owner. So if you want to enjoy a stable version with the least amount of effort, just have some patience and wait for updates to happen there.

For the most recent fixes, regularly check: QuestingDebug. Additionally, all worked new features are accessable via a branch from that link as well - just select desired branch in the top left above the project (see figure 1: Branches). I'll be adding all relevant branches to the link collection at the top.


[Image: branches.png]
Figure 1: Branches

[Issues]
If you decide to use QuestingDebug, I ask you to report encountered issues under QuestinDebug Issues. This will be done until Questing is in a more or less working state, at which point - reports should be attached to wiwi's project.

[Issues Format]
  • Title: I would prefer a "branchName | shortIssueDescription" format - adopt to the form of the other reported issues' title. This is needed due to no available option for branch related issue tagging.
  • Comment - pls provide:
    • Logs: add any form of log, you think could help narrowing down the error source. E.g.: Debug or normal textbox prints. Post them if unsure.
    • Detailed Information: as detailed as possible/willing. Details help a lot, when debugging.
    • Related Information: before posting, skim over it again and remove any unnecessary or unrelated information. If it is unrelated, but important it suggests itself that another issue report is needed.
    • CommitID: located in the README.md file
    • Team (regarding battle or leveling issues):
      • Level
      • Composition
    • Quest name - looks like:
      [00:11:05] Starting new quest: Soul Badge: Fuchsia City

Let's work hard to bring Questing to the next level Smile

SideNote: A few things seem redundant for all git users, but pls remeber that most community users download the projects via githubs zip function and have no access to commit information.
 
Reply
#2
Thanks for your hard work, m1l4! I really appreciate it ^^

For the bot, after 4 hrs using, I realised that this bot will capture all the pokemon and train all 6 pkm at the same time, right? Is there any way that we could focus on 1-2 pkm only to speed up the story, pls?
 
Reply
#3
Is the wiwi's questing already debugged? If no i have to put the debug files inside wiwi's folder and then it will be ok?
 
Reply
#4
(2017-09-11, 21:11:42)NightmareOnFire Is the wiwi's questing already debugged? If no i have to put the debug files inside wiwi's folder and then it will be ok?

Either this or just dowload this project - would be much more cleaner. It is a testing environment though - keep that in mind. All official releases will be done in wiwi's questing.
Status: Kanto ~90-95% done

(2017-09-11, 07:15:58)Yuyu89 For the bot, after 4 hrs using, I realised that this bot will capture all the pokemon and train all 6 pkm at the same time, right? Is there any way that we could focus on 1-2 pkm only to speed up the story, pls?

There are many ways to get that behaviour. But as I mentioned on multiple plattforms and every document regarding QuestingDebug:
*I won't do feature implementation, until after wiwi's questing is working again.*

[Reason]
I'll be doing a comlete Questing Rework at some point in the future. Since many things don't give me the necessary possibilty to get my desired behaviour easily. As such, I'll be adding new features, when I'm doing that rework. I see no reason to do that work twice.

I only want to make Questing work fast again, but as you can see - even that takes a while. Now think how long a rework would take... Many, many hours or days more.
 
Reply
#5
Got ban after 10 hours. The bot spends a lot of hours to farm all 6 pokemons and this makes you more easy to get banned but after all you did a great job.
Guys do not run the script a lot when it is farming pokemons because GMs know.

Got this error with the most recent version of the script at the start of the game. I tried to fix it alone but i don't really know what it is :3

[13:58:50] Bot started
[13:58:50] all fine
[13:58:50] Private messages disabled.
[13:58:50] Starting new quest: Start: Play the Start map
[13:58:50] Error during the script execution: Libs/teamlib.luaSad116,4-50): cannot convert a nil to a clr type System.Int32
[13:58:50] Bot stopped
 
Reply
#6
(2017-09-15, 11:53:58)NightmareOnFire Got ban after 10 hours. The bot spends a lot of hours to farm all 6 pokemons and this makes you more easy to get banned.
As I already mentioned, I will not change the script - I'm just doing fixing - that is just how the script was implemented. I myself never got banned, running the script. Could it be that the ban may be related to reusing bantagged proxies?


QuoteGot this error with the most recent version of the script at the start of the game. I tried to fix it alone but i don't really know what it is :3

[13:58:50] Starting new quest: Start: Play the Start map
[13:58:50] Error during the script execution: Libs/teamlib.luaSad116,4-50): cannot convert a nil to a clr type System.Int32
[13:58:50] Bot stopped
This was an error in the earlier stages of the fixes and was been corrected around two weeks ago. So pls do the following steps:
1. open an issue report - link is in the link collection at the top
2. add which branch and commit id you are using, as this error shouldn't be happening anymore
 
Reply
  


Forum Jump:


Browsing: 1 Guest(s)