can you show me the output of display(demonnic.roomItems) and display(gmcp.Room.Info.exits) please?

Nevermind, fixed it myself. Was just a punctuation thing with an exception I added

So I've been using this bundle for a few days now, and have been enjoying it thoroughly. But an interesting problem has happened with the influencer. Until last night, it worked like a charm. Now, every third attack instead returns a "Come Again?" type message from Lusty, which leads me to believe that the influencer is trying to use praise, which I don't have. I know that the skill list is supposed to be auto-pop'ed by GMCP events, so I'm not sure where this is coming from since none of my hack gui code has anything to do with that, and that's the only thing I've messed with since the last time it actually worked properly. Just to be sure, I rolled back my profile to the last save that I KNEW had a working influencer, and yet the problem persists. I haven't checked all the influence types, but I tried weakening, and it had the same issue (and I don't have that third skill, either). So I don't even know where to begin fixing this.
as usual.

Edit
Okay, I didn't manage to figure out why it was screwing up and not fixing, so I just did a clean install on a new profile and everything's better.

Which leads into my next question of how do I move the chatbox. None of the default settings work for me. What I'd like is for it to be in the bottomright corner but in more, away from the edges. As it stands it runs into my fancy GUI graphics and looks a mess. Unfortunately, the bottomright settings are written in machine code and I haven't been able to mess with them in a way that moves it where I want without breaking it entirely or causing huge spaces on the righthand side of the chatbox. I appreciate the complexity of all this, but it makes it hard for someone like me to customize, and I'm willing to blindly screw with code for quite a while before giving up

OK, so I was using your old package, but I updated to this new one since I updated Mudlet and am now using GMCP. It works great, and I especially like that the chat and calendar reposition themselves to not be behind the map (which the old version didn't do). However, whenever anything matches for the chat and is captured, I end up with it appearing twice in the Chats. I'm not actually using the Tab feature: I just have one window called "Aethers". Any idea what the problem might be, and how I can get it to only appear the once? I've gone through and made sure to delete all the old files from the previous package.

You have to have at least two tabs, because one is the 'bucket'. When you tell it to echo to a certain tab, it echoes to that tab -and- the bucket. So if you have everything echoed to 'Aethers', and 'Aethers' is your bucket, it goes to the same window twice. To stop using the bucket, go to the config options script and set demonnic.chat.config.Alltab = false

Excellent, thanks!

I've been using an older (modified) version of this influencing script, and it has always worked perfectly fine for my purposes. I got the m&m influencer but I like this one because it captures new arrivals to the room too.

However, it suddenly stopped working for me today. I turned on GMCP in Mudlet at last, not sure if that would've impacted it?

Here is the alias, which the client no longer recognizes or fires:



demonnic.influencer.typeOfInfluence = empower
demonnic.influencer.actionExit = "drink bromide"
demonnic.influencer.massInfluence = false
demonnic.influencer.actionNext = 1
demonnic.influencer.actionCancelled = false

demonnic.influencer.actionList = {
"compliments",
"admiration",
"praise"
}
demonnic_onInfluenceContinue()
enableTrigger("influenced successfully")
enableTrigger("not in the room!")


And the script:



demonnic.influencer = demonnic.influencer or {}
demonnic.targetList = demonnic.targetList or {}
function demonnic_getRoomItems()
send("ih")
SDebug("influencer", "Ok, checking the room items!")
demonnic.roomItems = {}
demonnic.roomItemTypes = {}
demonnic.ihTriggerId = tempLineTrigger(0,200,])
SDebug("influencer", "Ok, we just setup the trigger for readRoomItems")
end

function demonnic_readRoomItems()
selectString(line,1)
replace("")
SDebug("influencer", line)
local item = line:match(])
if item == nil then
SDebug("influencer", "This is not an item, so we stop looking")
killTrigger(demonnic.ihTriggerId)
demonnic.ihTriggerId = nil
send("config pagelength 40")
else
item = item:match("%w+%d+")
SDebug("influencer", "The item is " .. item)
local type = item:match("%a+")
SDebug("influencer", "It is of type " .. type)
demonnic.roomItemTypes = demonnic.roomItemTypes or 0
demonnic.roomItemTypes = (demonnic.roomItemTypes + 1) or 1
table.insert(demonnic.roomItems, item)
deleteLine()
end
end


function demonnic_influenceComplete()
if demonnic.influencer.massInfluence and #demonnic.targetList > 0 then
SDebug("influencer", "we're mass influencing, and there are more targets")
demonnic.influencer.target = table.remove(demonnic.targetList)
SDebug("influencer", "Next target is " .. demonnic.influencer.target)
target = demonnic.influencer.target
else
SDebug("influencer", "alright, nothing left to influence")
demonnic.influencer.actionCancelled = true
demonnic.influencer.massInfluence = false
target = ""
end
end

