Hey Guys... I have a concern about Resources usage.
I run on my UI Setup, Antagonist, SCT and other Combat Parsing addons.
Problem is that with those, I have enabled as dependencies, ParserLib, Parser 3.0 and LibParser 4.0 all at the same time. Ain't It using too much resources for the single task of Combat Parsing???
You should just be able to use LibParser-4.0 - though SCT was only tested against ParserLib and Antagonist only against 3.0.
Bumping an ancient thread because the issue I'm going to report is tied in directly with this comment ;).
After doing some testing to make sure LibParser-4.0 could adequately replace the earlier Parsers (Parser-3.0 is quite the resource hog), decided to enable SCT to see how it would be affected.
With both LibParser-4.0 & ParserLib running, no problems with SCT. Turn ParserLib off and continual errors from SCT (latest revision r59352). So LibParser-4.0's compatibility layer isn't 100% yet.
Once per session, but every session when Sink output was modified or other SCT options were changed: sct\\sct.lua:15: attempt to index global 'ParserLib' (a nil value)
Be interesting to see how this mod evolves in WoW 2.4 and/or if its going to be updated to use more modern libraries. In the meantime, don't run SCT without ParserLib (Parser-3.0, which also has a compat layer for ParserLib, is more of a resource hog). Or switch to Parrot or MSBT.
All versions of ParserLib are deprecated with patch 2.4. To use any "parsing library" would be counter-productive because you no longer need to "parse" combat log strings to get the arguments you need -- Blizzard events code now gives you the arguments directly.
That's not entirely true yet Xinhuan. Some information provided by parsers is not yet given to us by the new combat log in 2.4. Mainly Experience, Honor, Reputation, Skill Gains, etc...You can use the Blizzard combat text (not log) events to get a few of these, but not all. Until the 2.4 combat log is updated to include those events, you will still need to do parsing, either manually or with a library.
Zidomo, LibParser-4.0 and Parser-3.0 are not "new" versions of ParserLib-1.1. They are total remakes that "tried" to make mods that use ParserLib use theirs instead with forceful compatibility. SCT does not and will not ever directly support anything but ParserLib-1.1. If the authors of the others can make them work with ParserLib based mods then great, but I will not be updating SCT to work with them directly.
When 2.4 goes live SCT will be using the 2.4 combat log for most things, and ParserLib-1.1 (or if rophy creates a new one) for those few events I mentioned above that still need to be parsed. I was hoping to be able to use the Deformat lib to do these few events, but unfortunately there are still way too many global strings to worry about even for those few events. Maybe Blizzard will update it to send those events in the new formatting before it goes live.