Hey I got none, just wanted to start a topic for it! :)

I do have a feature request though. For party window, have the hp/sp/ep bars be the same colour as in ps and pss.
So when youre really low on something have them turn red, green when full etc...

I support the idea, however, I think as a workaround you can always do that with a beanshell trigger.

Bug
- The OOF window is super cool but if a player is a member of your party, goes link dead then you party kick his silly portrait stays in the window forever.

Cheers,
Askan

Thanks Askan, this was the one "in the know" already, but there are other similar-to-this type of party bugs in the new party window-system, still. If you have some time to find/report the others, we'd appreciate it.

Amarth

It also appears that if i'm not the one to create the party the party window and oof windows don't function.

That mite be old news too thou :)

Found a serious problem with autologging.

I turned it on last night, and when i started the client this morning it wouldn't load (just hanging there with the java virtual machine running)
I went into the config.xml and set the flag to false then the client loaded normally.

On 64bit vista as an administrator with that annoying user control feature turned off.

Cheers,
Askan

Something very minor!

I opened the client, closed the login window, chose "reconnect" from the bottom menu, and did my login on the generic window.
Everything worked fine except that the client echoed my password and remembered it in the history list too! omg! :)

I had the same problem with askan concerning autologging. In fact the client did start eventually after 12-13 minutes (Yea, I guess I have a big patience). I removed autologging and now it works fine. Im running it on XP so it's not vistas fault.

The client seems to load only one plugin.

Nevermind, it works now, and I couldn't recreate the problem. No idea what was causing it. :/

Ok, need more information on the "autologging bug" to be able to reproduce it.. Any specifics would do.

The autologging bug happens when you start the client and the logfile where the client starts to log is really large already. For example if you start batclient on 28.01.2008, have autologging on for generic tab and there already is a log file named "20080128-Generic.txt" that is big, like 6Mb, the client won't start up.

Moving/deleting/renaming the logfile, killing javaw.exe process and restarting the client is the best way to cope with the bug atm.

I'm not sure if this is the case with scipts/triggers, but if you have a plugin that triggers some text, and the text comes in two tcp packages, it doesn't get triggered.

EDIT: the same bug is in the normal triggers too. (and in version 1.61)