Swamplings for 1.14
Moderator: Forum Moderators
Re: Swamplings for 1.12
They come from here. I have not drawn them and they were not drawn to be a part of Swamplings. I've been suggested to use them, that's all. I might darken some parts of the portrait if you find it really necessary.
Re: Swamplings for 1.12
Great campain, excellent fun, thank You for job well done
Fun campaign!
Dear Swamplings team -- I greatly, greatly enjoyed the campaign! I cared more about minor characters in this campaign than I usually do about the primaries. Engrossing, fun story. Good balance on difficulty; loved the creative levels. Thanks!
-
- Posts: 189
- Joined: February 16th, 2015, 5:02 pm
Re: Swamplings for 1.12
Hi, I am not able to finish this scenario- when I tamed next bat, and made a next move, scene with poisoning and paralyzing Mage appears, and then all my units are hidden in chest, and I have no units to find cure for him.
I am adding savegame.
I am adding savegame.
- Attachments
-
- S-Healer_And_Slayer-Automatické_uložení26.gz
- (42.74 KiB) Downloaded 746 times
Re: Swamplings for 1.12
No bugs to report, just my thanks to the creator and the mantainer of the campaign. I had so much fun playing it
Free as a bird
Re: Swamplings for 1.12
Well, i have to say, I'm not even thirdway in and i can already tell why this was so highly rated.
Re: Swamplings for 1.12
Hey,
Not sure if this is where I should post this but, on 1.14, right at the beginning of the first scenario there is a bug
If this is the wrong place to post it could someone point me in the right direction?
Not sure if this is where I should post this but, on 1.14, right at the beginning of the first scenario there is a bug
Code: Select all
error scripting/lua: lua/wml/animate_unit.lua:15: bad argument #1 to 'get_unit' (expected string or location)
stack traceback:
[C]: in field 'get_unit'
lua/wml/animate_unit.lua:15: in upvalue 'add_animation'
lua/wml/animate_unit.lua:105: in upvalue 'add_animation'
lua/wml/animate_unit.lua:111: 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>
Completed official campaigns: ToTB, AOI, TSG, HttT, Liberty, HoT
Completed unofficial campaigns: The Amaranthine stone, Bad moon rising part 1, Ooze mini campaign
Completed unofficial campaigns: The Amaranthine stone, Bad moon rising part 1, Ooze mini campaign
Re: Swamplings for 1.12
Why would you upload a campaign & not check to see if it will actually work on the new version of Wesnoth?
Re: Swamplings for 1.14
As ekeron says, there's a WML error at the start of the first scenario. That scenario seems broken but can be completed (the enemy leader doesn't move to his castle, the player's leader has to spend several turns moving to his own castle). The second scenario has an interesting bit about bats, but then completely breaks with a WML error (the scenario objectives don't update, and the poisoning event doesn't happen).
So the campaign seems to be broken, with no response to the feedback thread.
Edit: the first scenario is more broken than I thought. There are three keeps on the map, and the scripted movement that's broken by the WML error in the intro would move you to the south-east corner. If you simply use the central castle (only 1 recruitment hex, but 3 turns closer to your starting point and 3 turns closer to your enemy) then you miss the scripted events giving you wolves and your first loyal supporter.
So the campaign seems to be broken, with no response to the feedback thread.
Edit: the first scenario is more broken than I thought. There are three keeps on the map, and the scripted movement that's broken by the WML error in the intro would move you to the south-east corner. If you simply use the central castle (only 1 recruitment hex, but 3 turns closer to your starting point and 3 turns closer to your enemy) then you miss the scripted events giving you wolves and your first loyal supporter.
Re: Swamplings for 1.12
I have fixed it.
I am currently busy. I have noticed that 1.14 came out when I started being bombarded by requests to upload specific add-ons. So I checked for the problems with 1.14 I know of and uploaded them all. I didn't know that a strange refactoring of [animate_unit] caused some previously working code (even without deprecation messages) to suddenly start producing lua crashes without any meaningful error reports.Byron wrote:Why would you upload a campaign & not check to see if it will actually work on the new version of Wesnoth?
Re: Swamplings for 1.12
Sorry, but the new upload has WML errors in scenario 1's events for finding Eeep and Misris.
Re: Swamplings for 1.12
Hi,
I think something's still broken (I play steam version of wesnoth). I finished first scenario successfully, but in second scenario after charming of the bats I get the green bottle, and after message "i wonder if it's it" there is lua bug (bad argument 1 to get_unit, expected string or location) and I can't continue with the quest/mission.
I think something's still broken (I play steam version of wesnoth). I finished first scenario successfully, but in second scenario after charming of the bats I get the green bottle, and after message "i wonder if it's it" there is lua bug (bad argument 1 to get_unit, expected string or location) and I can't continue with the quest/mission.
Re: Swamplings for 1.12
First of all, many thanks to make campaigns for us
Same error here, in the first and second scenarios. I think a more deeper test should be done in your campaign to fix everything.
Same error here, in the first and second scenarios. I think a more deeper test should be done in your campaign to fix everything.
Re: Swamplings for 1.12
Can you please be more specific? What do you mean with errors for finding someone? Can you please write the whole lua error? Bad argument 1 to get_unit means that author of the lua implementation of the WML tag forgot to write a proper error message.
A deeper test would take many hours and I do not have time for that at the moment. Problems of this kind shouldn't appear. Add-ons I wrote didn't suffer from these problems when I moved them to 1.14. I think the original author left a lot of errors in the code and these errors didn't were not visible until 1.14.
A deeper test would take many hours and I do not have time for that at the moment. Problems of this kind shouldn't appear. Add-ons I wrote didn't suffer from these problems when I moved them to 1.14. I think the original author left a lot of errors in the code and these errors didn't were not visible until 1.14.