The Battle for Wesnoth Forums

Use the {REMOVE_LABEL X Y} macro

Moved to Off-Topic (as you said, this is not a forum game, so that's where this belongs.) Since Adobe Flash was shut down for good, most of the stuff I remember is also gone with it, my favorite was 1066. I think the Humbug game and it's sequels are still available though, that's a very funny silly...

How about an ability with a [resistance] tag that's reducing every resistance value for melee/ranged weapons? You need Wesnoth >= 1.15 to be able to filter a weapon in a resistance tag though. If you're on 1.14, the bit more cumbersome workaround would be to make it a weapon special instead with a [...

For the last one, were you playing on 1.15? I did basically all of my play testing on 1.14 and I made sure the dwarves were on the same side there, but I could definitely see the team name changing in a way I didn't expect between versions. Sorry, forgot to specify the version. I'm afraid this was ...

This was so funny :D Great work. A few technical things I noticed: - I'd recommend disabling recalling for the second scenario. It spares the player unavoidably losing the recalled units, and also makes sense storywise - it's a dream, you shouldn't be able to recall your units. - The dark wizard doe...

Well, I was quoting the note at this section , and I remember it not working for me at filtering time. That was a long time ago, it may have been changed since :) I think I recall a similar issue where hitpoints weren't tracked "live" during these events, and if it got below zero, the atta...

The second_unit variable is not stored at the time of event filters, so you can't use it in [filter_condition]. Automatically stored variables such as this are stored at the time they are first accessed inside the event (so not yet at filtering-time). To get an "attack hits" event, you nee...

Don't use an explicit [filter] tag inside [set_extra_recruit]. It takes the standard unit filter keys directly as arguments. https://wiki.wesnoth.org/DirectActionsW ... recruit.5D

To be honest, I find it strange that this even starts with the game. :) Opening and closing tags don't match: you close [specials], leaving it currently in an [attack], putting an event there (which won't work in an [attack] tag), and then you open a [+abilities] tag, that's getting closed by [/spec...

You can use radius with [filter_location] : [filter] side = 1 [filter_location] x,y=9,29 radius=1 [/filter_location] [/filter] [message] takes no explicit [filter] tag, you can put the filter keys directly into it instead: [message] type = Peasant message= _ "..." [/message] Keep in mind, ...

[animation] is not action WML, you're probably looking for [animate_unit].

Neat looking fire guardian! I really like the overall approach and the smoke, great job. :D If you're looking for some feedback on improvements: I think the flames look a bit strange at places, especially the contour on the right-side arm (left arm in his perspective). I don't know I'm not an artist...

Moved to WML Workshop. This code looks good to me, unless I too am missing something, it should work like this. [remove_object] indeed takes no [filter] tag, so this event should remove the objectone object from every unit that has the oneability at the time when the event fires. If it doesn't work...

Until someone can clarify what's going on with the changes between versions, you could try a cheap workaround: Add a condition to your post advance event: [filter_condition] [variable] name=temp_disable_event not_equals=yes [/variable] [/filter_condition] Then before you'd unstore the unit just crea...

As far as I remember it was used to set some properties like "always on the right" in case of a few select units, and things like that. These seem to be done by IPF now, probably that's why the tag got deprecated somewhere.