Results: 5Comments by: Veramocor
File: CraftStore11/08/15
error message
Posted By: Veramocor
I liked your add-on from the first moment on... therefore I'd like see it work, unfortunately I get the following error message everytime I open the (updated) add: bad argument #1 to 'pairs' (table/struct expected, got nil) stack traceback: : in function 'pairs' user:/AddOns/CraftStore/CraftStore.lua:466: in function 'CS.Upda...
File: CraftStore09/11/15
Error message
Posted By: Veramocor
Hi everyone, I tried to understand a bit of what you all were writing about, but it seems that I am a bit to dump to follow the tracks... Could someone please tell me easily and practically what I can do or should do to prevent getting the following error message everytime I either open the Craft Store or I start to analyze a n...
File: Alchemist (Update Orsinium)09/11/15
After I put in the lua-file the add...
Posted By: Veramocor
After I put in the lua-file the additional line that you quoted, I still got an error message for the mod, and a long list in yellow in my chat window, starting with .(string): 1 = and then feature "one" of some reagent; this continues .(string): 2 = ..... until .(string): 4 = ..... and then starts with string 1 again, presumab...
File: Alchemist (Update Orsinium)09/08/15
After I put in the lua-file the add...
Posted By: Veramocor
After I put in the lua-file the additional line that you quoted, I still got an error message for the mod, and a long list in yellow in my chat window, starting with .(string): 1 = and then feature "one" of some reagent; this continues .(string): 2 = ..... until .(string): 4 = ..... and then starts with string 1 again, presumab...
File: Alchemist (Update Orsinium)09/04/15
Hi there, I am using the German...
Posted By: Veramocor
Hi there, I am using the German version of the great addon and receive the following error message as soon as I open the Alchemy workstation and have "Wiesenschaumkraut" (Lady's Smock) in my inventory: >>"Wiesenschaum|okraut" is not a valid reagant.<< It is actually the same error I received under the same circumstances...