Release MQ2FeedMe

[Zebadiah]

Yes I read the previous messages and yes I noted that EQ might have a bug but others also said it was MQ2Feedme. So question is if Mq2FeedMe is okay and that It is EQ that is messing things up then Why are we not pulling MQ2FeedMe untill we can solve the EQ problem? Or inform everyone that MQ2FeedMe and EQ do not play happly together for the time being.


Zeb

 

[Sic]

Yes I read the previous messages and yes I noted that EQ might have a bug but others also said it was MQ2Feedme. So question is if Mq2FeedMe is okay and that It is EQ that is messing things up then Why are we not pulling MQ2FeedMe untill we can solve the EQ problem? Or inform everyone that MQ2FeedMe and EQ do not play happly together for the time being.


Zeb

?

Feedme is just doing a /useitem when your thirst/hunger is at a certain level.

If we "pulled" everything that uses /useitem there would be no automation combat automation.

And not to beat a dead horse /useitem is also a native eq function (I'm not at PC to see if mq overrides that or not)

There seem to be some jumps of conclusion and blame happening here.

"We" can't solve the EQ problem unfortunately, they've had a "casting" and "item usage" error for years at this point, and when they try and fix it they whackamole it into coming up in some other way.

 

[Zebadiah]

Don't get me wrong Sic, I think everyone here is doing a great job and needs a lot of pat on the backs. What I am thinking is that there should be a way for us to figure a way around this so that the program can work as it should and not interfere with other aspects of MQ2. I understand the that it uses /useitem. Its a great program and hope we can figure it out.


Zeb

 

[madimp]

Is it possible that they've changed the satiation values? Zebadiah said they were getting spammed with the 'You cannot eat/drink anything more' message with it active with the values suggested, which means it could be trying to reach a number that isn't possible any longer.

 

[Nightmare327]

I wrote a Lua replacement I have been running the last few days to see if I could replicate the issue, or if it is solved by longer breaks between the useitem commands or some other change. No results so far to prove if it is solved or not, so hopefully in a bit I can say if is or is not solved. It's one of those tough issues, as you do not know it is a problem until it actually breaks and you catch that happening.