Download PES 2017 Stadium Server 1.0 For Sider 3.3.4 Tools by Zlac

FEATURES :

GDB-style unlimited stadium management
mostly unchanged stadium packaging – entire stadium directory tree (starting with “common” folder) can be copy-pasted into one top-level folder (usually indicating stadium name)
- supported folders from the usual stadium-related cpk-tree:
  - common\bg\model\bg
    - ad, audi, bill, cheer, effect, pitch, scarecrow, sky, stadium, staff, tv
  - common\demo\fixdemo
    - end, ent
  - common\render\model\bg\hit
    - bill, stadium
  - common\render\thumbnail\stadium
- IMPORTANT: db files (common\etc\…) for stadium registration are not required. DO NOT INCLUDE THOSE!!
stadium assignment to individual home teams via map_teams.txt file
stadium assignment to competitions via map_competitions.txt file – i.e. all teams participating in particular competition will use identical stadium
- IMPORTANT: by default, competition assignment always takes priority over team assignment in all modes except Exhibition mode matches
  - but, there’s a way to override that behavior for any individual competition – by slightly modifying StadiumServer.lua script itself, you can add/remove competition IDs in override_competitions table, thus defining more or less competitions where team assignment takes priority over competition assignment
- support for optional stadium to be used in final match only (not tested yet, hopefully it works)
correct stadium previews and stadium names are displayed in game menus (where available, depending on game mode) and scoreboards
while in edit mode, stadium server does nothing

Current limitations/issues:

adboards handling – by default, stadium server will load common\bg\model\bg\bill related files (including config.xml!!) if they exist within custom stadium files. If you’d like to use your already configured .cpk adboards packs, you can comment-out single line of code in StadiumServer.lua to disable adboards serving (see the code, it is noted where that line of code is)

IMPORTANT: cooperation with other .lua scripts that use “set_stadium” event – unfortunately, because of the way the stadiums are structured and handled by the game, it was necessary for StadiumServer.lua to use set_stadium event to force the game to use the exact stadium ID of the new stadium, in order to load all the files that belong to that stadium. Another approach, which would not “steal” set_stadium event (i.e. trying to override the files of any stadium that the game would like to use) did not prove successful, because stadiums simply are not file-for-file compatible, causing various artifacts when trying to replace e.g. stadium using ID 016 with custom stadium using any other ID

Bottom-line – if you want StadiumServer to work, you must not use any other .lua scripts that use set_stadium event to change stadium_id

you can still use additional .lua scripts to modify stadium conditions (day/night, weather, summer/winter) by using newly introduced set_conditions event (see Sider 3.3.4 release notes) – just to be on the safe side of the story, place your set_conditions related scripts below StadiumServer.lua in sider.ini

Recommended way to package stadiums that are available in .cpk files

Although extracted stadium packs may work without any problems, I’d recommend to use only one stadium per folder in content\stadium-server.
It is recommended to remove any files that are not directly related to stadium (especially common\etc\… files)

HOW TO USE :

Unpack the archive and copy folders ‘content’ and ‘modules’ inside your sider 3.3.4 folder
Add lua.module = “StadiumServer.lua” near the top of the Extension modules section in sider.ini
Customize map_teams.txt and map_competitions.txt files and add more stadium folders in content\stadium-server folder
- Please, read carefully all the comments inside map_teams.txt and map_competitions.txt files! Always use leading zeroes when writing stadium ID’s!

CREDITS :