After the Storm 0.10.18.1 [Wesnoth 1.14.x & 1.15.12+]
Moderator: Forum Moderators
Re: After the Storm 0.9.17 [Wesnoth 1.12]
It sounds like a case of mainline issue #3194, which was purportedly fixed in version 1.14.3. What version are you using?
Author of the unofficial UtBS sequels Invasion from the Unknown and After the Storm.
-
- Posts: 1187
- Joined: August 26th, 2018, 11:46 pm
- Location: A country place, far outside the Wire
Re: After the Storm 0.9.17 [Wesnoth 1.12]
I was using 1.14.0.
I have confirmed that the issue is resolved in 1.14.4.
thanks
I have confirmed that the issue is resolved in 1.14.4.
thanks
Speak softly, and carry Doombringer.
-
- Posts: 1187
- Joined: August 26th, 2018, 11:46 pm
- Location: A country place, far outside the Wire
Re: After the Storm 0.9.17 [Wesnoth 1.12]
E2S8
1.14.4, ubuntu 16.04.5
20180916 20:53:17 error engine: failed to auto-store $second_unit at (27,33)
20180916 20:53:17 error engine: failed to auto-store $second_unit at (27,33)
Invalid WML found: [unstore_unit]: variable 'second_unit' doesn't exist
Attack LoL with Elynia, click through some dialog.
1.14.4, ubuntu 16.04.5
20180916 20:53:17 error engine: failed to auto-store $second_unit at (27,33)
20180916 20:53:17 error engine: failed to auto-store $second_unit at (27,33)
Invalid WML found: [unstore_unit]: variable 'second_unit' doesn't exist
Attack LoL with Elynia, click through some dialog.
- Attachments
-
- AtS-2-And then there was Chaos-Auto-Save32.gz
- (81.62 KiB) Downloaded 401 times
Speak softly, and carry Doombringer.
Re: After the Storm 0.9.17 [Wesnoth 1.12]
E3 ending spoiler:
Last edited by Iris on September 17th, 2018, 11:18 am, edited 1 time in total.
Reason: Added spoiler tags
Reason: Added spoiler tags
Re: After the Storm 0.9.17 [Wesnoth 1.12]
@Kylix:
Spoiler:
-
- Posts: 1187
- Joined: August 26th, 2018, 11:46 pm
- Location: A country place, far outside the Wire
Re: After the Storm 0.9.17 [Wesnoth 1.12]
Return_to_Raelthyn
After defeating the drones, the scenario objectives are updated, but one of the defeat conditions is still based on the drones.
After defeating the drones, the scenario objectives are updated, but one of the defeat conditions is still based on the drones.
Speak softly, and carry Doombringer.
-
- Posts: 1187
- Joined: August 26th, 2018, 11:46 pm
- Location: A country place, far outside the Wire
Traits that might not make sense
I've never seen this before, though I just might not have noticed. But I recently upgraded from 1.14.0 to 1.14.4, and I've seen this twice since, and it seems kind of odd so I figured I'd point it out.
In the attached file, there's an imp (both times I've seen this it's been an imp, FWIW) at 37.31. His traits are weak and strong. Seems odd.
I'm sure the idea that some traits should or should not be mutually exclusive has been discussed, though I couldn't find that, and some decision made. If the decision was that things like weak and strong shouldn't coexist, something's broke.
In the attached file, there's an imp (both times I've seen this it's been an imp, FWIW) at 37.31. His traits are weak and strong. Seems odd.
I'm sure the idea that some traits should or should not be mutually exclusive has been discussed, though I couldn't find that, and some decision made. If the decision was that things like weak and strong shouldn't coexist, something's broke.
- Attachments
-
- AtS-2-A Final Confrontation Turn 10.gz
- (86.83 KiB) Downloaded 367 times
Speak softly, and carry Doombringer.
-
- Posts: 217
- Joined: December 17th, 2015, 10:27 pm
Re: Traits that might not make sense
This should be moved to Scenario & Campaign Development because, even if such a facility existed for traits like it does for AMLAs — so far as I know, it doesn't, per UnitsWML#.5Btrait.5D, — the problem here would need to be attended in the After The Storm campaign first.
One of my eras has its own system of assigning traits which bypasses the hardcoded one. It addresses this concern — though is a tad slower, as a result.
When this topic is moved, then I'll talk more about methods to work around this. (I don't mean for that to seem “anal retentive” or bureaucratic, but it is, somewhat.)
One of my eras has its own system of assigning traits which bypasses the hardcoded one. It addresses this concern — though is a tad slower, as a result.
When this topic is moved, then I'll talk more about methods to work around this. (I don't mean for that to seem “anal retentive” or bureaucratic, but it is, somewhat.)
-
- Posts: 1187
- Joined: August 26th, 2018, 11:46 pm
- Location: A country place, far outside the Wire
Re: Traits that might not make sense
Thanks. It sounds like the answer is that everything is working according to design. While I think it's a little odd, I only pointed it out in case it was actually a problem.
Speak softly, and carry Doombringer.
-
- Posts: 1187
- Joined: August 26th, 2018, 11:46 pm
- Location: A country place, far outside the Wire
Re: After the Storm 0.9.17 [Wesnoth 1.12]
E3S3
20180918 21:39:16 error engine: failed to auto-store $second_unit at (13,21)
20180918 21:39:16 error engine: failed to auto-store $second_unit at (13,21)
Invalid WML found: [unstore_unit]: variable 'second_unit' doesn't exist
Attack Nar-hamoth with three units, click through a little dialog
20180918 21:39:16 error engine: failed to auto-store $second_unit at (13,21)
20180918 21:39:16 error engine: failed to auto-store $second_unit at (13,21)
Invalid WML found: [unstore_unit]: variable 'second_unit' doesn't exist
Attack Nar-hamoth with three units, click through a little dialog
- Attachments
-
- AtS-3-Amidst the Ruins of Glamdrol-Auto-Save12.gz
- (81.09 KiB) Downloaded 377 times
Last edited by white_haired_uncle on September 19th, 2018, 6:42 am, edited 1 time in total.
Speak softly, and carry Doombringer.
-
- Posts: 1187
- Joined: August 26th, 2018, 11:46 pm
- Location: A country place, far outside the Wire
Re: After the Storm 0.9.17 [Wesnoth 1.12]
E3S4.1
20180919 00:12:17 warning wml: failed to match [secondary_unit] in [kill] with a single on-board unit.
I saw this every time I used a barrel. Didn't seem to affect anything, but here it is.
Save has a couple barrels ready to deploy.
20180919 00:12:17 warning wml: failed to match [secondary_unit] in [kill] with a single on-board unit.
I saw this every time I used a barrel. Didn't seem to affect anything, but here it is.
Save has a couple barrels ready to deploy.
Spoiler:
- Attachments
-
- AtS-3-Outpost of Hell-Auto-Save22.gz
- (137.33 KiB) Downloaded 387 times
Speak softly, and carry Doombringer.
-
- Posts: 217
- Joined: December 17th, 2015, 10:27 pm
Re: Traits that might not make sense
So, I know of a few ways to work around this.white_haired_uncle wrote: ↑September 18th, 2018, 4:04 am (…)
In the attached file, there's an imp (both times I've seen this it's been an imp, FWIW) at 37.31. His traits are weak and strong. Seems odd.
I'm sure the idea that some traits should or should not be mutually exclusive has been discussed, though I couldn't find that, and some decision made. If the decision was that things like weak and strong shouldn't coexist, something's broke.
- The obvious scheme, used by TBFW — also known as “mainline” era, — is to simply not make such opposite traits available: goblies have Dim, Weak; others have Intelligent and Strong.
- Use a multitude of
[variation]
definitions for each desired combination of opposite[trait]
attributes via therace=
value. I.e. if you have two opposite traits, you need two[variation]
s to support it; if you have two pairs of two such traits, you will need a total of four[variation]
s. Each such[variation]
uses its ownrace=
, which requires you to define copies of the conceptual[race]
that otherwise would use a differentid=
but could share name and description — although my recommendation would be to distinguish the name e.g.name=_"Faddlie, weak"
.
Because only one[variation]
can be used at a time — plus either[female]
xor[male]
, this deprives you of the ability to use[variation]
for anything else independently from its application as a way to vary the[trait]
pool. - Using
[modify_unit]
in a[event] name=prerecruit
. You can also doname=recruit
if necessary. This bypasses the usual quantification of[trait]
s, and so your event proc will need to use conditional flow-control.
This is my favorite scheme because it allows you to do so much more also.
-
- Posts: 1187
- Joined: August 26th, 2018, 11:46 pm
- Location: A country place, far outside the Wire
Re: After the Storm 0.9.17 [Wesnoth 1.12]
And now I'm stuck.
In the attached, click through a ton of dialog to get to the next scenario, which ends in defeat before you can do anything.
In the attached, click through a ton of dialog to get to the next scenario, which ends in defeat before you can do anything.
Code: Select all
20180921 21:24:18 error scripting/lua: ~add-ons/Naia/lua/common.lua:499: bad argument #3 to '__newindex' (number expected, got nil)
stack traceback:
[C]: in metamethod '__newindex'
~add-ons/Naia/lua/common.lua:499: in local 'cmd'
lua/wml-utils.lua:145: in field 'handle_event_commands'
lua/wml-flow.lua:20: in local 'cmd'
lua/wml-utils.lua:145: in field 'handle_event_commands'
lua/wml-flow.lua:200: in local 'cmd'
lua/wml-utils.lua:145: in field 'handle_event_commands'
lua/wml-flow.lua:6: in function <lua/wml-flow.lua:5>
- Attachments
-
- AtS-3-Breakdown.gz
- (28.46 KiB) Downloaded 365 times
Speak softly, and carry Doombringer.
Re: After the Storm 0.9.17 [Wesnoth 1.12]
@shadowm: I intend to get serious with testing the new version on BfW 1.14 in about a week or so. Do you want the notes I've made while playing on BfW 1.12 or do you just want me to post whatever comes up on AtS after I've started playing the new version?
Re: After the Storm 0.9.17 [Wesnoth 1.12]
I've had some time to play AtS the last few days and managed to knock out almost all of episode one, so here's all the stuff I found that's not on the Issue tracker:
Massive spoilers for ALL of AtS ahead!
Massive spoilers for ALL of AtS ahead!
Spoiler:
slightly confused