Triane
Aug 31 2003, 11:50 PM
As the previous thread has become more or less irrelevant, and is misleadingly described, I am starting this thread to provide support for FnB3TR1.2.xxx versions from TR1.2.526 and later.Although I will take and respond to technical-assistance questions in this forum, responses will be quicker on the official support site. Please do not cross-post either Q&A, or copies of this macro, to any other boards, and trust no copies which do not come directly from there. No permission is granted to re-distribute this macro except by linking to the official posting on the FnB site.
Please Note: Although the "Official" Fluff'n'Buff
website is not up, the Support Forums are. Feel free to visit them at
http://www.fluffnbuff.ca/ForumsDecember 5:NEW!The FnB3 server seems to be up and running, although it is difficult to tell when you're on the same network, if servers you can see can also be seen by people from other nets. Nevertheless, TR1.2.712 has been posted on the FnB3 website. If you are unable to reach the site, please let me know. This version has several minor fixes and also incorporates the new ACTools' commands. You
need at least ACTools v4.4.16 beta 5 to run this version.
(October 18): Some people have reported difficulties reaching my server. Although I am unsure as to the cause of this, I am posting the latest FnB3 release here again until I figure out what the problem is.
(October 11): Fairly major update to FnB3 released: TR1.2.584. I have incorporated most of the
Includes into the main ".mac" file. There are about 1/3 as many includes now, which dramatically reduces load-time when the bot is started. I have also made changes that incorporate Turbine's changes to the AC Client in the September '03 patch. That is to say, FnB3 now buffs whatever weapon is in the hand of the player it is buffing. It no-longer uses stored weapon Id's! This makes is much easier for players to have multiple weapons buffed (by simply issuing "
buff weapon" commands and changing weilded weapons) without having to "
define" them first. Also, although it is still in testing, the bot
SHOULD be able to buff users' armour
while they are wearing it. I would appreciate any feedback anyone has to offer on this in the way of bugs or known issues before I declare it to be a sound feature, but the few tests I have performed seem to indicate that it will work. The HTML help file has also been editted and updated to reflect the current state of the code, you should be sure to reconcile any old version of it that you may have posted with this new one. Enjoy!
(September 2): Released the full distribution of the current version (TR1.2.532). Some small changes implemented from .526 but mostly it's just the complete FnB3 distribution archive.
(August 31):Released updated TR1.2.526. Primary changes are mostly bug-fixes and minor tweaks. Error handling is more complete and the bot should recover from most errors that it generates (if any). Error data is saved to a CDS file that can be read at any time even with the bot in operation. The armour tinkering plugin is incorporated into this release. To disable it, remove the applicable include line from the FnB3TR1.2.526.mac (around line 108) and remove the "
tinker" command from the FnB3.Commands.cds file.
Download FnB3 from the Official FnB3 Support WebsiteThe newest updates will always be available from there!(The attachment to THIS message is the current HTML helpfile, to get FnB3 you have to go to the official site).
-Triane
Slit
Sep 1 2003, 07:58 PM
I am a bit confused. The FnB macro list a bunch included scripts. Where can I get them?
Thanks
Triane
Sep 1 2003, 08:40 PM
| CODE |
//-------------------------------------------------------------------// Constants // Out of consideration for the author(s), please do not change these FnBName = Fluff'n'Buff 3! FnBVersion = TR1.2.526 FnBDate = 31 August '03 FnBAuthors = Triane of Leafcull & Ican Fletch, Harvestgain End //-------------------------------------------------------------------//
Include FnB3.Utility.inc // all utilitarian procedures. Include FnB3.RestockOpt.inc // allows the bot to buy it's own tapers Include FnB3.UserManager.inc // all user management functions Include FnB3.Timers.inc // timer functions Include FnB3.MessageHandler.inc // incoming message handler Include FnB3.Casting.inc // procedures for casting spells Include FnB3.Help.inc // user help information Include FnB3.Setup.inc // Routines to setup and configure FnB3 Include FnB3.ArmourTink.mac // Armour Tinkering Support
//-------------------------------------------------------------------// |
All of the scripts that FnB3's main script calls are included in the distribution archive. Only the ArmourTink.mac is an optional module, the rest are required in order for the bot to function.
The following is a recommended procedure for installing FnB3:
Create a directory under the "ACTools" main directory (or, alternately, under "AcTools\Macros") called "FnB3".
In this folder place all the macro files (".mac" and ".inc") from the distribution archive.
Under the FnB3 directory, create two other directories, one called "Data" and one called "Logs".
Move all of the data (".cds") files from the archive into the "Data" directory you just created.
Load AcTools v4.4.15 or later as prescribed in the release notes.
Modify the AcTools preferences ("Editor|Preferences") to include the "FnB3" directory that you created.
Load "FnB3.Constants.Public.mac"
Edit ALL of the applicable values in this file to reflect your OWN, PERSONAL setup choices.
IMPORTANT NOTE: Ensure that you correct all path settings to reflect your OWN installation!
Save "FnB3.Constants.Public.mac"
Load the main portion of the macto (Typically "FnB3.TR1.2.xxx.mac" where "xxx" is the current revision)
You should now be ready to run the macro in Asheron's Call.
-Triane
stabaho
Sep 2 2003, 05:12 PM
You posted a .mac file Is there suppost to be a zip or jsut the mac?
Triane
Sep 2 2003, 08:02 PM
Heh -- obviously FnB3 is more than just the one mac file. The complete (up-to-date) distribution is posted now, thanks for the pointer, I dunno how many times I've looked at that page in the past few days and never saw that problem.
-Triane
Kenny
Sep 4 2003, 10:41 PM
ok running decal 2.5.01 actool 4.4.15 tr1.2.532 and getting this error
SENDTEXT - 15, 03/09/
SAYPASTE - Internal FnB3 Error Trapped! -- I am shutting down and restarting. I apologise for any inconvenience!
also says error:macro line:
file rewrite statfile
caused error:invalid filename
module:fnb3.setup.inc line 735
any ideas on this?
Triane
Sep 5 2003, 01:11 AM
I'm just guessing, but I'd say you've not defined your paths correctly in FnB3.Constants.Public.mac -- check to make sure that the paths you've defined there are correct AND end with a backslash character ("/").
-Triane
Kenny
Sep 5 2003, 05:42 PM
ok checked that and they have \'s at end is it suppose to be a /?
this is last thing it does b4 getting error
<AcT> Retrieved 2 Users from the data file. (C:\Program Files\AC Tool\FnB3\Data\FnB3.UserData.cds)
<AcT> 03/09/
Triane
Sep 5 2003, 05:46 PM
In Windows they'd be "\"s, not "/"s, pardon my linux

