EasyCoding
Contents
- 1 Foreword
- 2 MP related features
- 3 WML related features
- 4 Improvements to AI
- 4.1 AI Batch testing
- 4.2 Add more ai actions
- 4.3 write a (fai or c++ or lua) candidate action for leader control
- 4.4 write a (fai or c++ or lua) candidate action for using leadership/illuminate
- 4.5 write a (fai or c++ or lua) candidate action for healer control
- 4.6 berserker improvement
- 4.7 power projection improvement
- 5 GUI related features
- 6 GUI2 related features
- 7 Miscellaneous
- 8 Bugs
- 9 See Also
Foreword
This page is here to document easy to do coding tasks. It is not here to double the feature request database, and should only be filled by people that know the code well enough to judge the difficulty of a given task.
If you are such a person, you should feel free to edit this page.
If you're not, you should post a feature request and discuss your idea on the forum or IRC. A coder with better knowledge of the code might give you the green light to add your feature here.
Anybody should feel free to add "clues" to any tasks, that is entry points, traps to avoid, person to contact to discuss and so on.
If you plan to work on a feature, write your name at the bottom of the feature, with the date. Note that if you are too long at working on a feature I'll "free" it back (that is if you're not working on it. If you have problems implementing it, just tell us....)
--Boucman 20:48, 3 October 2006 (CEST)
Since bugs are sometimes a good opportunity to get a first idea of the code, i will add some here that are easy to fix as soon as i stumble upon them (the one i had in mind is fixed already ;-).
--Yogi Bear, 28 February 2008
Use different font for in-game chat
Since commas and dots are apparently hard to tell apart. As per FR #7470 [1]
WML configurable village income / upkeep
Preferably as a [scenario], [side] or [campaign] keys. As per FR #6301 [2]. Patch submitted: [3] (gabba)
--Boucman 08:56, 28 February 2010 (UTC) : this is postponed for 1.8, can be considered reserved
Add support of [if] for [scenario]
As per FR #4539 [4]
Make [have_unit] optionaly use full SUF
[have_unit] by default uses SUF but does not apply it to recall list. Introduce an optional key that will allow to lift that limitation.
Side-specific results
Giving result=defeat or result=victory for specific sides. (FR #4960) -- dlr365 -- patch submitted [5]
--Boucman 08:58, 28 February 2010 (UTC) Patch seems abandonned, but can be used for further work feel free to take over the FR
Support for leaderless multiplayergames
Add support for the WML key victory_when_enemies_defeated= in the scenario tag during multiplayergames. (FR #8106) --endercoaster 30, March 2010. I'm gonna give this one a try.
Support for standalone multiplayer scenarios
There used to be support for standalone scenarios in the userdata tree, in reorganising the trees this feature got lost and an add-on is now required to add a scenario. Re-add this feature. It is probably a good idea to mirror the mainline multiplayer tree.
Other Ideas
See FutureWML; some ideas there are easier than others.
Improvements to AI
Fix some todos, add new formula functions, or do minor improvements to the formula language. Make it easier to debug the formula language, add more ai components.
Please discuss these with Crab, Dragonking, Sirp or Boucman
AI Batch testing
Finish patch #1169 [6]
Add more ai actions
Add an ai action (and add formula_ai function to do that) to set a goto on a unit
Add an ai action (and add formula_ai function to do that) to send a chat message to a player
Add an ai action to set formula ai variable (convert existing code from formula_ai)
Add an ai action to set formula ai unit variable (convert existing code from formula_ai)
Add an ai action (and add formula_ai function to do that) to fire a WML event
write a (fai or c++ or lua) candidate action for leader control
write a (fai or c++ or lua) candidate action for using leadership/illuminate
special handling of units with leadership to have them support units. Only do it if it actually is useful (less hits needed to kill the unit) and ability to help multiple units in a single turn (assuming enough MP)
write a (fai or c++ or lua) candidate action for healer control
Handle units with healing power, moving them at places where they can provide the most healing
berserker improvement
The default AI's strategy of attacking as much as possible is very bad with berserker... A simple AI that would prevent the berserker from attacking (and keeping him close to fight without being exposed) and attack when the chance to kill is high enough would be an interesting addition
power projection improvement
AI sometimes wants to calculate 'how much firepower can enemy bring on location X'. in doing so, it considers enemy possible moves, time of day, attacks, enemy defense, etc. There is specific problem with 'time_of_day' used in that calculation -sometimes, it's really needed to check 'time of day for NEXT turn', not time of day for THIS turn.(since the time of day might change next turn).
power_projection must be fixed to account for the possibility of time_of_day being different.
Note that some enemies might go after us (so, still on THIS turn), and some - before us (so, their next turn will be on NEXT turn).
Note at the moment Mordante is working on a new GUI system, these changes will probably affect the way these items need to be implemented. Contact Mordante on IRC before starting to work on these.
--SkeletonCrew 14:04, 9 March 2008 (EDT)
Theme Changes
- allow custom themes to display values of WML variables (FR #6209)
- hide the hourglass item from the statusbar when there is no timer
Widget Changes
- show side number, name and team association information in the status table
- make games sortable in the lobby (open slots, total number of players, era, XP modifier, gold per village, fog/shroud)
- input history (chat, commands, ..) - note: rujasu is working on this feature
GUI2 is the new gui engine Mordante/SkeletonCrew is working on.
- Information on the wiki can be found here http://www.wesnoth.org/wiki/GUIToolkit
- The source code is under src/gui/
- The configuration config files are under data/gui/default
Some tasks need the --new-widgets since the code is only shown in the experimental mode. Tasks which need this switch have the * in the title.
Arrow keys for the slider
There's a new slider widget, but it doesn't support the keyboard yet. gui/widgets/slider.[c|h]pp
Clicking on the widget should capture the keyboard and then arrow left/right should move one step even if not all steps are visible.
Slider sizing
There are some issues with the sizing of a slider. gui/widgets/slider.[c|h]pp
In a layout step it needs to try to shrink itself, not entirely sure where or how yet, best ask mordante on irc.
Miscellaneous
More powerful village naming
Adding mountain names and other features to village names, having a second random name in village names
Currently the village naming engine has a very good structure that could allow more powerfull names to be generated. Understanding how it works should be quite easy, and a few usefull improvements could be added.
- Currently villages can use lake names and river names, this should be extended to other features like bridges, swamps, mountains etc...
- It would be nice to have a separate list of "first sylabus" and "last sylabus" for naming. That's not really needed in english, but some translations could use it
- Again, it is common to have villages with more than one "random" word in them. having a $name2 variable would be nice
Euschn 24/03/2009
Debug Mode
- New debug command functionality (setting additional status.variables, possibly terrain)
Fixed parameter in a nimation
since we're a little short in easy codings, this feature request is easy.
Ask Boucman for details