PLUGINS TO HEARTHBUDDY -plugin: relogger .dc/hearthstone down detected -> launch hearthstone though blizzard launcher .relaunch hearthbuddy -> -plugin: automatically start botting hearthbuddy | desc: after hearthbuddy detects problems with hearthstone leading to automatic relaunch and automatic starting of botting -plugin: arenadeckdraftmode: preferred classes/custom classes ,rush/control/spell/custom drafts.. | choose your favourite botting arena drafts and classes -plugin: rankeddeckmode: aggro/control/cuostom deck | desc: choose your deck and playstyle when playing rankeds -plugin: autoemote: click greeting emote at x time, click well played at x time, click random emotes at x time. -plugin: humanitizeplugin: timers on every action from x to y | desc: random timer from values between x to y to every action made HEARTHBUDDY need new discussion ares: /ARENA Discussion OR /SUCCESS stories /REPORTS /SUGGESTIONS -talking about arenadrafts -custom classes etc.
Relogger cannot be a plugin. Hearthbuddy must attach to an existing process, and will close when that process exits. As a result, a dedicated relogger must be used. We will look into a dedicated relogger that uses the Battle.net launcher in the future, as it will be useful for other games as well. The Heartbuddy application already supports command line arguments for auto-starting. However, more command line arguments will be added as needed. The idea will be to switch to a configuration based system, so you can setup a configuration, and then simply launch it as needed depending on what you want to do. For an example of how this system works, you can look at the Exilebuddy User's Guide, which has the system that will most likely be used. In addition, I would like to add profile support for playing games, so users can setup profiles to level all basic characters to a certain level, or play casual games until a certain rank, be able to add in delays between games, etc... Those are all good examples of features the bot we provide should offer. * Arena drafting will use a new system in the future so users can have custom logic to do just that. * Constructed play settings are based on the AI being used, so a setting for that doesn't make sense. If you're using a Control AI, then it obviously can't play Aggro. * Emote features will be supported, but randomly using them is not human like behavior. As I've explained in another reply, "randomness" is not human-like behavior, so you need custom logic to properly handle using emotes in a believable manner. * Delays before or after actions comes down to using an AI that offers those features rather than the bot controlling it. Otherwise, you'll notice odd behaviors like you'll see in the Beta where if oyu play a card and delay, and it has a targeting arrow, then the action to use the targeting arrow is delayed longer than it needs to be. In short, the AI implementation needs to perform actions in a human-like way, as the bot itself doesn't do the AI; it just offers the API to perform actions. I'll talk to Tony about some of these, but I don't think we need those exactly: * Ban report section should be added. * I'd be fine with a suggestions forum to have one place to organize feedback. * Success stories section isn't needed; General can be used. * Arena discussion isn't needed as a Community Development section would be needed first for relevant discussion about making new logic to handle them correctly. * For custom classes or deck construction, there are certainly other sites that offer useful information and discussions about, so I'm not sure that would fit here, but I'll see what staff thinks.
Well that was hell of an positive answer, first of all I thought it was wall of text, but as indepth it has reached much higher level in discussion than I've seen on -buddy forums ever so 2 claps to that. This should be done as prioritized as follows: I want to say first that these were plugin raw-ideas, it wasn't necessary to be a plugin since (sorry for saying this) you lazyasses haven't even added plugin support to hearthbuddy yet and godknows how long the idea and hearthbuddy had been existing. To do ->3-6.-> steps takes about 20 minutes of forum admins time and pretty much satisfies a whole lot crowd in here. Relogger can be a plugin: Plugin or the bot detects problem with hearthstone client -> plugin quickrestarts hearthstone (through given details) and hearthbuddy (almost simultaneously) -> plugin always autostarts hearthbuddy(buddying) when hearthbuddy is launched. Random emote and greeting emote and wellplayed emote at times x actually is humanlike behaviour and randomizing anything in AI is closer to humanlikebehaviour than AI behaviour so that makes your argument invalid. You might not understand this plugin proposition the way I do, I see it as a list where player chooses emote and chooses times x and y for the listed emote (table like UI where is 3 tables: emote, mintime, maxtime) (this image might explain it better than my not-mathertongue english http://www.pronic.co.id/sites/defau... Hasil Komparasi, Sept 08, english_resize.jpg , just replace the top "text" with previously said emote, min time, max time and bot makes random timer from those values) This is basic AI programming to make it humanlike movements, timers for these basic functions should be made also as min,max timer but with much smaller values taken a median from human play (requires one time tracking human play of the game with writing down the timer values) Explain profile support for playing games? Making user friendly profile editor is very good idea IMHO. also should be prioritized as seen in hearthbuddy developers community. Can you explain this also a bit better maybe indepth (no need to reveal "secrets") I just didn't understand what you ment? Did you mean player can make profiles for valuing cards per class in arenadraft? As to end this post, before the buddycommunity comes here to praise this whole thread, I want to say that I could do all of this in matter of weeks for X sum through paypal that message you can deliver to Tony and Big-Tony will find me.
When it comes to project setup, how a project starts, rarely lasts as time goes on, and the needs of the users change. It has nothing to do with laziness though, but rather the current vision of a project needing to be "refreshed", which is what is happening now. We're making some big changes with the project now, because we see a lot of room for improvement, and the popularity of the game warrants it. The issue isn't how long, or in this case, short, it takes for something to get done. It's more of an issue of realizing the need for something in the first place. Before you brought up the issue, I can't say I've read any threads talking about the same thing (then again, I've only spent so much time browsing the forums to get an idea of what needs to be done, so I might have missed them). Most of the community concerns I've come to understand, are with the bot itself and how it interacts with the game. "Easy" things, like forum issues, are handled by other people, so it's not problem at all communicating to them we need something changed, if it needs to be changed. Consider the scenario of you being on life support. You have two options: 1. You monitor your own vitals, and alert the doctors if they are failing and intervention is needed (might be hard to do since you're dying). 2. A machine/person monitors your vitals, and alerts the doctors if they are failing and intervention is needed. You're suggesting #1, and I'm saying that #2 is how it's done in practice pretty much everywhere. The only client issue that should happen is a crash, and a crash would take down HsB. If there's a bot issue, for whatever reason, be it crash, freezing, or getting stuck in an infinite loop, the plugin code to execute the relogging logic would not execute. An external monitor to manage all that is a must. You'd have to check the profile section of Honorbuddy for the concept, but the idea was to let users do something like this: GrindPracticeMode.xml Code: <?xml version="1.0" encoding="utf-8"?> <Profile Name="practice" Author="Bossland GmbH" Version="0.1.0.0"> <If Condition="HeroLevel(TAG_CLASS.WARRIOR) < 10" > <SoloAdventure GameType="PRACTICE" GameMode="NORMAL" DeckType="BASIC" DeckClass="WARRIOR" OpponentClass="DRUID" /> </If> </Profile> In that short profile example, the bot would start a Normal practice game using the Warrior basic deck, against a Druid, but only if the level of your Warrior basic deck was < 10. In essence, users have an easy way to control the game creation flow of the bot, as opposed to having to change GUI settings each time. I can't say there's "an easy" way to have profile development, other than just using a text editor and learning the features provided, but we'll always keep our eye out on ways to improve the work flow. Sometimes though, in an attempt to make things "easier", you end up making them a lot more complicated than just taking the simple way out. Lastly, thanks for the offer for work, but if Buddy is looking to hire, I'm sure the people in charge of that will contact people as they need.
This could be done with a process within a process, when 1st process crashes it autolaunches second process to restart that process and through this loop it is possible to develope relog plugin or even relogger inside the process (settings for example) My claim explained in your examples' way: 1. machine monitors your vitals, if it crashes it relaunches through backup process and so it doesn't alert anything until there is actually vital situation. Believe me when I say this: in coding pretty much anything is possible it is only limited to the coders know-how. Regards, Thank you for your reply and time Ps. everything I've written is based on spent time: ½ hours on forum and ½ hours of observing the bot. Seeing there is no settings at all for user to custom and nothing of basic things (that I even had to propose) in this program. Leads to conclusion that it is ridiculously badly launched. (no offend attended, it's constructive feedback which you can see in the whole thread and compare to the time I've spent on this whole thing: 1 hour of observing hearthbuddy and forums.) Pss. I know that Blizzard is very keen on catching every injection of any blizzardbuddy programs I really hope you guys got real good coders there to make sure the injection will never be detected. Leading users not getting banned by using the program but by getting reported and thus
Maybe just use Hearthlogger ? ps: Try it some time. Then, if there will be suggestions on an improvement, welcome to the that thread. I will help what I will be able.
