Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
BBot 82.2
#1
Hello guys,

Quote:+ Bank Balance support new Trade message: 'Your account balance is now...'

+ HUD alignment constants to HUD.Print and HUD.Setup
* Fixed Attack Sequences, Mana>NeededMana should be Mana>=NeededMana
* Fixed Advanced Attack Waver unnecessary exhaustion between turn & shoot

= Macro internal functions Add, Sub, Div, Mult, Mod now return values and won't change variables, also they receive absolute values instead of variable names.

+ New macro variable usage possibility: !VAR instead of !VAR!, both will be supported

+ Macro Cooldown System - allows you to create a internal macro cooldown, you can use cooldowns to create conditions that last a certain period
+ [macro] Cooldown.Create(CooldownName, Delay)
+ [macro] Cooldown.Rest(CooldownName)
+ [macro] Cooldown.Blocked(CooldownName)
+ [macro] Cooldown.UnBlocked(CooldownName)

+ Macro Constants feature, some common used constants now have pretty names, making easier to understand the macros

+ [macro] Self.Direction()

= Macro Editor auto-complete now shows more information about each function
+ Macro Editor auto-complete: "!" for variables and ":" for constants

Macro constants:
Now BBot support a kind of constants in Macros.

1. Some functions returns constants:
Self.Direction -> :North | :South..

2. Some functions receives constants as parameters
HUD.Setup(HAlign, VAlign) where VAlign could be :VTop | :VMiddle | :VBottom
HUD.Print(...)

3. These constants can be used in comparison:
Self.Attacking()==:True

4. And finally, some constants are not constants, but easier names for common variables:
:x | :y | :z -> returns CURRENT player position
:SelfID -> returns current player ID
:TargetID -> returns current player Target ID (or 0 if none)

Macro Cooldowns
Macro cooldowns allows you to create internal cooldowns/exhaustions. They can be used to allow/disallow actions for an certain period:

[macro]100 {WeHaveAPlayerOnScreen Cooldown Activator} Creatures.PlayersOnScreen()>0 Cooldown.Block(WeHaveAPlayerOnScreen, 5000)[/macro]
[macro]1000 {WeHaveAPlayerOnScreen Cooldown Usage} Cooldown.Blocked(WeHaveAPlayerOnScreen)==1 [NotActivated] Debug.Log(There were no players on the last 5s on screen) Exit() {NotActivated} rest:=Cooldown.Rest(WeHaveAPlayerOnScreen) Debug.Log(There was a player on the last !rest)[/macro]

This version is still beta, we are testing the constants, if you have any issue, please post it here!
Reply
#2
So it doesn´t matter if bbot are upload becouse i can´t use it for payling tibia rl 10.0 without battleye come on guys -.- upload this sht i waste my money
Reply
#3
(04-06-2017, 08:50 PM)aldevalmar Wrote: So it doesn´t matter if bbot are upload becouse i can´t use it for payling tibia rl 10.0 without battleye come on guys -.- upload this sht i waste my money

It's been known for a year that bbot Won't be supporting RL TIBIA ANYMORE after Battleye release, so you have NO RIGHT to complain.


Now all improvements are focused on OTS, meaning making bot less human / random and much faster cuz it doesn't matter on OTS.

Improvements in macro language also are awesome
Reply
#4
There is a Tibia without battleye and look what you have here.

Tibia 11.0 and Tibia 10.00 with BattlEye wont be supported!

I want my money back..

i have my complain!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! don´t lie
Reply
#5
(04-08-2017, 07:34 AM)aldevalmar Wrote: There is a Tibia without battleye and look what you have here.

Tibia 11.0 and Tibia 10.00 with BattlEye wont be supported!

I want my money back..

i have my complain!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! don´t lie


Send your issue to: admin <at> bmega <dot> net
Reply


Forum Jump:


Users browsing this thread: 1 Guest(s)