Pentarctagon wrote:Yeah, I couldn't tell you why it's putting all the units under the portraits add-on, but the errors it reports are all about missing units, so adding the [binary_path] should fix that. Also, the add-on size limit was increased to 100 MBs for 1.13, so going forward you would be able to combine them back into a single add-on.

Pentarctagon wrote:Yeah, I couldn't tell you why it's putting all the units under the portraits add-on, but the errors it reports are all about missing units, so adding the [binary_path] should fix that. Also, the add-on size limit was increased to 100 MBs for 1.13, so going forward you would be able to combine them back into a single add-on.

What add-on size limit is (was?) for older versions? 1.12 for example

For older versions, there was no size limit.

99 little bugs in the code, 99 little bugs
take one down, patch it around
-2,147,483,648 little bugs in the code

A 1.13.x version (I think it was 1.13.5 but I'm not sure) shipped with a rewrite of the network code that resulted in the add-ons server gaining a maximum pack size. The issue was discovered after the release and patched one or two releases later.

Just a heads-up for people who might be keeping an eye on units.wesnoth.org: the rebuild task might not run this week due to some major pending changes coming from my direction rather than Elias’, for a change. My apologies for any inconveniences this may cause. I’ll make sure to keep you notified of any new developments from that front and figure out the best schedule to run the rebuild as soon as it is all done.

units.wesnoth.org has been rebuilt and it now has a fix for an issue where [portrait] tags (which are gone in 1.13.x and were never intended to be used by the general public in the first place) were used to read unit portraits instead of the profile= attribute.

Oh and it also uses the new site design now.

There is an issue where the sidebar menus do not work until the page has fully loaded, which tends to take a lot of time on my end due to the absurd number of images on the unit tree pages. Assuming I don’t get too busy with other stuff, I will rectify this before the next rebuild.

shadowm wrote:units.wesnoth.org has been rebuilt and it now has a fix for an issue where [portrait] tags (which are gone in 1.13.x and were never intended to be used by the general public in the first place) were used to read unit portraits instead of the profile= attribute.

Oh and it also uses the new site design now.

this script you are using to build unit database pages - is it available for download?

It’s wmlunits, which is part of the Wesnoth source code distribution (data/tools/wmlunits — note that it has several dependencies on the rest of the included scripts). I don’t think I’m the best person to explain how it works, though. There’s a --help switch, and this is what I use to run it:

Before this commit it used a bundled minimal version of Glamdrol (provided as data/tools/unit_tree/style.css) that contained additional units.w.o-specific styles. Now it uses the shared site stylesheet and a smaller units.w.o-specific supplement stylesheet, all built from the Wesmere source code but not part of the main repository. So it hasn’t really ever “generated” any CSS other than a few inline style attributes.

I strongly advise against using older versions of wmlunits on untrusted data, though (see this commit).