Quote:
Originally Posted by pwebranflakes
...I'm going to assume you meant your combat log, though. If it's real time, that sounds like it is a plugin or a 3rd party program attached to the actual game. This also is strictly not allowed and violates the EULA/ ToS.
|
Hey Brandon, could you provide input about the particular case I'll describe below?
STO currently has the /CombatLog command set up so that it prints real-time log data to the combat log file. That is, if I shoot at something and do damage, a few milliseconds later it appears in the combat log file and can be read by other programs. (Literally, I can just open the log as a text file, scroll to the bottom, and the information is there.) Would a parser that _only_ monitors the combat log and reports "real-time" information based on what's being output to the log be considered a plugin or 3rd party program attached to the actual game? I don't think so, because the parser is only examining something that STO _explicitly outputs in real time_, and doesn't hook into the game client executable or scan memory; in addition, I'd like to note that many popular combat log parsers (ACT included) have the option to display some "real-time" data based on what's being output to the combat log. I'm interested to hear Cryptic's official position on this matter. I couldn't find anything in the TOS about this particular situation...
This post has been edited to remove content which violates the Perfect World Entertainment Community Rules and Policies . ~BranFlakes