Topic: Bugs
Tibor |
Posted at: 2017-02-13, 20:14
@WorldSavior
Top Quote |
kaputtnik |
Posted at: 2017-02-13, 21:09
Just copy the whole folder into your home directory, there you should have write permissions. Then start widelands with the option Top Quote |
Tibor |
Posted at: 2017-02-13, 22:20
Alternatively: a) Check your file manager - perhaps it allows rights elevation (will ask for root password) and allow you to change authorization b) Or just lear how to change the authorities/ownership in console
or
then change ownership to your user (use actual account of course)
or allow write access to everybody (g=group, o=others, +w=add write access)
And then the file will be writable for you from GUI EDIT: So the "session" can look like:
Edited: 2017-02-14, 10:46
Top Quote |
fuchur |
Posted at: 2017-02-14, 21:51
Ok, I think I didn't phrase correctly what I meant. That was the following: the game is designed that buildings are burned down if they are not protected by soldiers inside or the influence range of another manned military building. Consequently that happens to the headquarters as well. Besides that I share your opinion that it is an annoying behaviour. If it can be attacked there should be a possibility to adjust the number of guaranteed defenders. As far as I understand the bug report it should be easier now with the new barracks feature to make headquarters, warehouses and ports behave like military buildings in a way that you can adjust a number of soldiers to stay there. Top Quote |
Notabilis |
Posted at: 2017-02-14, 23:51
The new barracks building has nothing to do with this functionality. It only moves the soldier creation out of the warehouses and into a designated building. There is a bug open for defenders in headquarters but it is already a "bit" older and there hasn't been any work (directly) on it in the last years: https://bugs.launchpad.net/widelands/+bug/536583 Top Quote |
Ex-Member |
Posted at: 2017-02-15, 11:23
I think it is a no brainer that HQ, ports and warehouses should be military buildings, in the sense that they can store soldiers and once soldiers enter any of them there will always be at least one as a 'last line of defence' defender. This means you can attack ports and warehouses as well as HQ, but there will normally be at least one defender so the attack is slightly harder than attacking a HQ is now. If the building is captured and is in the influence range od another manned militay building then it is destroyed, if it is not protected by another building then you capture it, the enemy workers all leave and do their headless chicken dance taking with them wares of their tribe, any wares that are common to all tribes are captured by you, logs, coal, ores and metals etc.everything else that was there is gone, even if you are the same tribe. Top Quote |
GunChleoc |
Posted at: 2017-02-15, 13:55
IMO the best implementation for a garrison would be to have a separate object for it, like the portdock for ports. Then we could theoretically garrison any building type that we want. Busy indexing nil values Top Quote |
GunChleoc |
Posted at: 2017-02-15, 20:28
The missing attack message is confirmed now. Thanks for the savegame Issues in this thread that still need looking into and be turned into proper bugs:
Busy indexing nil values Top Quote |
fuchur |
Posted at: 2017-02-15, 21:03
I don't know anything about the implementation of headquarters. But I understood comment #1 in that bug (which I mentioned before) in a way that it causes problems with soldier production if there are stationed soldiers in the headquarter. So I thought now with soldier production outsourced to the barracks it would be easier to fix. But again, I don't know the source code. @Tinker: Do you really think it's a good idea that you can get wares stored in a captured warehouse? I'm even not sure if it should be possible to capture a warehouse. But maybe this discussion and ideas should be made in the bug report. Top Quote |
GunChleoc |
Posted at: 2017-02-15, 22:07
Capturing wares would be a separate feature implementation-wise that could have its own bug if we want it. Busy indexing nil values Top Quote |