Ogre Craft

Solenoid

Member
Hi,

I have one toon that i am trying to level and consistently Ogre Craft stops.

The message says "
OgreCraftError[1.2]: Custom: Counter: ( Billow of Steam )Option1-3: ( 3 )Dur or Prog: ( Progress-1 )
OgreCraftError: Taking a screen shot of the error. Your latency is 131. If this is above 400-500, you are lagging pretty hard and is probably the cause of the error.
OgreCraftError Unable to finish writ quest."

This occurs on more than one computer.
 

Kannkor

Ogre
Hi,

I have one toon that i am trying to level and consistently Ogre Craft stops.

The message says "
OgreCraftError[1.2]: Custom: Counter: ( Billow of Steam )Option1-3: ( 3 )Dur or Prog: ( Progress-1 )
OgreCraftError: Taking a screen shot of the error. Your latency is 131. If this is above 400-500, you are lagging pretty hard and is probably the cause of the error.
OgreCraftError Unable to finish writ quest."

This occurs on more than one computer.
Hmm... Those are two completely unrelated errors. One is it just missing a counter. And I double checked that counter, it is definitely coded in there.

Can you provide more information. Such as what class, what level, what was the writ name, and what was it crafting (exact recipe name) when you got this.
 

Solenoid

Member
Well it must have just been the 60's for provisioner as i have had no issues once i got into the 70s. Maybe not related but so far so good.
 

Ibotthis

Active Member
This happens when you've got so much experience that you ding two levels in the same writ. If you have a lot of crafters on the account that boost up the veteran experience, vitality, and a potion running, you'll ding so fast that one of the recipes don't get scribed on level. It happens to me in the 30's through 50's then stops. I figured it out when I saw it didn't happen on an account that had no vitality and no other crafters on it for the veteran experience, but it happens to all my other toons. I can't just set it and forget it until after I get past the early levels, need to be at the keyboard doing other stuff till then and scribe the missing recipe book before the next writ starts.
 

Kannkor

Ogre
This happens when you've got so much experience that you ding two levels in the same writ. If you have a lot of crafters on the account that boost up the veteran experience, vitality, and a potion running, you'll ding so fast that one of the recipes don't get scribed on level. It happens to me in the 30's through 50's then stops. I figured it out when I saw it didn't happen on an account that had no vitality and no other crafters on it for the veteran experience, but it happens to all my other toons. I can't just set it and forget it until after I get past the early levels, need to be at the keyboard doing other stuff till then and scribe the missing recipe book before the next writ starts.
ahh, I was wondering this at one point but couldn't prove it so discounted it as unlikely to happen.
I can likely fix this... In the future..
 

Ibotthis

Active Member
ahh, I was wondering this at one point but couldn't prove it so discounted it as unlikely to happen.
I can likely fix this... In the future..
That would be awesome! I like to sit and make sure things are going smoothly as far as crafting goes before I afk for an extended period, and I still come and check it periodically to down a fresh potion and whatnot. It was sitting down and watching the whole process that I noticed it skipping over scribing one of the recipe books. Glad I could help in some small way :)
 

scolsis

Member
Started to get an error today in ogrecraft when adding a recipe to the queue. OgreCraftError: Unable to read recipe information. ( 916924427 )
 

microgiant

New Member
I just signed up to use this software. I was trying to figure out what I was doing wrong. OgreCraftError: Unable to read recipe information. here as well.

I wish I had seen the trial before I paid for the sub!
 
Last edited:

bjcasey

ISX Specialist
There was a bug with the first version of ISXEQ2 after today's update. Amadeus has since corrected this bug. Reload all EQ2 sessions to fix your issue.
 
Top Bottom