If you have a question you would like answered, I would very much appreciate you checking for an answer in the BOSS Userlist Manager FAQ before posting.
New users should take a look at these sections in the Help...
- Getting Started ›› Rule basics, Recommendations #2 - Getting Started ›› Creating Rules ›› The ADD Rule
The latest B.U.M. combined with BOSS 2.3.1 found a malfunctioning idkrr race, possibly Corean, then freezes leaving a blank interface with a row of red text on the right side. The previous versions of both work with no problems.
Alrighty, here's the latest: BOSS has a problem with sorting mods in the userlist if the rule includes a mod that is not in your load order. I've been in contact with the dev, and he's looking into it. We're still trying to work out exactly what and how... but that doesn't concern BUM. However, with BOSS 2.3.1, BUM still doesn't work 100% right, and I don't think it's the fault of BOSS (but it may be). After adjusting the userlist via BUM, run BOSS through BUM and after BOSS does it's thing and you have seen the report, BUM wants to add all of the plugins in your load order to the userlist. U can just close BUM without saving the userlist to work around this behavior, but it's still an error. I'll keep you posted as new things come to light.
The behaviour you describe doesn’t make sense to me – BUM starts by processing the BOSS Masterlist to determine what is defined and what is not defined. This processing is repeated after running BOSS to deal with any changes to the Masterlist. The implication, from your description, is that after running BOSS, the Masterlist is empty or has been updated in a way that BUM does not handle, so it thinks that there are no entries.
Just to confirm, are you saying that when you start BUM, it processes everything correctly. You run BOSS and then |BUM thinks nothing is defined in the Masterlist. You close BUM without saving and restart it and everything is OK again. Is this the behaviour you are seeing?
I wonder if it is a timing issue with the new BOSS - BUM will start to process the Masterlist as soon as BOSS opens the browser, perhaps the new version has not yet closed the file or is still writing to it.
Instead of closing BUM when everything is undefined, can you try reloading the Userlist from the Userlist Menu and let me know what happens.
Does look like I will need to try the new BOSS and see if I can figure out what is happening - when I get some time
I just downloaded the new version and was able to reproduce the problem.
It is caused by the line terminators for the modlist.txt being changed. I have got a fix for this that deals with both old and new formats and will release in the next day or so.
Ok, I'm back with a bug report (this time it shouldn't be premature). For some reason, all of the recognized plugins are showing up in the User Rules window as unrecognized, all in one continuous line. Clicking the long list of plugins brings BUM to a almost blank page that just shows each plugin in a list one by one. I have to exit BUM to restore functionality. So, BUM and the latest BOSS do not appear to be 100% compatible.
I'm continuing to dig into this and it appears BUM adds all recognized plugins to the UserList. If I clear the recognized plugins from the list manually, run BOSS, it crashes BOSS. I'll post more as I find it, but it may be best if you download the latest BOSS and see for your self.
...And further digging... It appears there is a problem with BOSS 2.3.1 as well as BUM. I don't know if sorting the BOSS problem will also sort the BUM problem, but I've let the guru's handling BOSS know about the problem. It seems the new BOSS can't parse a userlist with entries in it. If it is blank, there are no problems, but if there is anything in the list, BOSS crashes.
I think I will wait for the BOSS issue to be resolved first before I start trying to solve compatibility issues that may not be there,
Please let me know your findings once the BOSS issue has been resolved so I can determine whether any changes are necessary - I hope not, haven't looked at BUM's code for some time
BOSS has been updated. Is there anything you need to do, Surazal, to make BUM compatible? I'm having issues running BUM thru Mod Organizer. BUM reports that a "ModList" file is not present. The virtual directory doesn't seem to be recognized by BOSS either. I don't know if it is do to BUM or MO, but I thought I'd start by informing you.
Thanks.
EDIT:
Nevermind, Surazal. All is well. I just messed up a setting. Everything seems to be running okay. I hate it when I premature post.
Did you make BUM 6.8 a 64 bit program? I'm trying to launch it through Mod Organizer and it crashes at launch. I've read the FAQ, and the "solution" there doesn't work. If BUM is now 64 bit, then it will not be able to launch via MO, so I'm wondering if it is.
You are the second person to ask, so I ran it on my machine and checked with the Task manager to see what it was and, much to my surprise, it was running 64-bit.
There was nothing I changed to make it specifically 64-bit, but it may be the new version of Visual Studio that I am using.
I will make some changes so that it runs as 32-bit and release another version as soon as I have time.
Thanks for making me use the task manager to check (never knew it could tell me which-bit a program was )
Give Feedback
145 comments
New users should take a look at these sections in the Help...
- Getting Started ›› Rule basics, Recommendations #2
- Getting Started ›› Creating Rules ›› The ADD Rule
Thanks
[size="4"]Features and Fixes[/size]
The behaviour you describe doesn’t make sense to me – BUM starts by processing the BOSS Masterlist to determine what is defined and what is not defined. This processing is repeated after running BOSS to deal with any changes to the Masterlist. The implication, from your description, is that after running BOSS, the Masterlist is empty or has been updated in a way that BUM does not handle, so it thinks that there are no entries.
Just to confirm, are you saying that when you start BUM, it processes everything correctly. You run BOSS and then |BUM thinks nothing is defined in the Masterlist. You close BUM without saving and restart it and everything is OK again. Is this the behaviour you are seeing?
Instead of closing BUM when everything is undefined, can you try reloading the Userlist from the Userlist Menu and let me know what happens.
Does look like I will need to try the new BOSS and see if I can figure out what is happening - when I get some time
It is caused by the line terminators for the modlist.txt being changed. I have got a fix for this that deals with both old and new formats and will release in the next day or so.
I'm continuing to dig into this and it appears BUM adds all recognized plugins to the UserList. If I clear the recognized plugins from the list manually, run BOSS, it crashes BOSS. I'll post more as I find it, but it may be best if you download the latest BOSS and see for your self.
...And further digging... It appears there is a problem with BOSS 2.3.1 as well as BUM. I don't know if sorting the BOSS problem will also sort the BUM problem, but I've let the guru's handling BOSS know about the problem. It seems the new BOSS can't parse a userlist with entries in it. If it is blank, there are no problems, but if there is anything in the list, BOSS crashes.
I think I will wait for the BOSS issue to be resolved first before I start trying to solve compatibility issues that may not be there,
Please let me know your findings once the BOSS issue has been resolved so I can determine whether any changes are necessary - I hope not, haven't looked at BUM's code for some time
Thanks.
EDIT:
Nevermind, Surazal. All is well. I just messed up a setting. Everything seems to be running okay. I hate it when I premature post.
[size="4"]Features and Fixes[/size]
There was nothing I changed to make it specifically 64-bit, but it may be the new version of Visual Studio that I am using.
I will make some changes so that it runs as 32-bit and release another version as soon as I have time.
Thanks for making me use the task manager to check (never knew it could tell me which-bit a program was