Join GitHub today
GitHub is home to over 36 million developers working together to host and review code, manage projects, and build software together.
Sign upDebug message about mandated special spawns serves no purpose #19290
Comments
This comment has been minimized.
This comment has been minimized.
|
Indeed, its hard to tell what its actually counting, and if there is/was never an issue in the coregame why was it included in such an abrasive manner? |
This comment has been minimized.
This comment has been minimized.
|
It counts the sum of mandatory counts of all specials. Defining extra mandatory specials effectively pushes out some "mandatory" specials into optional ones. This means that the abrasive warning is well deserved: "mandatory" loses its meaning if it can't actually be enforced. For example, if you want to make sure every overmap contains an evac center, but then request no less than 10k ponds, the evac center will no longer be guaranteed. The message could possibly be displayed in some different way, but it does deserve to be a big red warning for the designer (not necessarily for players). |
illi-kun
added
the
<Suggestion / Discussion>
label
Nov 18, 2016
This comment has been minimized.
This comment has been minimized.
|
I have observed this while testing Mining Mod today. Can we confirm that minimum demanded specials are actually being enforced if under the threshold? I increased the minimum due to signs that minimums were not enforced, frequently seeing overmaps with no sign of veins generated unless the minimum was solidly high. If I can confirm that a reasonable number is reliably generated when the minimum is reduced from 100 each (which was overkill), then I can safely reduce each to around 5 or so. It would be prudent for @mugling to mention this problem in #19376. Edit, it would seem that I can only get away with 1 or 2 as the minimum if Arcana and Magic Items and More Locations are in use. |
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
|
I am uncertain. Was there a pull request recently affecting overmap specials? It has to have been something generating this debug message. |
This comment has been minimized.
This comment has been minimized.
|
It seems it is either #19223 or one of the prior pull requests in that series. In this case, it would seem that the issue (too many minimums) is pre-existing, but this issue makes it visible to mod authors. They should be made aware of this maximum of minimums (odd as that phrase sounds) so they may test what will stay within acceptable limits. |
codemime
added
the
Mapgen
label
Jan 15, 2017
This comment has been minimized.
This comment has been minimized.
|
Any possible way to correct this? |
This comment has been minimized.
This comment has been minimized.
|
Yea. Mod authors can overwrite the defaults Like I do. |
This comment has been minimized.
This comment has been minimized.
|
How so? |
This comment has been minimized.
This comment has been minimized.
|
https://github.com/pisskop/PKs_Rebalancing/blob/master/pk_overmap_freqloc.json#L1296 Take all of these. But this line is about the outpost; that bunker with 8 turrets and 4 spotlights that only usually spawn rarely off of roads. I make them spawn much more. Essentially I redefine the locations after the coregame loads. |
This comment has been minimized.
This comment has been minimized.
|
I see. Peculiar. Not sure if that is the ideal solution. I assume it can at least be made more efficient and futureproof by use of |
This comment has been minimized.
This comment has been minimized.
|
This was invalid to start with, and most of the mandatory misuse seems to have been corrected by now. |
pisskop commentedNov 15, 2016
While it complains about too many mandatory spawns, it still manages to spawn several optional spawns and Ive never noticed it to fail to spawn at least 1 mandated spawn.
Its a thrown error that doesnt particularly help. Nor does it particularly seem to be an issue.