The Battle for Wesnoth Forums

What you sent me today is much closer to a standard Wesnoth campaign. You don't really need all the empty folders though. I would put the Lua code in utils. I found some time last night and fixed all the code from before. I used it as a challenge for myself and a way to practice Lua coding. Use it i...

I would like to say things in a nicer way, but I assume you will translate my message, and I don't want the meaning to be lost. map size can be changed I actually did it myself, but unfortunately, it caused major issues like unreachable exits or misaligned positions. It was immediately obvious to me...

I can’t change the map dimensions without breaking the generation algorithm. I can't imagine this. I can't imagine code that is so bad that you can't change it that way. The size should be a variable that you can change everywhere by modifying one line of code. This is very important for testing. T...

Then you could have the information just from looking at the army, or the unit you recruited. That's a really useful idea. It seems like it should have been obvious now that someone has thought of it! I don't think the number of variations is that important, so cutting it down to six in some cases ...

How? And where? Answering this question fully means explaining the structure of a Wesnoth add-on. Nobody is likely to do that since you can just follow the "Create" link at the top of the page to find a thorough description. Maybe if you had some more information, you could ask a more tar...

Well, that was interesting. I didn't think there was any reason to have a turn limit on the final scenario, but I guess you proved me wrong!

Refumee wrote: ↑February 27th, 2025, 9:08 pm Why not using it for SotA as unique saurian sprite for Vendraxis?

It's not up to me either, but I assume my vote counts for something. I would prefer using it as intended, and giving Vendraxis a level-3 advancement.

The difference is not subtle it if works, so there is a bug in the Pixel Scale Multiplier (I assume only on the Macintosh). That's the problem that needs to be solved. You should put in a bug report. I would do it myself, but I don't have access to a machine with the same problem. I won't know if a ...

The pixel scale multiplier does exactly what you are asking for. A pixel scale of 2x makes each interface pixel take up a four-pixel box on the screen, making it much larger, but the map can still be scaled separately so that it looks the same as before. The text can be up to 16 times its default si...

You are trying to do too much at once I think. We don't know which part is not working, so we need to guess. I think the event code gnombat provided should work fine as long as it is in the right place, but verify that by using a different image path function in it (GS for example) to make sure that...

You could use that [object] code in an event (I would use a unit_placed event), and the [event] can go in [unit_type].

I found some old images. This is what Wesnoth looked like when I started playing. Those were the large sized portraits, by the way.

It has come a long way. This isn't even showing the full story because maps are animated now, too.

You are playing the version under development, not the stable version, so you should expect some bugs. This does seem to be a bug that nobody else has noticed. Can you report it on the bug tracker site? If you are interested in more technical information, the merfolk side is controlled by a microAI....

Celtic_Minstrel wrote: ↑October 28th, 2024, 1:50 pmIf the generator were rewound, you would get the exact same unit when you redo anyway.

Not if you recruited your units in a different order to make sure that didn't happen. This would allow you to fish around for specific traits on at least some of your units.

I suspect that your roles are not correct, and the code did not fail for the reason you think. The [role] tag is meant to provide a speaking role to one unit, and it is not guaranteed to be set at all. You should use a custom [status] instead. Maybe I am wrong, and you are using : inspect to verify ...