Dear visitor, welcome to WesWorld. If this is your first visit here, please read the Help. It explains in detail how this page works. To use all features of this page, you should consider registering. Please use the registration form, to register here or read more information about the registration process. If you are already registered, please login here.
Quoted
Originally posted by BruceDuncan
Perdy's apparent departure leaves the Philippines without a player/caretaker. I would like to put my name forward for that role.
Quoted
Originally posted by Desertfox
Mexico and the Philippines have been friends for a while now, and both countries Bruce has taken over where good friends with Mexico. But as soon as he took them over, there was a 180 reversal in relations. It makes things complicated and I don't want it happening again. Another country I'm fine with because he does a good job with detail.
Quoted
Originally posted by ShinRa_Inc
I also don't recall any specific mention of relations between Mexico and the Phillipines, (it has admittedly been quite some time since Swamphen was running things, and no one's really 'stuck it out' since), but it would make good sense for both parties to have good relations.
Quoted
Originally posted by TheCanadian
I really have no objection to Bruce running the Philippines per say, though perhaps I would counsel that if Bruce can bring the Philippines up to speed on a variety of areas, then if/when we have a suitable player that could fill that spot it would make it easier on said new player.
Quoted
Originally posted by BruceDuncan
I thank you for the general vote of confidence on my request. I will endeavor to bring the Philippines up to speed as quickly as possible.
Towards that end, I must ask the opinion of the player-base on two matters:
1. I have attempted to audit the existing Philippine sim reports to establish what exactly the status of the vessels under construction, and the state of Philippine tonnage. This has proved extremely difficult. The expenditures cited in individual sim reports do not add properly, and values shift from report to report. For example, the 3Q40 sim reports ends with a stockpile of 1,329 tons; the 4Q40 sim report begins with a stockpile of 2,444 tons. I have gone back as far as 1939 and there appears to me little likelihood of resolving the inconsistencies.
I would propose to the player-base the following: My best effort has reduced the error in the 4Q40 sim report to a deficit of 17 tons, which could be counter-balanced by deducting that from the tonnage specified as being used to repair ships subsequently scrapped. Rather than do that, I would propose that a line be drawn at the close of 1940 and that for 1Q41 the Philippines begin with a zero stockpile.
Quoted
Originally posted by BruceDuncan
2. In reviewing the Philippine order of battle and sim reports back to the 1930s I find that there are four cruisers cited as being in existence which do not appear in the encyclopedia – at least not directly.
There are references to the heavy cruisers Cebu and Luzon, built circa 1934-35. The fragmentary tonnages cited in the existing sim reports imply that these are two vessels of the Basilan class, which would explain why they have no separate encyclopedia entry of their own. Unfortunately the 4Q34, 1Q35 and 2Q35 sim reports are not on file, and the completion of the vessels in question comes in those months. I would ask the concurrence of the player-base to treating the Cebu and Luzon as the third and fourth units of the Basilan class.
(Of course, if anyone has definite information to the contrary, please bring it to my attention so that the mystery can be dealt with.)
There are also references to two small cruisers, the Masbate and Mindoro, in the 3Q34 sim report but in no surviving sim report thereafter. I have no information what these vessels ought to represent. Therefore, in the absence of information from any other players who may know of these vessels, I propose to presume that they do not in fact exist.
Forum Software: Burning Board® Lite 2.1.2 pl 1, developed by WoltLab® GmbH