Smogon Forums

Ugh, size might be a serious issue. 443k is half a megabyte...

It's half as big as the moveset data, and not much compared to pictures. However, it's still big. I did think of a way to trim it down some more though; I think I can get to a quarter meg.

Pictures can be streamed, and moveset data is a huge problem for PS; it's already our largest data source and responsible for a noticeable proportion of the size. And you've said that OU is only one metagame...

In theory checks/counters should be fairly similar between all the metagames; if you could find a way to merge them...

I could set it up to not load the check/counter data until you enter the teambuilder with a team in that tier.

Any given OU through NU stack should merge without too much harm. I'm iffy on Ubers, LC would be very shaky, and cross-gen stuff even shakier still. I would highly recommend only enabling the feature one tier at a time though.

Ubers should work the same way as OU-NU. There are rarely LC Pokémon usable in other tiers, so that shouldn't be a big deal either. I'd probably just turn off the feature for past gens.

Bigger problem would be Hackmons, in which the feature should probably also be turned off. In most other tiers, though, generally if a Pokémon counters another, they're counters as long as both Pokémon are legal in the tier.

The only issue with Ubers is that better counters should exist, in which case we just weigh an Ubers counter higher than an OU counter, same as we go down the list.

Gliscor is 75% effective against Aegislash in OU, but 57% effective in Ubers.

That's what I'm concerned about with merging.

Hm, is it a matter of which sets are more common? Oh well, rate the OU counter data higher, then. Incidentally, I don't know how you're storing the data, but I think just lists of the top 10 counters, sorted, for each pokemon, would be comparatively lightweight.

Yeah, I mentioned earlier that it can be trimmed down. I was storing the weighted version separately. And I later realized that I have the team co-occurance data in there too. So 1/3 as big as I said.

So, how's this coming along?

Sorry for the delay. I think everything's cleared up now; I'll post a repo and send a patch some time tomorrow.

Thanks!

No prob! I sent you a pull request. I'm new to github so tell me if there's anything I need to sort out.

The patch is OU-only, but correctly disables itself elsewhere. The final data file size is 127k, btw.

So, any more thought on the teambuilder?

Sorry, will need some more time. Currently dealing with ladder.

Okay, no problem. Good luck! I took a look at the problem and was only successful in being reminded that PHP scares me.

Since it's been two weeks - friendly reminder to consider using the teambuilder suggestions.