Page 1 of 1

SOLVED - WPP V01.00.04 Beta 5.2 - Problem with logistics points returned

Posted: Wed Oct 27, 2021 5:29 pm
by ncc1701e
I discover this problem with 1.00.041 patch and reproduced it with Beta 5.2.
I think the problem is applicable to all nations and maybe to Warplan (I did not test it).

Here is the situation of Thailand at turn one. Thailand has 10 logistics points in its stockpile.

Image

RE: WPP V01.00.04 Beta 5.2 - Problem with logistics points returned

Posted: Wed Oct 27, 2021 5:33 pm
by ncc1701e
Thailand has also a small corps.

Image

RE: WPP V01.00.04 Beta 5.2 - Problem with logistics points returned

Posted: Wed Oct 27, 2021 5:34 pm
by ncc1701e
This small corps consumes 20 logistics points.

Image

RE: WPP V01.00.04 Beta 5.2 - Problem with logistics points returned

Posted: Wed Oct 27, 2021 5:35 pm
by ncc1701e
Now, I can disband this corps.

Image

RE: WPP V01.00.04 Beta 5.2 - Problem with logistics points returned

Posted: Wed Oct 27, 2021 5:36 pm
by ncc1701e
And this is wonderful, I have 30 logistics points in the stockpile of Thailand. Everything is fine until then Alvaro. [:D]

Image

RE: WPP V01.00.04 Beta 5.2 - Problem with logistics points returned

Posted: Wed Oct 27, 2021 5:38 pm
by ncc1701e
Now, the bug. I will not disband the small corps. Instead, I will move it by sea to this location.

Image

RE: WPP V01.00.04 Beta 5.2 - Problem with logistics points returned

Posted: Wed Oct 27, 2021 5:39 pm
by ncc1701e
I will use everything I have to sunk the small corps. Poor guys. [:)]

Image

RE: WPP V01.00.04 Beta 5.2 - Problem with logistics points returned

Posted: Wed Oct 27, 2021 5:42 pm
by ncc1701e
But, and here is the problem, I have 10 logistics points in the stockpile of Thailand. The loss of the corps at sea has not retrieved the logistics points to the pool.

Image

RE: WPP V01.00.04 Beta 5.2 - Problem with logistics points returned

Posted: Sat Nov 06, 2021 10:31 am
by AlvaroSousa
Thanks I will look into it.

Re: WPP V01.00.04 Beta 5.2 - Problem with logistics points returned

Posted: Sun Mar 27, 2022 12:41 pm
by ncc1701e
This is fixed in my current V1.06.2 patch, super!