ambra5555

On 12/12/2017 at 2:17 AM, Aquamentis12 said:

And saving the chats to the computer is also a must.

Can you clarify this? You mean an export feature, or automatically saving? Although I get that it's nice to not depend on a server to have your chat history, overall having your chat history saved on the program's server is safer because even if your computer breaks you won't lose anything.

I don't recommend Skype (it once lost ALL my messages and even contacts, and it's a memory hogger) or whatsapp (the web version only works if you have it installed and running on your phone, and you don't have one).

If you use Facebook, their IM feature is pretty popular so it should be easier for you to find your friends there. It saves messages on their servers, but there's a way to export them to your computer (I did it once and it works fine, it just takes a bit of work). But it's also a total memory hogger. The IM I use is Telegram, it's great, lightweight and secure, but it doesn't have any kind of history export feature, although it does work with Pidgin. You could also try and make a bot that automatically saves your messages (since you only use stuff on your computer, it should be easy enough), but it's a stopgap. Plus you'd have to use the bot's account to chat instead of your own. But yeah, ever since MSN I haven't seen anything with automatic local history saving.

You could also ask for help with Discord! It never messed with anything I had, so your issues are probably fixable. There's a script that exports histories, although once again it's not automatic.

24 minutes ago, okkusu said:

It doesn't matter on what difficulty, or from what team the opponents are?

Nope, as long as it's ten fights you'll get the boons. You can even fight the same opponent ten times on easy and you'll get them!

It's definitely slow. TNT said the plot was slow last month so we could have time to play the GMC, but now it's over and it still feels super slow...

Hi! This CSS works solo to change that height:

.bx-viewport {
	height: 250px !important;
}

But it conflicts with your current userlookup's code. I'm not sure what part conflicts, but I can try to find it if you want. Leaving your code as-is, add this CSS instead:

.bx-viewport {
	height: 274px !important;
}

The gist of it is that, for some reason, Neopets cuts that div ten pixels before it should. That element is added by JS, too, so finding out what exactly went wrong would make for a prettier way of fixing that height, but it would also be a pain because the related code is all minified and I hate one-letter variables. So right now, the way to go is find out the value of that element's height in your lookup, and then add CSS to change the height so it'll be 10px taller.

In simpler words, right now if you look at your lookup the bx-viewport div is 264px high, which is why you have to change it to 274px. In default lookups, the div is 240px tall and must be changed to 250px.

If anyone wants to go hunting for that prettier way to fix it, the culprit is the bxslider code.