The Battle for Wesnoth Forums

I'm working on this again, all the things mentioned will be changed in the next version.

About the hotkeys I'm not sure: What would be good hotkeys?

Yes.

This add-on would profit a lot from switching to [modify_unit_type]. The [modification] will be compatible with more add-ons.

I think you can use for define=… in both [campaign] tags the same value. A few nitpicks: - Use [units] instead of [ + units]. The latter is an old workaround. - Binary files, that are images, sounds, music, are found by [binary_path] . No need for {~add-ons/A_Hidden_War/music} . - {~add-ons/A_Hidden...

That code is for 1.12, where the size was 205x205. It was a useful piece of code back then. If you use it nowadays, the picture will be upscaled again (after having being downscaled to 205x205). As for today: Picture in the help tries to be 400px for width or height . It scales the picture according...

Edit: I think I somehow got confused about the purpose of this thread, sorry. I don't think so. The purpose of this thread is to be a porting guide, not only about breaking changes (=minimum to change guide). At least that is was I had in mind when I wrote it. Updated the post about the new macros ...

# This file was generated using the scenario editor. # # If you edit this file by hand, then you shouldn't use the # scenario editor on it afterwards. The editor completely # rewrites the file when it saves it, which will lose any WML # that the editor doesn't support. There's a way around it, but ...

[…] I've had this thought for a while in mind … I think what is missing is a new landing page in the wiki for people who are new here, which tells where to start. Maybe you guys want to write one? You're new enough to know what is missing. What I feel what is missing: - telling people how to use th...

On the first sight's it's an easy way to write one event instead of two.

But the special part is that it will fire only once – so it offers a way for dialogues, which should fire in one of the two cases, but not twice.

It actually is easy. For an enter hex event x2,y2 would be the adjacent hex which can be full. For a moveto event it can be farther away, but it's empty. [event] name=moveto first_time_only=no [filter] x,y=1,5 [/filter] {TELEPORT_TILE 1 5 $x2 $y2} [/event] Uses the macro from here

Looked into it too, but all solutions have some quirks …
Made a symbol image which you could use though.

Another option is to block the terrain by putting a petrified unit onto the hex, or teleporting units which step onto it.

For realizing it: 1. Events on turns 5, 10, 15 and 20 2. There's a mod for it, https://r.wesnoth.org/t51067 3. Balancing … 4. Balancing + some event which gives extra MP. 5. AMLAs are fun and easy 6. Fuel mechanics … duh. Needs to write a Candidate Action or MicroAI in Lua, otherwise the AI will ju...

The problem is that you wrote ability in singular, but the tag is called abilities nevertheless. Let me throw in a variant with [heal_unit] instead of storing & unstoring: #define PL_ABILITY_ENDLESS_MP # wmlxgettext: [abilities] [dummy] id=PL_endless_mp name= _ "…" description= _ "...

Hi There's not much needed to be done differently. First of all, the code above does not change the movement of an ai leader, but of all of side 2's units. Though, as it happens before side 2 recruited, the movement restricting object will only be given to the leader. You could fire the code at a la...

That's on the bug tracker as bug #4978.