Putting up add-ons on 1.9

[Velensk]

When I attempt to add one of my add-ons to 1.9 the game crashes much as it does if you try to get to the multiplayer server through the direct link. I can see that there are add-ons on the server so it must be possible to do and I was wondering if there was any special requirement to get add-ons onto it.

Incase it helps, I am using a mac and the .pbl was simply copied from the 1.8 version of the add-on.

[Iris]

AFAIK what's recommended for now is to use the wesnoth_addon_manager script instead of the built-in game client, but since it's rather complicated for non-Linux/pure BSD users, you may want to avoid wasting efforts in 1.9 until the next version.

Either that, or learn how to use wesnoth_addon_manager, which even beats me sometimes.

EDIT: actually, the aforementioned recommendation is in the Wesnoth 1.9.0 release announcement, under Known Bugs.

[Exasperation]

If you decide to try to use the wesnoth_addon_manager script, the necessary command to upload to the 1.9.x add-on server (or at least the one that I got to work under windows) is

Code: Select all

<full path to python.exe> <full path to wesnoth_addon_manager> -p 1.9.x -u <full path to your add-on>

[Anonymissimus]

If you decide to try to use the wesnoth_addon_manager script, the necessary command to upload to the 1.9.x add-on server (or at least the one that I got to work under windows) is

Code: Select all

<full path to python.exe> <full path to wesnoth_addon_manager> -p 1.9.x -u <full path to your add-on>

OK, how many of the authors who have their add-ons on the 1.9 server were doing this from a windows machine ? I've downloaded ATBX and your init-icon.png is a corrupted file, the same happened with my image files. So the uploading of binary files doesn't seem to work. Text-only files like .cfg and .lua work however, so in the case of ATBX it's (almost) sufficient.
I don't feel like trying to fix it since the addon_manager is usually pretty unimportant.

[Exasperation]

Well, since init-icon.png is both unfinished and unused (I had forgotten about moving it into the ATBX directory for testing purposes before the last time I uploaded), it doesn't matter in this instance, but I think you should probably file a bug report anyway.

[Anonymissimus]

I've uploaded from my ubuntu dual boot and unsurprisingly it worked, although the files are exactly the same. (a separate BfW installation isn't needed). A bug report isn't going to be of much use however since the seemingly only one who's capable of fixing it (esr) is never going to test on windows.
https://gna.org/bugs/?16649

[Max]

any chance it's caused by this line (data\tools\wesnoth\campaignserver_client.py):

z = gzip.GzipFile(mode = "w", fileobj = io)

(shouldn't it be set to wb?)

how do those files differ?

[Anonymissimus]

Thx but silene "fixed" it. Uploading campaigns with the syntax described by Exasperation above should work now. I couldn't figure out how to do it with the "other" syntax however which you get informed about when running with -h option, but it seems relevant only for the old-style campaign syntax with the external .cfg file instead of _main.cfg.

[sur.nhm]

Not Completely Off-Topic

I know for sure that at least one add-on maintener (I8) is waiting for 1.9.1 before moving the add-on to 1.9 because of the uploading mechanics.

[Anonymissimus]

Replacing data/tools/campaignserver_client.py with the version from the source repository
http://svn.gna.org/viewcvs/wesnoth/trun ... y?view=log
should do the trick. Anyone able to handle wmllint should be able to handle the addon manager too.

[Sapient]

I just used my 1.8 client and uploaded it to addons.wesnoth.org:15002

As a Windows user, that will probably be faster and easier for you than the python options.

[Alarantalara]

There still seems to be some problems in 1.9.1
While the addon manager works fine, I am told that my passphrase is incorrect for the addon when using Wesnoth itself.

[Astoria]

There still seems to be some problems in 1.9.1
While the addon manager works fine, I am told that my passphrase is incorrect for the addon when using Wesnoth itself.

Never happened to me...