Feed-O-Matic 10900.2
[ download ]
Fixed a 1.9 compatibility issue. (Error message about GetBattlefieldStatus()).
Gazmik Fizzwidget's
Superior Gadget & Doodad Emporium
Fixed a 1.9 compatibility issue. (Error message about GetBattlefieldStatus()).
January 3rd, 2006 at 9:11 pm
Thx Team
January 4th, 2006 at 5:36 am
Nice! Summoned pet, got the error, and you’ve already fixed it 😀
January 4th, 2006 at 9:13 am
autofeed not working anymore ><
And whenever I want to readd custom food (since pet refuses to eat) the error points me to this line
“local _, _, itemID = string.find(itemLink, “item:(%d+):%d+:%d+:%d+”);”
January 4th, 2006 at 11:15 am
One other thing I notice is that when using the savebonus, questfoods, etc. on or off, while the message stating the food will / will not be avoided, after I use the cammands displays properly; when I type I type FoM status, it still says (for exampe):
food that gives the player extra bonuses will be avoided
EVEN if I have set that I do not want it to be with FoM savebonus.
January 4th, 2006 at 1:23 pm
I keep getting the Gtbattlefieldstatus error message
January 4th, 2006 at 10:22 pm
Best turn-around on a fix ever. No wonder I <3 Fizzwidget’s mods.
January 5th, 2006 at 7:03 am
Hi!
Looks like another 1.9 bug – opening up cooking in IF – I get a message:
“Interface\AddOns\GFW_FeedOMatic\FeedOMatic.lua:1560: bad argument #1 to ‘find’ (string expected, got nil)
Help! Grumble the Fisherman
January 5th, 2006 at 9:16 am
odd error i have been getting w/ 1900.2 It only happens when I open my cooking panel. I have tried deleting out the savedvariables and such w/ no luck. Here is a link to a picture. http://img213.imageshack.us/img213/323/feedomaticerror8nz.jpg
January 5th, 2006 at 3:05 pm
I use Feed-O-Matic and Autocraft, and I got the following error when opening my cooking window after selecting “saveforcook” (wanted to make sure pet doesn’t eat sagefish):
……\FeedOMatic.lua:1560: bad argument # to `find’ (string expected, got nil)
it popped up twice, but I haven’t seen it since.
January 5th, 2006 at 5:29 pm
kept having nil variable error after over-install and new install – did a /fom reset and it fixed it
January 5th, 2006 at 5:33 pm
scratch that last reply – still doing it – heres the error feedomatic.lua:1465:attempt to index global ‘FOM_foods’ (a nil value)
any suggestions?
January 5th, 2006 at 7:05 pm
that’s exactly the line it points me to.
if you use standard food, and one kind of it in your bags it just works.
however if I add other food in my bags or special food, it stops working and gives errorboxes whenever it tries to feed.
January 5th, 2006 at 8:30 pm
Post the food items you are getting the error with. Some items are not in the list in FeedOMatic_Foods.lua
like: 21552, — Striped Yellowtail
January 6th, 2006 at 1:31 am
I also tried to manually add Undermine Clam Chowder (using /fom add fish [Undermine Clam Chowder]), which FeedOMatic didn’t seem to recognize, and got the same error:
FeedOMatic.lua:1560: bad argument # to `find’ (string expected, got nil)
It’s the same error that Uller got when opening his cooking window (and I get the error when opening the window sometimes too). This is the first time I’ve seen the error without actually having the cooking window open.
sigh back to PetFeeder for now 🙁
January 6th, 2006 at 8:39 am
Im not using any strange foods- same meats i always use – buy them from the butchers
January 7th, 2006 at 10:51 am
I get the same message. It happens everytime I open my cooking window or whenever something finishes cooking. Mod list available on request.
Thanks, in advance, for any help anyone can give. SDime
January 8th, 2006 at 9:16 am
When I try to add lobster stew, or any other food not in its database I get that same error too
\FeedOMatic.lua:1560: bad argument # to `find’ (string expected, got nil)
I get it everytime I try to add any new foods 🙁
January 8th, 2006 at 9:20 am
I was having the line 1560 of FeedOMatic.lua when opening a cook window and in trying to track down the problem I wound up taking all of my food and putting it in the bank, re-adding it to my pack piece by piece and by the time I was done and it was all back in my pack the error was gone. I didn’t identify a problem food but perhaps the list, cache or whatever just needed to reinitialize. This is a complete guess but mine appears to be working fine again.
This is a great addon for hunters, thank you Gazmik Fizzwidget!
January 8th, 2006 at 2:15 pm
Items that mess it up are …
Magebread Lobster Stew …
Just any customs
And you can’t add them as you normally do that gives the same error.
Seems the routine to add non standard things is broken.
iow
/feedomatic add fish /feedomatic add meat
returns error and doesn’t add it.
Think if that gets fixed the other errors disappear to it all points to the same line.
Did item links get a slight change in 1.9 so feedomatic doesn’t pick it up correctly anymore?
January 9th, 2006 at 3:23 pm
I’m guessing Gazmik knows about the issue being that I see the post above mine has been edited for foul language.
Great mod(s) Gazmik. We all appreciate what you do and eagerly await a working release of Feed-o-Matic.
January 9th, 2006 at 4:30 pm
I’m getting the same error when opening my cooking tab. I have pretty much every recipe. I wiped out my savedvariables, and after getting the error, logged out and the following is all that got saved… Whatever food is after id 13760 is causing a problem? I’m not sure how you are parsing the cookbook…
FOM_Cooking = { [“Hellscream.Ahlee”] = { [13893] = 3, [13754] = 1, [13758] = 1, [13755] = 1, [13759] = 2, [13760] = 2, }, }
January 9th, 2006 at 4:31 pm
Forgot to add that I completely emptied my inventory of food before opening the cooking tab per the advice of someone above; I still get the error.