What's new
  • Visit Rebornbuddy
  • Visit Panda Profiles
  • Visit LLamamMagic
  • Visit Resources
  • Visit Downloads
  • Visit Portal
RebornBuddy Forums

Register a free account today to become a member! Once signed in, you'll be able to participate on this site by adding your own topics and posts, as well as connect with other members through your own private inbox!

[Release] RebornBuddy Version 1.0.461

Right on!

How about x64 compatibility? I see every month or so a new addon-esque system, or bot, or some other random thing that is only compatible with the x64 version, and all this rumor and speculation of "no longer supporting 'legacy' versions is concerning, at the least. Sorry for the multi-post, you replied too fast! XD
 
VdXMfbn.gif
 
All my gathering profiles doesn't work anymore. Every eorzean time check has 1HE of advance (When I check between(2,3) it goes at 1:00AM instead of 2:00AM)
 
All my gathering profiles doesn't work anymore. Every eorzean time check has 1HE of advance (When I check between(2,3) it goes at 1:00AM instead of 2:00AM)

This happens when your system time is off. Adjust your clock to the proper time.
 
Version 363
Code:
Add FishingManager.TugType and FishingManager.SelectedBaitItemId
Add GatheringManager.HqGatheringCombo
 
Version 364

Code:
The following conditonals now provide all the overloads they were intended to
HuntEntryCompleted
HuntSubEntryCompleted
HuntGCEntryCompleted
HuntGCSubEntryCompleted
HuntGCRankCompleted
HuntGCEntryCompleted
HuntGCSubEntryCompleted
HuntGCEntryCompleted
HuntGCSubEntryCompleted
HasItem
ItemCount
HasHqItem
HqItemCount
HasNqItem
NqItemCount

Updated ironpython
Change how we handle finding agent modules
UseTransport: Favor objects that are close to the provided position
Log line number when condition execution fails in if and while tags

Gathertag:
Properly output debug information when the poi is changed
Make sure we are not flying before we try to interact with a node (improves compatbility with exmats enableflight plugin)
Shorcircuit the logic for returning to a hotspot if our vision totally encompasses the hotspot (it will no longer run back all the way to the center of the hotspot thus looking more human and saving time)
 
Does this affect RB at all?

http://forum.square-enix.com/ffxiv/...anctuary-A-Guide-to-DPS?p=3576473#post3576473
Hello, everyone.

FFXIV Producer and Director Yoshida here.

First, I would like to thank those who reported and investigated this matter! However, these reports are based on unofficial data, and not from official data, so we’re carefully investigating cases such as these.

From the reports received from everyone, we were able to confirm players circumventing aspects of the game system to, among other things, deal higher than intended levels of damage. Also, we would like to assure you all that this is something we take very seriously.

We have conducted an investigation based on official logs that were accumulated within the development team, and we have already identified the cause. For security reasons I won’t delve into specifics, but there already exist several checks and balances in place for irregularities in output damage, as well as strict limitations that have been set on the system-side. However, in order to avoid players from experiencing unexpected lag, or severely lowered level of gameplay comfortability, the system allows a certain amount of room for the decision to be made. For the case at hand, we have decided to carry out a stricter measure for unjustifiably speeding-up within the boundaries that have been set.

As we are nearing the release of Patch 3.2 and the introduction of the next raid tier, the development team has already implemented a stricter log observation, as well as a stricter automated detection for any data irregularities on the server-side.

I would like to mention that should we find tools which unjustifiably control the client process speed, or tools which modify the packets, we will not hesitate to carry out punishment such as banning the offending players.

We thank you all for sharing this information with us!
Please continue to enjoy FINAL FANTASY XIV!

And, of course, please look forward to Patch 3.2. :P
 
Version 366
Code:
New version for ff14 3.2
All reported mesh issues have been fixed
Descending method has changed, now will slide down objects instead of stuttering
 
ChatManager.SendChat is throwing System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. ---> GreyMagic.InjectionSEHException: Injection resulted in a process exception with error code 0xc0000005

testing in rebornconsole should reproduce
 
ChatManager.SendChat is throwing System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. ---> GreyMagic.InjectionSEHException: Injection resulted in a process exception with error code 0xc0000005

testing in rebornconsole should reproduce
Thanks for the report, restart the bot to get the updated offsets and it should work now.
 
ff14bot.Managers.MovementManager.StartAscending(), ff14bot.Managers.MovementManager.StartDescending(), ff14bot.Managers.MovementManager.StopAscending(), ff14bot.Managers.MovementManager.StopDescending() are throwing System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. ---> System.Exception: Error while writing Memory!

should be reproducible in rebornconsole
 
ff14bot.Managers.MovementManager.StartAscending(), ff14bot.Managers.MovementManager.StartDescending(), ff14bot.Managers.MovementManager.StopAscending(), ff14bot.Managers.MovementManager.StopDescending() are throwing System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. ---> System.Exception: Error while writing Memory!

should be reproducible in rebornconsole
Pushing a new build now, i wasn't able to reproduce it 100% let me know if you are still able to after this version.
 
ff14bot.Managers.DataManager.GetLocalizedQuestName() can't seem to get the name for quests (and preventing pickupquesttag from working)
 
ff14bot.RemoteWindows.JournalAccept.Accept() is hitting decline instead of accept I think. it's a least closing the window without accepting the quest
 
New version building.

Also there is no need to provide the entire namespace in the console or in code tags for most functions. JournalAccept.Accept() works fine and the ff14bot.RemoteWindows just complicates it needlessly
 
Back
Top