# Support for optional stadium to be used in final match of the competition only – again, pretty much self-explanatory. To override this default behavior, you can slightly modify a script itself – add/remove competition IDs in override_competitions table, thus defining more or less competitions where individual team assignments from map_teams.txt takes priority over competition assignment from map_competitions.txtĭefault stadium server script already includes an exhaustive override_competitions table, which should cover all available exhibition, league and league-cup matches – so that you can keep individual stadiums for those teams that already have one in map_teams.txt, while all the other teams without individual stadium would get randomly selected stadium from map_competitions.txt IMPORTANT: by default, competition assignment would always take priority over team assignment in any game mode, but that can be easily configured within. IMPORTANT: db files (common\etc\… data_st_list.bin, Stadium.bin, StadiumOrder.bin, StadiumOrderInConfederation.bin) for stadium registration are not required. These folders (and their subfolders) from the usual stadium-related cpk-tree are currently supported:įor adboards – only config.xml is supported, for stadiums that need to REMOVE adboards completely!!Ĭommon\bg\model\bg\bill\config\config.xml cpk version, meaning that entire stadium directory tree (starting with “Asset” and “common” folders) can be copy-pasted into one top-level GDB folder. # Mostly unchanged stadium packaging – stadium structure remains almost identical to the. # GDB-style unlimited stadium management – add as many stadiums as you want in a GDB-like folder structure
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |