Wesnoth 1.13.7

Get help with compiling or installing the game, and discuss announcements of new official releases.

Moderators: Forum Moderators, Developers

User avatar
nuorc
Forum Regular
Posts: 569
Joined: September 3rd, 2009, 2:25 pm
Location: Barag Gor

Re: Wesnoth 1.13.7

Post by nuorc » March 23rd, 2017, 3:23 pm

DewyB wrote:Shouldn't we be offering the latest STABLE release (1.12.6) at a major site like that ?
I think it's more the case of them picking a version (presumably going by the highest version number) than anyone offering a specific version to them. So you would have to contact them about a remedy.
I have a cunning plan.

User avatar
Pentarctagon
Forum Administrator
Posts: 3484
Joined: March 22nd, 2009, 10:50 pm
Location: Earth (occasionally)

Re: Wesnoth 1.13.7

Post by Pentarctagon » March 23rd, 2017, 11:19 pm

jyrkive wrote:
DewyB wrote:This may be a noob question, but this is one way to learn.
The above post says the Windows download is (369.6 MB)
When I start the download, it says XX.XX/352MB XX minutes left

Is there a discrepancy here? The reason I ask, I have tried to download it twice, both packages were different sizes upon completion, and neither worked (would not even open).
I've had an issue with dropped packets before, but that is supposed to be resolved. Hasn't been an issue recently, but certainly seems to be an issue today.
The thing is, there is disagreement about what "mega" means. It can mean either 1 000 000 (10^6) or 1 048 576 (2^20). We have listed package sizes using the smaller of the two, SI mega. Your browser instead uses the computing mega; with that unit, the Windows installer size is 352,48 MB. So, no, there isn't a size discrepancy.
That's not a disagreement, that's one using the incorrect term. A MegaByte (MB) is 10^6, while a MebiByte (MiB) is 2^20.
99 little bugs in the code, 99 little bugs
take one down, patch it around
-2,147,483,648 little bugs in the code

Shiki
Developer
Posts: 198
Joined: July 13th, 2015, 9:53 pm
Location: Germany

Re: Wesnoth 1.13.7

Post by Shiki » March 23rd, 2017, 11:38 pm

Well, both definitions exist for MB, while MiB is everytime the later one.
Maintainer of Era of Myths.

User avatar
Celtic_Minstrel
Developer
Posts: 1184
Joined: August 3rd, 2012, 11:26 pm
Contact:

Re: Wesnoth 1.13.7

Post by Celtic_Minstrel » March 24th, 2017, 1:05 am

Dugi wrote:
Celtic_Minstrel wrote:The reason it's deprecated is that there's now new WML tags for looping constructs - [repeat], [for], and [foreach]. FTR, the {FOREACH} macro is now implemented in terms of [for].
Yes, but writing a [for] cycle is still longer in WML tags than with macros. No matter how specifically designed for this purpose, it will add at least two lines, doubling its invocation's length. WML's problem with massive line counts has been one of the main reasons to use macros.
Not sure how those numbers work; the way I use them, a {FOREACH} macro would have two lines plus the body, while a [for] loop would most likely have five lines plus the body. It doesn't really matter, though; the {FOREACH} macro is deprecated, and it will almost certainly someday be removed, so if you really prefer using a macro for looping, I would suggest you find time to write your own version of the {FOREACH} macro. There's no hurry, mind you — {FOREACH} won't be going away anytime soon — but in my opinion it's probably better to stop using it sooner rather than later.
Author of The Black Cross of Aleron campaign and Default++ era.
Maintainer of Steelhive.

User avatar
Dugi
Posts: 4822
Joined: July 22nd, 2010, 10:29 am
Location: Carpathian Mountains
Contact:

Re: Wesnoth 1.13.7

Post by Dugi » March 24th, 2017, 6:43 am

Celtic_Minstrel wrote:
Dugi wrote:blablabla
Not sure how those numbers work; the way I use them, a {FOREACH} macro would have two lines plus the body, while a [for] loop would most likely have five lines plus the body. It doesn't really matter, though; the {FOREACH} macro is deprecated, and it will almost certainly someday be removed, so if you really prefer using a macro for looping, I would suggest you find time to write your own version of the {FOREACH} macro. There's no hurry, mind you — {FOREACH} won't be going away anytime soon — but in my opinion it's probably better to stop using it sooner rather than later.
I can create a macro for that, but what I fear is the phase just before the macro is removed - deprecated things tend to make big warnings visible to everyone. 1.12 still prints very annoying messages about deprecated ability formats that will not be supported any more in 1.12 (which is simply not true) instead of simply not supporting it and showing slightly weird formatting, becoming almost the only reasion why the usage of old 1.10 saves is annoying.

User avatar
Eagle_11
Posts: 733
Joined: November 20th, 2013, 12:20 pm

Re: Wesnoth 1.13.7

Post by Eagle_11 » March 24th, 2017, 10:48 am

New multiplayer maps and a campaign.
Yay!

DewyB
Posts: 19
Joined: February 23rd, 2017, 5:58 pm

Re: Wesnoth 1.13.7

Post by DewyB » March 24th, 2017, 1:08 pm

Just a quick follow up, rebooted, ran various malware scans, still cannot open 1.13.7 on my machine.

Caught the wife afk and it installed and ran without issue on her machine, she of course ran me off as soon as she returned. I really have no fraking clue.
Tell me again, where are we going, and why are we in a handbasket?

User avatar
Celtic_Minstrel
Developer
Posts: 1184
Joined: August 3rd, 2012, 11:26 pm
Contact:

Re: Wesnoth 1.13.7

Post by Celtic_Minstrel » March 24th, 2017, 5:08 pm

Dugi: I've considered adding a "addon developer mode" option in Advanced Preferences which will enable the showing of deprecated messages (and possibly other things) which currently are just dumped to chat for everyone. Would that help with your complaints?
Author of The Black Cross of Aleron campaign and Default++ era.
Maintainer of Steelhive.

User avatar
UnwiseOwl
Posts: 471
Joined: April 9th, 2010, 4:58 am

Re: Wesnoth 1.13.7

Post by UnwiseOwl » March 24th, 2017, 5:17 pm

Celtic_Minstrel wrote:Dugi: I've considered adding a "addon developer mode" option in Advanced Preferences which will enable the showing of deprecated messages (and possibly other things) which currently are just dumped to chat for everyone. Would that help with your complaints?
That would be a good thing.
Maintainer of the Imperial Era and the campaigns Dreams of Urduk, Epic of Vaniyera, Up from Slavery, Fall of Silvium, Alfhelm the Wise and Gali's Contract.
But perhaps 'maintainer' is too strong a word.

User avatar
The_Gnat
Posts: 1537
Joined: October 10th, 2016, 3:06 am
Contact:

Re: Wesnoth 1.13.7

Post by The_Gnat » March 24th, 2017, 9:18 pm

Great to see that this has finally been released :D

gfgtdf
Developer
Posts: 1026
Joined: February 10th, 2013, 2:25 pm

Re: Wesnoth 1.13.7

Post by gfgtdf » March 24th, 2017, 9:35 pm

Celtic_Minstrel wrote:Dugi: I've considered adding a "addon developer mode" option in Advanced Preferences which will enable the showing of deprecated messages (and possibly other things) which currently are just dumped to chat for everyone. Would that help with your complaints?
I'd also like to have some new mode, that is not exactly debug mode but rather some limited debug mode that can be used for both playing and debugging. That is, you have lua-console, debug consolde commands, deprecated wanrings etc, but no other things that spoil your game experience like 'all side visible in side overwiew', 'the messy right-click menu' or the game config reloads due to DEBUG defines. Maybe this could be combinated without your 'developer mode' idea.
Scenario with Robots SP scenario (1.11/1.12), allows you to build your units with components, PYR No preperation turn 1.12 mp-mod that allows you to select your units immideately after the game begins.

Tad_Carlucci
Developer
Posts: 289
Joined: April 24th, 2016, 4:18 pm

Re: Wesnoth 1.13.7

Post by Tad_Carlucci » March 24th, 2017, 11:54 pm

I'd suggest "Debug mode" simply enabling a "Debug preferences" dialog.
Then you can enable or disable the various options, as needed; or trigger certain events.
That way each developer can have a default setup which suits their general needs, and quick access to features they rarely use.
I forked real life and now I'm getting merge conflicts.

User avatar
Celtic_Minstrel
Developer
Posts: 1184
Joined: August 3rd, 2012, 11:26 pm
Contact:

Re: Wesnoth 1.13.7

Post by Celtic_Minstrel » March 25th, 2017, 3:01 am

gfgtdf wrote:I'd also like to have some new mode, that is not exactly debug mode but rather some limited debug mode that can be used for both playing and debugging. That is, you have lua-console, debug consolde commands, deprecated wanrings etc, but no other things that spoil your game experience like 'all side visible in side overwiew', 'the messy right-click menu' or the game config reloads due to DEBUG defines. Maybe this could be combinated without your 'developer mode' idea.
What I described would be independent of debug mode; you could have either or both enabled as you see fit. It could be used by addon devs, but also by the more dedicated beta testers for example.

I'm not sure what it would do besides increasing the verbosity of diagnostic messages though. (That is, including deprecation and other warnings along with the more-fatal errors.)
Author of The Black Cross of Aleron campaign and Default++ era.
Maintainer of Steelhive.

User avatar
beetlenaut
Developer
Posts: 2190
Joined: December 8th, 2007, 3:21 am
Location: Washington State
Contact:

Re: Wesnoth 1.13.7

Post by beetlenaut » March 25th, 2017, 4:33 am

This is UtBS:A_Subterranean_Struggle. After killing the last leader, you get this error. It sounds like next_scenario is not recognized. Is this just a bug, was it removed or renamed intentionally, or am I misunderstanding the message? (Since [endlevel] doesn't work, the scenario doesn't end.)
Attachments
utbs_lua_error.png
Campaigns: Dead Water
The Founding of Borstep
Secrets of the Ancients

User avatar
Celtic_Minstrel
Developer
Posts: 1184
Joined: August 3rd, 2012, 11:26 pm
Contact:

Re: Wesnoth 1.13.7

Post by Celtic_Minstrel » March 25th, 2017, 6:19 am

Um... that shouldn't happen in 1.13.7? As far as I know, that's a change made after 1.13.7 in this commit.

Also possibly relevant... what platform do you use?
Author of The Black Cross of Aleron campaign and Default++ era.
Maintainer of Steelhive.

Locked