function demonnic_extractEntityType(entity)
demonnic.targetList = {}
SDebug("influencer", "We're now pulling all items of type " .. entity .. " from the room item list")
for i,item in ipairs(demonnic.roomItems) do
temp = item:match(entity)
if temp ~= nil then table.insert(demonnic.targetList, item) end
end
if #demonnic.targetList > 0 then
SDebug("influencer", "There are targets!")
demonnic.influencer.target = table.remove(demonnic.targetList)
SDebug("influencer", "And our current target is: " .. demonnic.influencer.target)
target = demonnic.influencer.target
else
demonnic.influencer.actionCancelled = true
demonnic.influencer.massInfluence = false
secho("Either you've failed to provide a type of target that's in the room, or you've muffed the syntax")
end
end

function demonnic_onInfluenceContinue()
SDebug("influencer", "Time to influence again")
if demonnic.influencer.target == nil then
SDebug("influencer", "No target to influence. Time to stop influencing")
return
end
SDebug("influencer", "We have a target, it is " .. demonnic.influencer.target)
if demonnic.influencer.actionCancelled == false then
SDebug("influencer", "The action has not been canceled")
if demonnic.curEgo <= (demonnic.maxEgo * 0.20) then
SDebug("influencer", "Time to run, less than a quarter ego remaining")
secho("FLEEING")
send(demonnic.influencer.actionExit)
else
SDebug("influencer", "No need to flee.")
if demonnic.influencer.actionNext > #demonnic.influencer.actionList then
SDebug("influencer", "Ok, our next action is greater than 3, time to go back to 1")
demonnic.influencer.actionNext = 1
end
demonnic.influencer.action = "INFLUENCE "..demonnic.influencer.target.." WITH "..demonnic.influencer.actionList
send(demonnic.influencer.action)
demonnic.influencer.actionNext = demonnic.influencer.actionNext + 1
demonnic_chaser(], {consumesBal = false})
end
end
end


Please help, I really liked this script!

EDIT:
figured it out through some very crude method

Just started using it, and I love it. The whole package. Thank you for making this available.

A suggestion, while I'm at it: Would it be possible to include Stratagem in the harvester and the influencer?

Terqiq:

Just started using it, and I love it. The whole package. Thank you for making this available.

A suggestion, while I'm at it: Would it be possible to include Stratagem in the harvester and the influencer?

I've been gone for long enough that I have no idea what that means... but I'm trolling the forums in an effort to come back before too long. I'm still working stupid hours, and I'm dealing with a bunch of other stuff besides... but I've got to find something to relax with, and I do so miss Lusternia...

Anyways, if I manage to actually come back, I would be delighted to see about adding this.

It's basically just a server-side queue system, Dem. Pretty damned awesome, actually. Nowhere near as good as a proper client-side system (it ignores many afflictions) but for something like this, it would be great.

I still use your influencer, but I am also away from the game at the moment. I'll see about adding it in should I be able to return before you do.

Hope things are well with you and will surely chat soon!

-phasma

The major problem I've been having with this system (which I use for harvesting and the tabbed chat) is the calendar not automatically updating when I log in. It gets stuck on the 5th of Dvarsh 294 AE (or something akin to that), and I have to wait for a long time before it gets refreshed. Maybe include a manual updater?

It probably just needs the regex changing.

Draylor:

It probably just needs the regex changing.

This. The regex messes up on the moon phase I think, I fixed it in my stuff some time ago, but can't access it, nor do I recall what the fix was.

Duly noted. I'm devoting a chunk of time tomorrow to updating the mudlet wiki and looking into changes such as this for my packages. Give them a bit of an update. Actually play some, maybe... I've even informed the wife I'm going to be in geek mode and we should be prepared with buffalo wing flavored pretzel bites and coffee. Anyways... hopefully tomorrow I can knock out several small bug fixes.

Gimme a holler when you start. I'll chip in.

Minor update, 2.1 pushed

Having a great time with the influencer, thanks. I can't figure out how to get the tabbed chat to work though. Is it automatically on? If so, then I am failing at something and I'm not sure what, but I don't have a separate tab for chatting.

It should be on, yes. And default to the top-right corner. What version of Mudlet are you using, and do you have any errors in the error console of the script editor?

Do you have any other packages with UI elements installed?

I'm on Mudlet 2.0test4. I just have m&m installed with m&m beastmastery. I have a bunch of errors when I hit the error button in Mudlet and since I'm a giant noob, I have no idea what they mean. Should I PM those to you?

yes... specifically if you would capture everything out of it from a fresh restart of mudlet up through getting logged in. That should capture any relevant errors without too much kruft to sift through.