Topic: maning military buildings
GunChleoc |
Posted at: 2016-05-12, 11:49
You have the choice of iterating while adding a soldier to the warehouse, or iterating when selecting a soldier. Sorting algorithms can be made a lot more efficient than iterating though, so sorting the soldiers when adding them to the warehouse is a better implementation. If you iterate over an unsorted list while selecting you always have to go across the complete list.
It's not unimportant, but less important than a crash, for example. Which issues get addressed also depends on which developers are available - you need to know quite a bit about the engine in order to work on this, so you need somebody who knows the codebase well.
I think we should only look at this for Build 20 - at the moment, we are trying to finish up Build 19. Any changed code at all can potentially introduce a new bug. And don't worry, your feedback is appreciated Busy indexing nil values Top Quote |
teppo |
Posted at: 2016-05-14, 10:37
I was quite astonished when I realized how powerful that was. Generally, I would like to move Widelands towards the direction where micromanagement does not pay off . However, I have not figured out ways to make micromanagement of training to be less profitable (without crippling the game). Making training sites to prefer "heroes in other arts" would be a possibility. Any ideas? Top Quote |
king_of_nowhere |
Posted at: 2016-05-15, 18:45
that's not really possible, unless you want to completely remove the chance for micromanaging - and in that case one may as well go back to play settlers 2. if micromanaging is possible, then the only way to not make it advantageous would be for the computer to do all the best moves by itself. which 1) would require more skill and time than anyone here has, and 2) would make human players mostly redundant. Really, what's wrong with getting ahead by micromanaging? it's not necessary, so casual players can still enjoy the game. let powergamers also have something appealing to them. Edited: 2016-05-15, 18:45
Top Quote |
teppo |
Posted at: 2016-05-18, 16:38
I am not sure we understand each other now .. Removing the options would be stupid. I think that the training sites could be improved a lot if they, for example, would have a weak preference for tranees that are already trained in those arts the training site does not teach.
Micromanagement is not evil. However, if it brings a huge advantage then that is a sign that the buildings are not doing their job right. You would not like to instruct each forester to place their trees to vacant slots, would you? Removing the huge payoff from micromanaging makes the game better, in my opinion. Top Quote |
king_of_nowhere |
Posted at: 2016-05-18, 18:05
that's not what i meant. what i meant was that a skilled human player will always be able to do things better than the algorithm, and so he will be able to get some advantage from micromanaging; unless you go out of your way to make that impossible, but that's not good for the game. I'd say there are two different kinds of micromanaging, a good one and a bad one. good micromanagement is about making meaningful decisions; it enriches the game, and let the player use his skill for something. bad micromanagement does not involve meaningful decisions but only mechanical, repetitive tasks; it does not take skill to perform it, except maybe for remembering it all the time while doing something else. your forester example would clearly be a case of bad micromanagement. Regarding training sites, I'd say they already work pretty well. they wait long enough to kick out a soldier that if you have a passable economy you should get your soldiers to full promotions. They were vastly improved from build 18. I don't really see that they can be improved. Keep also in mind that sometimes, especially in early game, it is preferrable to send out a partially trained soldier to quickly defend the front against untrained soldiers, so I'd still pen that under "meaningful decision". Top Quote |
GunChleoc |
Posted at: 2017-01-16, 09:22
Related bug: https://bugs.launchpad.net/widelands/+bug/1643201 Busy indexing nil values Top Quote |