New GINA crashing issue

GINA was never a business for Gima, it's always been a hobby like some of the other programs written and maintained by other folks, GINA doesn't HAVE to be patched...

This will be fixed in the May patch.

That's fair but they should at least make the source code available.

So this indicates GINA literally needs to do nothing. EQ Mistake and they have expressed time and time again they do not care about 3rd party programs.....sooooo

Opinions you know the saying.

I think it's something I'm never going to do.

It depends in part what exactly you mean.

1) Uploading your existing log file isn't difficult, and in fact the test version I'm working on already includes that functionality. It's disabled by default but it works. It's both a proof-of-concept for a similar idea and an easy way for people to send me log files since email is not good). Sending only *part* of a log (like a single fight) is a whole other thing entirely and GamParse isn't built for that. It's not impossible of course, but that leads into:

2) The server would have to parse every log once to sync them, then parse them again for the actual damage calculations. How complicated it would be is proportional to how much information is supposed to be returned. Just a damage list? Spell cast lists? Tanking lists?

3) Even something as "simple" as uploading each person's individual damage and collating them into a single list isn't quite as easy as it appears. The reason for this is because while I realize that raw dps is what gives most of you boners, I know that its completely worthless as a method of comparison. What matters is total damage, and sdps, which is total damage / total time.

This is fine when you're parsing yourself, but when you start attempting to combine parses you end up with different total damage and different total time depending on how close someone is to the action. Basically, it's worthless to just create a list. It HAS to be parsed to be accurate, which means writing a program/script to do it. And I don't want to. Which leads me to:

4) GamParse is very accurate if you are in range of the fight. There is really no need for a complicated system to combine parses. There are very, very few instances where a personal parse will show more than a parse by someone close to the NPC.

I'll probably regret this, but if he doesn't want to continue to maintain it, I'll offer to do it.

in-line active/cooldown timers pls

It's just common decency when you abandon a project when there's still active users. Not really hard to understand.

It hasn't been abandoned. It's still being maintained, unfortunately he wasn't able to complete the fix last night but i know for a fact that he is working on it tonight.

That's cool then. I misunderstood what you were saying in the previous post.

Here's the temporary fix: http://eq.gimasoft.com/forums/viewtopic.php?f=3&t=261

Kinda late now but I just did this in bash
tail -f eqlog_myname_myserver.txt | sed -u "s/^\[\(...\) \(...\) \(.\)/\[\1 \2 0\3/" > newlog.txt &

tail -f eqlog_Bigstomp_bristle.txt |perl -ne's/^(\[\w{3}\s\w{3})\s(\s)/$1 0/; print;' >eqlog_Bigstomp_fixed.txt

You don't need 3 captures, only 1.

And yes, I realize looking at it now I have 2 captures in mine. The 2nd is entirely useless.

Can someone who is able to contact him pass on that any fix he makes this coming weekend could be broken again when the format is changed back in the May patch.

I have it on good authority that the fix works with both types of log files, so even after the patch in May it will be fine.

This fixed the crashing for me...but no triggers work.

Everything works for me.

Odd not had a moments problem with mine. No crash's, it works fine.

It kept working, until you restart it. As soon as you do that, it will crash on start.