-
You've discovered RedGuides, an EverQuest multi-boxing and scripting community 🧙♀️⚙️. We want you to play several EQ characters at once, come join us and say hello! 👋
- Thread starter aquietone
- Start date
- Joined
- Jul 23, 2020
- RedCents
- 650¢
That worked!, thanks for all your hard work on this, have a lovely day!
I could use a hand with the following error if anyone has a moment.
C:\Next\Lua\boxhud\settings\settings.Lua:94: attempt to call field 'loadTheme' (a nil value)
stack traceback:
C:\Next\Lua\boxhud\settings\settings.Lua: in function 'ValidateOptionalSettings'
C:\Next\Lua\boxhud\settings\settings.Lua:118: in function 'ValidateSettings'
C:\Next\Lua\boxhud\settings\settings.Lua:191: in function 'LoadSettings'
C:\Next\Lua\boxhud\init.Lua:214: in function 'main'
C:\Next\Lua\boxhud\init.Lua:259: in main chunk
Ending Lua script 'boxhud' with PID 14 and status -1
I'm getting this when I /Lua run boxhud
I've tried a re-install but didn't want to mess around in the .Lua file and make any changes I wasn't sure I should make.
C:\Next\Lua\boxhud\settings\settings.Lua:94: attempt to call field 'loadTheme' (a nil value)
stack traceback:
C:\Next\Lua\boxhud\settings\settings.Lua: in function 'ValidateOptionalSettings'
C:\Next\Lua\boxhud\settings\settings.Lua:118: in function 'ValidateSettings'
C:\Next\Lua\boxhud\settings\settings.Lua:191: in function 'LoadSettings'
C:\Next\Lua\boxhud\init.Lua:214: in function 'main'
C:\Next\Lua\boxhud\init.Lua:259: in main chunk
Ending Lua script 'boxhud' with PID 14 and status -1
I'm getting this when I /Lua run boxhud
I've tried a re-install but didn't want to mess around in the .Lua file and make any changes I wasn't sure I should make.
pushed a fix, should update in ~50 minutes when rg pulls from github again.
You rock!
Copying a post from mq2druid as this likely applies to cwtn/sic mq2druid and mq2wizard plugins where they do not show toon info within boxhud by default at the time of this post. You will need to edit the properties for CWTN.Mode/Paused/etc to add wiz,dru as shown below;
Shadow
Ultimate seasoned veteran member
- Joined
- Feb 15, 2022
- RedCents
- 1,877¢
Are they in the same zone? Just reset observers. I have had zero issues with Boxhud since release except for the occasional hiccup in reporting that reset observers always fix.
Yes. All in the same zone. Just some columns are not updating in real time. I reset, it will give me current information, and then be out of date in 5 mins. I can't restart it constantly, so i generally just deal with it. But cwtn.paused is one i am constantly having to check. Character wont be paused but it will show paused.
There is a setting to toggle whether boxhud will work or not, but the setting is currently out of order.
Shadow
Ultimate seasoned veteran member
- Joined
- Feb 15, 2022
- RedCents
- 1,877¢
How many toons at one time? Most I have running is 18 and never seen this issue. Additionally, have you added the properties for the classes you use correctly?
anywhere from 12 to 36. And yes. It doesn't show nothing, it shows the wrong answer cause it wont update. When i reload, it shows the right answer. For example, I have a column that shows CWTN.paused status. it updates fine, until it stops, and it shows toons paused that aren't after a while, and stops updating across all characters i got loaded. If I reload, it works fine, for a few minutes, then it stops.
Shadow
Ultimate seasoned veteran member
- Joined
- Feb 15, 2022
- RedCents
- 1,877¢
Ok, next question. Are you running grinds? Let's assume Restless Assault. Sometimes data is not updating correctly with multiple groups because of instance ID that I have seen. But when they are all together in say GH, they don't update unless I reset. But if I stay in GH for 6 hours, and come back and pause/unpause, etc.. no issues.
Trying to help but maybe I'm just convolution the issue.
Is the CWTN paused your own property or the built in? Boxhud only running on MT(s)?
Do you have the same settings for each instance of boxhud?
Trying to help but maybe I'm just convolution the issue.
Is the CWTN paused your own property or the built in? Boxhud only running on MT(s)?
Do you have the same settings for each instance of boxhud?
Undefeated
Well-known member
- Joined
- Jul 27, 2020
- RedCents
- 169¢
How did u make it work? I tried adding this it won't work
- Joined
- Dec 1, 2006
- RedCents
- 1,529¢
I noticed if you have the title bar on, and auto-scale height, it doesn't scale the window correctly. With the title bar off, it works correctly.
For anyone who plays many characters, I found it useful to add the lines below to your character. Lua right after 273 allows you to right-click on a name in Boxhud and have them /exit out.
Cheers!
Code:
ImGui.SameLine()
self:drawCmdButton('Exit##'..self.Name, '/dex %s /exit')Cheers!
don't think so, maybe just reset imgui positions from /mqsettings?
if you have boxhud set to save its own window settings, you can probably just edit your boxhud-settings-character.Lua file. otherwise at the very least i think that also contains the state of the lock button.
I unchecked that when i got my third monitor cause everytime I logged in my windows were somewhere new (and totally not visible). Was a stopgap until I could figure out what the deal was.
- Joined
- Dec 1, 2006
- RedCents
- 1,529¢
Quick question. The main toon I use BoxHud on, has a title bar so I can collapse the window down. Another toon I copied the configuration to did not have the title bar, and I could not find a way in the gui window to turn that on. I ended up going to the ini file for that character and setting it to true, but I was wondering if I missed it somewhere.
- Joined
- Dec 1, 2006
- RedCents
- 1,529¢
Doh! I figured I missed it 
I don't think I have ever clicked at the root of that tree, and just assumed there was nothing there Thanks!
I don't think I have ever clicked at the root of that tree, and just assumed there was nothing there Thanks!
I am beyond in love with Boxhud, sans a very tiny annoyance:
It does not play nicely when docked/tabbed with other imgui windows; meaning, when it is next restarted, it will be in the same location, but will be in its own window... on top of the window with 3-4 tabs of other scripts' windows. I'll have to unlock and drag it back into that window to make it a tab again (and keeping it unlocked has the same effect).
It does not play nicely when docked/tabbed with other imgui windows; meaning, when it is next restarted, it will be in the same location, but will be in its own window... on top of the window with 3-4 tabs of other scripts' windows. I'll have to unlock and drag it back into that window to make it a tab again (and keeping it unlocked has the same effect).
I really like Boxhud, and I use it all the time... Makes it easier to switch between characters. However, today it is not loading right. My daily routine is simple, I log in all my guys, group and set roles. Hit my hotkey (Dannet command) to start Boxhud on everyone, usually there are no issues at all. Today, it only starts up on my MA (who I have the hotkey on), but wont start on anyone else. If I turn it on for everyone manually, on each screen that is the only one that shows up in the Boxhud window. I cant get them all in the same window. I have restarted multiple times, zoned, and tried everything I can think of. Checked to make sure my files are all updated. I dont know what else to do here.
This behaviour sounds to me like a issue with dannet peers not seeing each other, which would result in boxhud not establishing observer links to those peers.
off the cuff, I would suggest to check the following:
- is dannet running on all clients? It may not be loaded for some reason. you can verify in the /plugin list, output or plugin manager if you use that tool. Or simply /plugin dannet on each client
- Are you using a VPN? I've experienced issues like this on a VPN because...
- check your /dnet interface. It's possible the clients are on a different iface (say, vpn, wifi, loopback, eth0, etc). you can /dnet interface 0/1/2/3/etc to force each client to get onto a single one, then reload the plugin (in my experience, it may not be necessary)
- check your /dnet info.. and see if the clients are seeing each other