Carda's bunch of daily Lua questions

[Carda]

Hello there Wesnoth Community,

Downloaded the game last week and observed a lot of games. RPG maps are what makes this game very interesting to play for me and so found out about Bob's RPG addons what makes the game even cooler now.

Used to making scripts for Warcraft 3 in the long past and the scripting blood starts to boil again. My goal is to create a RPG multiplayer map like Labyrinth of Champions.

To test my map's progression I need to create an event that gives the player who enters a specific coordinate an # amount of xp.

[event]
name=moveto
[filter]
x="6"
y="74"
side=1,2,3,4,5
[/filter]
?????????????
[/event]

What command do I use to give the player who activated the script some xp?
Is there a clear guide on the internet where I can find the basic commands like this one?

Thank you all for your kind help,
Carda

[Sapient]

http://wiki.wesnoth.org/ReferenceWML

Read documentation for the following tags:

[store_unit]

[set_variable]

[unstore_unit]

Ask questions if you have any.

Yes, this can also be done with Lua, but I'm not the one to ask for that.

[Atz]

If you just need to add XP for testing purposes (ie. it's not going to be in the finished version) you can also manually add experience and do various other things using debug mode. Start playing your scenario and type ":debug" to activate it. Then you can mouse over the unit you want and type ":unit experience=10" to set a unit's XP to 10, for instance. You can also make a unit level up with "unit advances=1". See http://wiki.wesnoth.org/CommandMode for more.

[Ceres]

An easier way to do this would be

Code: Select all

[modify_unit]
			[filter]
				id=$unit.id
			[/filter]
			experience=100
		[/modify_unit]

'unit' is a container stored automatically after each event, storing all values of the triggering unit. The macro didn't work for me, but this did.

[Astoria]

An easier way to do this would be

Code: Select all

[modify_unit]
			[filter]
				id=$unit.id
			[/filter]
			experience=100
		[/modify_unit]

'unit' is a container stored automatically after each event, storing all values of the triggering unit. The macro didn't work for me, but this did.

This should work if you have 1.9.x. Else use:

Code: Select all

{MODIFY_UNIT x,y=$x1,$y1 experience 100}

[bigkahuna]

This should work if you have 1.9.x. Else use:

Neither of those work.
That alters the modified unit to 100 xp, meaning no matter what the xp was before, it would have 100. This is how to add it.

Code: Select all

[store_unit]
    [filter]
        x,y=$x1,$y1
    [/filter]
    kill=no
    variable=unit_stored
[/store_unit]
{VARIABLE_OP unit_stored.experience add 100}
[unstore_unit]
    variable=unit_stored
[/unstore_unit]

[Ceres]

Corrected version of my code adding the experience instead of setting:

Code: Select all

		[modify_unit]
			[filter]
				id=$unit.id
			[/filter]
			experience="$($unit.experience+100)"
		[/modify_unit]

[Sapient]

Corrected version of my code adding the experience instead of setting:

Well done! You even remembered the quote marks.
This made my day to see a new WML wiz is joining the ranks.

[bigkahuna]

Well done! You even remembered the quote marks.
This made my day to see a new WML wiz is joining the ranks.

QFT

[Carda]

Thank you all for the detailed responses.

I tried reading the Lua manual about store_unit and such but if I don't have a working example before my nose that manual is still a bit too complicated for me. So I just started copying/paste a few examples you people gave here and I found a working example in bigkahuna's version. If works combined with a event like 'a unit moves to a specific coordinate' *big cheer*.

Going to study this further because I have a feeling I can use this script for changing the value of Max HP and more which is badly needed at the moment on my map.

Great job all ,
Carda

Statements usable with store_unit found in Wesnoth Manual and added later to the post

* advances_to
* alignment
* alpha
* attacks_left
* canrecruit
* cost
* experience
* facing
* flying
* gender
* goto_x
* goto_y
* hitpoints
* id
* language_name (same as the name key in the unit config)
* max_experience
* max_hitpoints
* max_moves
* moves
* overlays
* resting
* side
* type
* unit_description
* unrenamable
* upkeep
* x
* y
* zoc
* [movement_costs]
* [defense]
* [resistance]
* [variables]
* [status]
* [attack]
* [modifications_description]
* [modifications]

[Reepurr]

Going to study this further because I have a feeling I can use this script for changing the value of Max HP and more which is badly needed at the moment on my map.

Probably.

Code: Select all

[store_unit]
    [filter]
        x,y=$x1,$y1
    [/filter]
    kill=no
    variable=unit_stored
[/store_unit]
{VARIABLE_OP unit_stored.max_hitpoints add 100} 
# Can also be max_moves if you want, etc. - though if you want to
# give a unit more attacks you'll probably have to do a silent [object]
[unstore_unit]
    variable=unit_stored
[/unstore_unit]

[Carda]

Yeah it's starting to work out. Thanks. Already mastered how to give HP, add MAX HP, Restore HP to full and XP giving.

Next problem:

{VARIABLE_OP unit_stored.moves value unit_stored.max_moves}

Why doesn't this work? It sets the moves to 0 instead of his maximum moves (5).

And by the way... with VARIABLE_OP I use ADD for + , but what word replaces - ? And is = really replaced by the word value?

Thanks for making everything clear again,
Carda

[Ceres]

If you want to set something to the value of a variable, you have to use a $ sign.
[set_variable]
name=myvariable
value=$anothervariable
[/set_variable]
would work.

{VARIABLE_OP unit_stored.moves value unit_stored.max_moves}

should be changed to {VARIABLE_OP unit_stored.moves value $unit_stored.max_moves}

And - is set with 'sub'. * is done with 'multiply' and / with 'divide'.

[Carda]

*CHEERS* A quick reply again. Was breaking my brain why it didn't work. Going to study your post and the difference with the $

Also thanks for SUB. I tried 'subtract' but that didn't work either (heheh)

Going to fix the problem in my map at once and thanks,
Carda

[bigkahuna]

{VARIABLE_OP unit_stored.moves value $unit_stored.max_moves}

Actually this would be much better (and simpler!):

Code: Select all

{VARIABLE unit_stored.moves $unit_stored.max_moves}

Which makes variable "$unit_stored.moves" equal to "$unit_stored.max_moves".