a must be above any other 'lua.module=' lines for scripts that use set_stadium event too). lua script that also uses 'set_stadium' event to change stadium_id (i.e. stadium using ID 016 with custom stadium using any other ID.īottom-line - if you want StadiumServer to work, you must not give HIGHER PRIORITY to any other. 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. lua scripts that use 'set_stadium' and 'set_conditions' events - unfortunately, because of the way the stadiums are structured and handled by the game, it was necessary for a to use set_stadium event exclusively 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.Īnother approach, which would not 'steal' set_stadium event (i.e. It works safely only with special blank adboards template (which should be used only to fully remove adboards from stadiums) and allows for supplying a custom version of config.xml database for adboards (to assign blank template to the stadium).Ĭustom adboard models, 'baked' directly into stadium 3d model are neither safe nor meant to be used via stadium server - adboards available via global ad-boards system (.cpk files or sider's live.cpk root) should work well with stadiums from stadium server too!ģ. adboards handling - by default, stadium server does not allow for custom adboards embedded within stadiums. No support for replay mode yet - if you're going to watch a saved replay of a match that has been played on custom stadium, you'll see black screen with adboards only during replay at best (perhaps it may also crash the game) - current version of sider does not support replay gallery!Ģ. # stadium previews visible on overlay, when possible - REQUIRES sider 5.1.4 or newer - update your sider first!!ġ. # Stadium customization via weather-conditions based AddOn system - allows easier creation and application of 3rd party mods to a specific GDB stadium (turf mods for specific stadium, gfx_mod, etc.)
# More/less detailed level of logging - in config.ini file, property 'detailed_logging' controls whether more info will be logged to sider log (value '1') or less info (value '0'). # Correct stadium previews and stadium names - displayed in game menus (where available, depending on game mode) and scoreboards
0 kommentar(er)