What are the contents of your FnB3.Errors.cds file?
-Triane
Kenny
Sep 6 2003, 12:24 PM
have a few actually
Macro Line: FileReset TextFileCopy caused error file not found
Macro Line: FileRewrite StatFile caused error invalid filename
Could not find constant StatFile
Macro Line: SetConst 1342762041 = _selectedGUID caused error 'kenny' is not a valid integer value for field 'GUID'
that's all i see in there for now
Triane
Sep 7 2003, 08:17 AM
While I appreciate your attempt to convey the error data, there's not enough information in JUST those messages to track down the source of them. Please post the error file so I can have a look at it. In the meantime, the errors seem to be related to filenames/paths, so check to ensure that you have correctly defined these values in FnB3.Constants.Public.mac:
| CODE |
[126] // File Names used by FnB3+ (these shouldn't need to be changed and must NOT contain any path or wildcard characters!) [127] [128] UserFileName = FnB3.UserData.cds // stored user information [129] StatisticsFile = FnB3.Statistics.txt // stored FnB statistics [130] [131] // File Paths used by FnB3+ [132] // IMPORTANT NOTE: These paths MUST exist PRIOR to running this macro AND they MUST terminate with a back-slash character! I do not [133] // recommend that you keep the default values, customize them to your specific installation! [134] [135] FnBDataPath = K:\Asheron's Call\Decal\AC Tool\FnBData\ // Place to find/store our data. [136] FnBLogFilePath = K:\Asheron's Call\Decal\AC Tool\FnBLogs\ // Place to store our logs. [137] FnBMacroPath = K:\Asheron's Call\Decal\AC Tool\Macros\Fluff&Buff3\ // Path where FnB3 macro files are stored. |
You should NOT be using the values listed above (and which are also the default settings that FnB3 is distributed with), the values should be modified to reflect your particular installation.
-Triane
Kenny
Sep 7 2003, 09:49 AM
// File Names used by FnB3+ (these shouldn't need to be changed and must NOT contain any path or wildcard characters!)
UserFileName = FnB3.UserData.cds // stored user information
StatisticsFile = FnB3.Statistics.txt // stored FnB statistics
// File Paths used by FnB3+
// IMPORTANT NOTE: These paths MUST exist PRIOR to running this macro AND they MUST terminate with a back-slash character! I do not
// recommend that you keep the default values, customize them to your specific installation!
FnBDataPath = C:\Program Files\AC Tool\FnB3\Data\ // Place to find/store our data.
FnBLogFilePath = C:\Program Files\AC Tool\FnB3\Logs\ // Place to store our logs.
FnBMacroPath = C:\Program Files\AC Tool\Macros\ // Path where FnB3 macro files are stored.
Triane
Sep 7 2003, 09:59 AM
| CODE |
FnBDataPath = C:\Program Files\AC Tool\FnB3\Data\ // Place to find/store our data. FnBLogFilePath = C:\Program Files\AC Tool\FnB3\Logs\ // Place to store our logs. FnBMacroPath = C:\Program Files\AC Tool\Macros\ // Path where FnB3 macro files are stored. |
When you extracted the FnB3 macro files, did you put them in "C:\Program Files\AC Tool\Macros", or in "C:\Program Files\AC Tool\FnB3"? If it is the latter, your definition of $FnBMacroPath is incorrect. If you put the macro files into the "AC Tool\Macros" directory, did you then move the included data files to the "Ac Tool\FnB3\Data" folder? (I'm assuming that you already created the "Ac Tool\FnB3", "Ac Tool\FnB3\Data" and "Ac Tool\FnB3\Logs" folders)
-Triane
Kenny
Sep 7 2003, 10:34 AM
OK got past that error. Now getting one about Accepted Items.
Error: Could not find List AcceptedItems defined!
Module: FnB3.Constants.Public.mac Line: 315
Everything listed in the Accepted Items sections should be correct as I haven't made any changes to that. Thanks for all the help.
Triane
Sep 7 2003, 10:48 AM
In FnB3.Setup.inc find the following:
| CODE |
[257]//-------------------------------------------------------------------// [258]// Setup procedures for FnB3+ [259]//-------------------------------------------------------------------// [260] [261]Include FnB3.Constants.Public.mac // all user editable constants. [262]Include FnB3.Constants.Private.inc // all internal constants. |
Try reversing the order of lines [261] and [262] so that the private constants are defined first. What's weird about this error is that I don't understand how it's never occurred before: looking at it, EVERYONE should experience this error every time, but AFAIK this is the first that it has been reported... very strange...
-Triane
Kenny
Sep 7 2003, 11:07 AM
Ok. Changed those...closed AC Tool and restarted it. Everything works great now. Thanks alot for the prompt and friendly help. Have a wonderful Sunday.
Wolfpack
Sep 14 2003, 09:37 PM
Hiya,
Well, I've been trying to get this bot to run, from what I hear it's a great buff bot, very reliable.. I'm having some problems. My path names are correct and I followed your installation directions exactly, I'm running AC Tool 4.4.15, decal 2.5.0.1 final.. Here is what I see in the game. I start up everything loads fine until I get here... then I begin to loop, the bot restarts each time at this step..
| QUOTE |
<AcT> Kiva tells you, "Loaded 45 profiles from C:\Program Files\AC Tool\FnB3\Data\FnB3.SpellProfiles.cds" <AcT> 03/09/ <AcT> Kiva tells you, "Fluff'n'Buff 3! coming down, timers disabled - be careful out there!" You say, "Internal FnB3 Error Trapped! -- I am shutting down and restarting. I apologise for any inconvenience!" |
I checked the error file with the cds edit and this is what I see...
| QUOTE |
Date : 03/09/14 Time: 19:44:22 Message: Macro Line: MousePos 0 | .1 sec Caused Error: "is not a valid integer value Line Text : MousePos 0 Proc: Procedure: OpenMainPack Line: 0 Module: FnB3.Utility.inc User: Kiva Command: text text |
Ahh! I have no clue how to fix this.. please help!
Triane
Sep 14 2003, 11:03 PM
This is quoted from the other, older FnB3 thread (
here). This bug is QUITE common for whatever reason, but I'm unsure of why it occurs.
| QUOTE |
I'm still unsure as to why this error crops up sometimes and not others, it's kind of annoying, and as was stated, it's been around pretty much since FnB3 was born.
The "official" solution was to enable "Universal Constants - StretchUI" (or "Universal Constants" if you don't use StretchUI). IPA has said though, that these are legacy ACTools settings, and have the potential to do more harm than good. If the fix Jtul mentioned works, I will incorporate it in future releases. As for ACTools 4.4.13, I have been running FnB3 TR1.2.5xx under ACtools 4.4.15 for several days and have experienced no significant issues. If necessary, I will post a release of 1.2.5xx, but there are no noteworthy changes in it from version 1.2.455 which is posted presently. |
Apparently I was out of my skull the day I wrote that: the "fix" I referenced (by Jtul) was not a fix, but a substitution that regressed the code. The PackSlots array is used to optimise application of predefined incUI MousePos coords. When it was implemented, I went through the ENTIRE macro, and removed hard-coded packslot definitions and replaced them with PackSlots references. Going BACK through the entire thing and performing that in reverse is regressive and not something I plan to do. The "Use Universal Constants" settings seem to correct the problem, and haven't caused any noticable side-effects, so I would recommend that course as the one to follow.
-Triane
Wolfpack
Sep 15 2003, 10:37 AM
Awesome, it worked. I set Use Universal Constants and she's up and running! Woot! Thank You!

Very fast bot, I luv it!
Also, am I right in assuming the packslots are listed backwards? 1 being first main backpack, and then 8, 7, 6, 5, 4, 3, and 2? It just seems that she is trying to target her comp pack which I set to pack 7 but she actually targets the foci I have 3rd slot down including the main pack 1. If this is the case, should this info be in your writeup?
hehe, I prolly overlooked something in your writeup, I will try moving my packs around and see.
Thanks again!
Triane
Sep 15 2003, 12:11 PM
The PackSlots assignments are sequential, from 1 (main) to 8 (last/bottom)... if this is not happening correctly, ensure you're using the correct "Use Universal Constants" setting (either the one WITH StretchUI, if yours is stretched, or without it if it's not).
-Triane
Wolfpack
Sep 15 2003, 08:11 PM
Thanks!

The Bot is up and running smoothly now.
Triane
Sep 15 2003, 08:35 PM
Np, glad to hear it's doing it's job!

-Triane
Triane
Sep 26 2003, 06:27 PM
*bump*
Vengor
Oct 7 2003, 02:52 PM
How hard would it be to scab this macro (scrounged from the CastAway forums and written by Sweetleaf) into FnB? It relogs into AC when the AC client drops to desktop. There was another one there as well that worked with the dual client installed. You can view the thread
here.I like FnB but I hate that damned trade window cash to desktop bug.
Triane
Oct 7 2003, 04:12 PM
Hehe -- it drives me crazy too.. I wish there was some explanation for why this happens to ACT macros far more frequently than InsaneBot or TradeBot plugins...
I'll have a look at the code and see if there's something that can be done...
-Triane
Triane
Oct 11 2003, 03:10 AM
Am attempting to work out a new method for performing logins, will see how it pans out. In the meantime, TR1.2.584 has been released thismorning, details (and a link to the official FnB support forums) are at the top of the thread.
-Triane
Triane
Oct 18 2003, 08:23 PM
Due to problems some people have been experiencing with reaching the FnB3 website (Forums), I posted a copy of the current release at the top of this thread. Once again, FnB3 can be downloaded from here.
-Triane
There are two loyalty spells defined in the settings I have TR1.2.584, fresh install.
| QUOTE |
FealtyOther = Odif's Boon LoyaltyOther = Odif's Boon LeaderOther = Ar-Pei's Boon |
Just a heads up, I don't know if both have to be there so I won't touch it--just modify the settings to what I need and move along

.
Setting up a bot (in software mode) on an old PC, hopefully it runs good. I don't care what the window looks like, as long as it puts out those spells
The PC I'm running it on is very...ancient. It took well over 3 minutes just to get FnB to run, and then went into an error trapping loop. Gonna mess with it tomorrow, hopefully all is good -- I remember the /tell's when my brother ran this bot long ago (he quit...) that my buffs were going...definitely one of the coolest features.
Ahk
Triane
Dec 5 2003, 09:40 AM
Hehe -- that's an old leftover from Ican's code. Some of that stuff has been hanging around since I started adapting FnB2 and was never expunged. I did a quick search through the macro, and I don't think "LoyaltyOther" is ever referenced except in that one case. There's an updated version I haven't posted yet that includes a few updates from Ipa's recent ACTool modifications. I'll yank the "LoyaltyOther" variable before I post it. Thanks for the note!
-Triane
Found the bug:
| CODE |
| Macro Line: MousePos 0 | .1 sec |
Don't freak yet! I read the above fixes but it didn't seem right that it be necessary to use universal constants.
I did some digging and found this in the setup include:
| CODE |
257: Call DefinePrivateConstants // From FnB3.Constants.Private.inc ... 270: Call SetUp // From FnB3.Setup.inc
|
DefinePrivateConstants is assigning values to the PacksSlots list that haven't yet been determined by incUI. I simply moved the ListAdd PacksSlots from DefinePrivateConstants to right after Call SetUI...I recall seeing some windowed mode calculation and I'm not sure where it was - but you probably do...so it'd probably be more appropriate to put it after that line?
I tested the move and it worked.. I also found out that you can't just copy the macro after it's been run on one character and try to run it on another heh.
Lol the klunker K6-2 took over 4 minutes.
Ahk
I've got a problem.
The klunker put out the following errors when I issued the command 'help'.
Macro Line: DSIndex Users, Names||||Caused Error: Index 'Names' not found
Proc: SelectUser $WhoSaid
FnB3.TR1.2.584.mac
User Human Shield //<- the bot
Macro Line: FileRewrite StatFile||||Caused Error: Invalid filename
Proc WriteStatFile
FnB3.Setup.inc
Some background info...
| QUOTE |
FnBDataPath = C:\Program Files\AC Tool\Macros\FNB3\Data\ // Place to find/store our data. FnBLogFilePath = C:\Program Files\AC Tool\Macros\FNB3\Logs\ // Place to store our logs. FnBMacroPath = C:\Program Files\AC Tool\Macros\FNB3\ // Path where FnB3 macro files are stored. |
FNB3 is included as a macro path, and the file FnB3.Statistics.txt was actually created in the FNB3\Data\ folder with the following contents:
I don't see why the FileRewrite would bug out like that..everything looks ok to me. The PC runs pretty slow, but I don't think that should affect it's ability to do anything. It's on beta 5, decal doesn't relate to this..but I d/led it yesterday to that PC and up'd the memlocs.
I'm going to set the bot up *sigh* again on my PC and see if it does the same thing. I've tried clean setups, and setting up on my PC then copying the files for his character but no luck.
On my PC at least it rebuffed, and I thought it was all good then copied it.
Ahk
Triane
Dec 5 2003, 03:50 PM
I'm at work, so I can't do too much poking around, however I wonder, given the age of your old PC, if long-filename operations might cause an issue? If it's not Fat32, you might need to change the path/filename's to 8.3 format. This seems an unlikely situation, but it's one possiblity...
-Triane
It's on NTFS, but I didn't think of that. It's wierd that I can run the same code on my PC without problems (same config and character)..also I posted about the MousePos issues on Pg2.
Ahk
Triane
Dec 5 2003, 05:07 PM
NTFS shouldn't have any trouble at all with the filenames... In all honesty, I would have been kind of surprised if it HAD turned out to be the problem, but I thought I'd throw it out there as a possibility...
I caught the issue about MousePos, but as I'm at work, I can't look into it. I had investigated the order of the assignments before and was sure that the SetUI code was called first, but I'll know better when I get home and can look at it directly. (It's been a while since I've done much FnB work as interest had died off lately).
-Triane
Triane
Dec 5 2003, 06:57 PM
Hehehe -- well, you were right on, I don't know how that's slipped by (especially given how many times I've looked at that), but sure enough, SetUI was called well after those variables were defined. Needless to say, I've corrected it now.
Will hopefully get the current version of this out this weekend. nothing new in it per se, but some bug-fixes, and the adaptations for some of Ipa's new commands. Oh, and I also looked at the code that discerns when buffs run out (prompted by your earlier comment in regards to it) and I think I located and (hopefully) fixed a bug that caused it to never give the warnings.
-Triane
Triane
Dec 5 2003, 07:35 PM
Okies, I posted the current version. It needs some playtesting time though, I haven't had much opportunity to run it of late. It's on the FnB3 website at
http://www.fluffnbuff.ca/forums.
If you experience problems reaching the website, please post here and let me know!
-Triane
This is a "lo-fi" version of our main content. To view the full version with more information, formatting and images, please
click here.