Ok Macro Monkey uses Polling as apposed to event driven input.

So basically a poll looks like:

function poller()
checkhp()
lookformobs()
--meats, potatoes, gravy, and so on
end

ReqBot does this in a more organized way, using included files, and conditional statements, but hopefully you get the point.

Then with a timer you run that poll often, in the case of reqbot its 13 times a second I believe.

To see the main poller, look at SoloMain.mms
Now obviously you'd want your "party hp check" function to be within the scope of the poll, but more relevantly placed so it's not being checked when it doesn't need to be or shouldn't be.

Polling is simpler in design then event driven, but It also makes the code a bit more organized and "centered". That's how I look at it. Granted your not going to catch everything going on at one given time (as if 13 times a second is slow), but we aren't aiming at fps botting either so the speed isn't that crucial :]

So to answer your question, "after the return flag becomes true where does the code go?", after that function finishes it continues through the rest of the code and restarts the poll.

So in a execution path illustration.... thing:

function poller
check function 1
function 1 returns
check function 2
function 2 returns
poll function returns
restart poll function

The poller itself is accomplished via a timer. Basically, "Call poller function ever 0.075 seconds". Reqbot has a timer, I've not looked too terribly much into it, I just kind of skimmed around following code.

Look in "RestAndBuff.mms"
You'll see some heal skill stuff in there.

And in "Skills.mms"
The concept is to have little containers to manage skills/spells.
Down to the basics it's just selecting a target (in the solo, only your self normally) and pressing a hotbar key limited by a timer.

I use one of the, if not the most basic Lua class/object type setup.
Mainly a single base table and a "metatable".
In C++ it would be like basic class that can have member data and methods but no inheritance et al.
There are a lot of ways to do this kind of thing in Lua.
See here: http://lua-users.org/wiki/SampleCode

In your setup function(s) you'll want to initialize healing skill containers something like this:


You can use a party heal it's easy to just target your self and cast it.
Use "cHealSkill:UseCheckTarget()" to do a target heal skill.

A function to get a read on the whole party:


Then you can walk through the members and see if anyone needs healing and strategize on
what kind of heal needs to be used, etc.

Making a party bot is kind of complex.
Complex as you want to make it with features and what not.

Could just do something kind of simple.
Like if you wanted to have a healer bot it could just follow your main character around
and cast heals on it when your health gets below a level.
Can be something that just keeps pressing the party heal skills over and over in a loop, etc.

ok, just one finaly question, where do u advice to put the new 2 functions?, the one for scan the party and the one for heal, on CombatSolo.mms? or on SoloMain.mms?.

i mean, for what i saw i can just modify combatsolo.mms and get the heal function, but if i just wan to heal and not attack ill have to comment all the other functions inside combatsolo.mms

on the other hand if i add the heald function on SoloMain.mms i can just comment the calls for the CombatSolo functions and get a heal only bot, right?.

or maybe inside the function that verify ur own hp and do the self heal, put the verify party function there and the party heal function there, so everytime the healer checks hes own HP, it will check the party HP and heal if needed.

idk, what whould u recomend me?, i think the last option whould be the best, but im not the expert

Thanks.



EDIT: maybe inside the function cHealSkill:UseCheckTarget, i can put the code after the self check, so it will verify the party hp everytime and heal if needed, what u think?, it will put to much delay on the self heal?.

Thanks.

If you don't want combat at all you could just comment out the line:
"gtCombatSolo:DoCombat()" in "SoloMain.mms".

If you just want a healer bot, you could take out more things from "Main loop..".
If you don't want the healer to loot, etc.

With healing you want it in some place that gets called a lot.

Maybe at the in or at the end of "RestBuffSys:CheckHeals()" in "RestAndBuff.mms".
Since it gets called a lot to do healing on your self.

Maybe start out small just playing with things.
There is no real "debugger" for it unfortunately, but I find i don't really need one.
I just use a lot of print statements to dump stuff out.
For instance if you want to just see it working you could take that "ReadPartyInfo()" from above.



That should dump out the party like this:


For testing things you do it on a key press.
See around line #468 in "Core.mms'
I use the key 'T' as a "test" key.

еще бы по-русски расказали бы про что тут написано и что хотел Сир сказал))

тоже интересует, кто разобрался как настроить хила, чтоб хилил того кто в пати, когда тот нуждается? Опишите плз (на русском)

а что описовать то? =) часть кода есть. токо вот сомневаюсь что ты сможеш дописать остальную часть.