bugBattle for Wesnoth - Bugs: bug #8264, Modularizing [hides] slightly

Show feedback again

bug #8264: Modularizing [hides] slightly

Submitted by:  Lari Nieminen <zookeeper>
Submitted on:  Sat Jan 13 21:42:57 2007  
Votes:  5  
Category: Feature RequestSeverity: 1 - Wish
Priority: 5 - NormalItem Group: WML
Status: NonePrivacy: Public
Assigned to: Celtic Minstrel <celticminstrel>Open/Closed: Open
Release: 1.3+Operating System: all

Add a New Comment (Rich MarkupRich Markup):

You are not logged in

Please log in, so followups can be emailed to you.


Sat Aug 6 23:19:43 2016, comment #2:

assigming to celmin as requested

Daniel <gfgtdf>
Project Member
Thu Jan 18 18:01:47 2007, comment #1:

I think i'll do 2) for hides, slows, poison, ...
(with default value = current alert)
It looks easy to implement.

BenoƮt Timbert <noyga>
Project Member
Sat Jan 13 21:42:57 2007, original submission:

I'd like a few enhancements to how [hides] can be used.

1. Currently, the unit is revealed only when an enemy steps next to it: I'd like a range=x key be added that would specify the range (in hexes) at which the unit could be detected. So, a unit with a [hides] ability with range=3 would be detected if an enemy moved within 3 hexes of it.

2. The text to be displayed when the "ambush" is triggered should be customizable. Currently it's always "Ambushed!". A new key to specify the text to be used when the unit is revealed should be added to allow this to be customized as well.

So, the current ambush ability (in the [hides] tag) would, after these changes, simply receive these additional keys:

alert= _ "Ambushed!"

range= could default to 1 or 0. A value of 0 would mean that the unit would only be revealed when an attempt is made to move onto the hex where it is hidden. If this is hard to implement, it can be discarded (and thus make range=0 be illegal), but it'd be nice to have. Do note that currently the unit is revealed only when an enemy moves next to it (into its ZoC), whereas with a range of >1 the discovering unit should stop immediately when stepping into range (just like when sighting a unit) even when it's not stepping into anyone's ZoC. This might be obvious to whoever implements this, but I'd thought I'd mention it just in case.

alert= should default to an empty string. Could default to "Ambushed!" too, it doesn't really matter IMO.

Lari Nieminen <zookeeper>
Project Member


(Note: upload size limit is set to 1024 kB, after insertion of the required escape characters.)

Attach File(s):

No files currently attached


Depends on the following items: None found

Items that depend on this one: None found


Carbon-Copy List
  • -unavailable- added by gfgtdf (Posted a comment)
  • -unavailable- added by epaul (Voted in favor of this item)
  • -unavailable- added by noyga (Posted a comment)
  • -unavailable- added by zookeeper (Submitted the item)

    Do you think this task is very important?
    If so, you can click here to add your encouragement to it.
    This task has 5 encouragements so far.

    Only logged-in users can vote.


    Error: not logged in



    Follow 2 latest changes.

    Date Changed By Updated Field Previous Value => Replaced By
    Sat Aug 6 23:19:43 2016gfgtdfAssigned toNone=>celticminstrel
    Sun Oct 14 19:42:37 2007epaulCarbon-Copy-=>Added epaul
    Show feedback again

    Back to the top

    Powered by Savane 3.1-cleanup