Understanding ESMS

<body topmargin=0 leftmargin=0 marginheight=0 marginwidth=0> <script type="text/javascript"> //OwnerIQ var __oiq_pct = 50; if( __oiq_pct>=100 || Math.floor(Math.random()*100/(100-__oiq_pct)) > 0 ) { var _oiqq = _oiqq || []; _oiqq.push(['oiq_addPageBrand','Lycos']); _oiqq.push(['oiq_addPageCat','Internet > Websites']); _oiqq.push(['oiq_addPageLifecycle','Intend']); _oiqq.push(['oiq_doTag']); (function() { var oiq = document.createElement('script'); oiq.type = 'text/javascript'; oiq.async = true; oiq.src = document.location.protocol + '//px.owneriq.net/stas/s/lycosn.js'; var s = document.getElementsByTagName('script')[0]; s.parentNode.insertBefore(oiq, s); })(); } //Google Analytics var _gaq = _gaq || []; _gaq.push(['_setAccount','UA-21402695-19']); _gaq.push(['_setDomainName','tripod.com']); _gaq.push(['_setCustomVar',1,'member_name','basileague',3]); _gaq.push(['_trackPageview']); (function() { var ga = document.createElement('script'); ga.type = 'text/javascript'; ga.async = true; ga.src = ('https:' == document.location.protocol ? 'https://ssl' : 'http://www') + '.google-analytics.com/ga.js'; var s = document.getElementsByTagName('script')[0]; s.parentNode.insertBefore(ga, s); })(); //Lycos Init function getReferrer() { var all= this.document.cookie; if (all== '') return false; var cookie_name = 'REFERRER='; var start = all.lastIndexOf(cookie_name); if (start == -1) return false; start += cookie_name.length; var end = all.indexOf(';', start); if (end == -1) end = all.length; return all.substring(start, end); } function getQuery() { var rfr = getReferrer(); if (rfr == '') return false; var q = extractQuery(rfr, 'yahoo.com', 'p='); if (q) return q; q = extractQuery(rfr, '', 'q='); return q ? q : ""; } function extractQuery(full, site, q_param) { var start = full.lastIndexOf(site); if (start == -1) return false; start = full.lastIndexOf(q_param); if (start == -1) return false; start += q_param.length; var end = full.indexOf('&', start); if (end == -1) end = full.length; return unescape(full.substring(start, end)).split(" ").join("+"); } function generateHref(atag, template){ atag.href=template.replace('_MYURL_', window.location.href.replace('http://', '')).replace('_MYTITLE_','Check%20out%20this%20Tripod%20Member%20site!'); } var lycos_ad = Array(); var lycos_onload_timer; var cm_role = "live"; var cm_host = "tripod.lycos.com"; var cm_taxid = "/memberembedded"; var tripod_member_name = "basileague"; var tripod_member_page = "basileague/esms.htm"; var tripod_ratings_hash = "1747893443:73e9046c1007be0258b897824a19ff39"; var lycos_ad_category = null; var lycos_ad_remote_addr = "209.202.244.9"; var lycos_ad_www_server = "www.tripod.lycos.com"; var lycos_ad_track_small = ""; var lycos_ad_track_served = ""; var lycos_search_query = getQuery(); </script> <script type="text/javascript" src="https://scripts.lycos.com/catman/init.js"></script> <script type='text/javascript'> var googletag = googletag || {}; googletag.cmd = googletag.cmd || []; (function() { var gads = document.createElement('script'); gads.async = true; gads.type = 'text/javascript'; var useSSL = 'https:' == document.location.protocol; gads.src = (useSSL ? 'https:' : 'http:') + '//www.googletagservices.com/tag/js/gpt.js'; var node = document.getElementsByTagName('script')[0]; node.parentNode.insertBefore(gads, node); })(); </script> <script type='text/javascript'> googletag.cmd.push(function() { googletag.defineSlot('/95963596/TRI_300X250_dfp', [300, 250], 'div-gpt-ad-1450204159126-0').addService(googletag.pubads()); googletag.defineSlot('/95963596/TRI_above_728x90_dfp', [728, 90], 'div-gpt-ad-1450204159126-1').addService(googletag.pubads()); googletag.defineSlot('/95963596/TRI_below_728x90_dfp', [728, 90], 'div-gpt-ad-1450204159126-2').addService(googletag.pubads()); googletag.pubads().enableSingleRequest(); googletag.enableServices(); }); </script> <script type="text/javascript"> (function(isV) { if( !isV ) { return; } var adMgr = new AdManager(); var lycos_prod_set = adMgr.chooseProductSet(); var slots = ["leaderboard", "leaderboard2", "toolbar_image", "toolbar_text", "smallbox", "top_promo", "footer2", "slider"]; var adCat = this.lycos_ad_category; adMgr.setForcedParam('page', (adCat && adCat.dmoz) ? adCat.dmoz : 'member'); if (this.lycos_search_query) { adMgr.setForcedParam("keyword", this.lycos_search_query); } else if(adCat && adCat.find_what) { adMgr.setForcedParam('keyword', adCat.find_what); } for (var s in slots) { var slot = slots[s]; if (adMgr.isSlotAvailable(slot)) { this.lycos_ad[slot] = adMgr.getSlot(slot); } } adMgr.renderHeader(); adMgr.renderFooter(); }((function() { var w = 0, h = 0, minimumThreshold = 300; if (top == self) { return true; } if (typeof(window.innerWidth) == 'number' ) { w = window.innerWidth; h = window.innerHeight; } else if (document.documentElement && (document.documentElement.clientWidth || document.documentElement.clientHeight)) { w = document.documentElement.clientWidth; h = document.documentElement.clientHeight; } else if (document.body && (document.body.clientWidth || document.body.clientHeight)) { w = document.body.clientWidth; h = document.body.clientHeight; } return ((w > minimumThreshold) && (h > minimumThreshold)); }()))); window.onload = function() { var f = document.getElementById("FooterAd"); var b = document.getElementsByTagName("body")[0]; b.appendChild(f); f.style.display = "block"; document.getElementById('lycosFooterAdiFrame').src = '/adm/ad/footerAd.iframe.html'; // DOM Inj Ad (function(isTrellix) { var e = document.createElement('iframe'); e.style.border = '0'; e.style.margin = 0; e.style.display = 'block'; e.style.cssFloat = 'right'; e.style.height = '254px'; e.style.overflow = 'hidden'; e.style.padding = 0; e.style.width = '300px'; var isBlokedByDomain = function( href ) { var blockedDomains = [ "ananyaporn13000.tripod.com", "xxxpornxxx.tripod.com" ]; var flag = false; for( var i=0; i<blockedDomains.length; i++ ) { if( href.search( blockedDomains[ i ] ) >= 0 ) { flag = true; } } return flag; } var getMetaContent = function( metaName ) { var metas = document.getElementsByTagName('meta'); for (i=0; i<metas.length; i++) { if( metas[i].getAttribute("name") == metaName ) { return metas[i].getAttribute("content"); } } return false; } var getCommentNodes = function(regexPattern) { var nodes = {}; var nodesA = []; var preferredNodesList = ['a', 'c', 'b']; (function getNodesThatHaveComments(n, pattern) { if (n.hasChildNodes()) { if (n.tagName === 'IFRAME') { return false; } for (var i = 0; i < n.childNodes.length; i++) { if ((n.childNodes[i].nodeType === 8) && (pattern.test(n.childNodes[i].nodeValue))) { var areaName = pattern.exec(n.childNodes[i].nodeValue)[1]; nodes[areaName] = n; } else if (n.childNodes[i].nodeType === 1) { getNodesThatHaveComments(n.childNodes[i], pattern); } } } }(document.body, regexPattern)); for (var i in preferredNodesList) { if (nodes[preferredNodesList[i]]) { if( isTrellix && nodes[preferredNodesList[i]].parentNode.parentNode.parentNode.parentNode ) { nodesA.push(nodes[preferredNodesList[i]].parentNode.parentNode.parentNode.parentNode); } else { nodesA.push( nodes[preferredNodesList[i]] ); } } } return nodesA; } var properNode = null; var areaNodes = getCommentNodes( new RegExp( '^area Type="area_(\\w+)"' ) ); for (var i = 0; i < areaNodes.length; i++) { var a = parseInt(getComputedStyle(areaNodes[i]).width); if ((a >= 300) && (a <= 400)) { properNode = areaNodes[i]; break; } } var propertyName = getMetaContent("property") || false; if( isTrellix && (properNode) ) { e.src = '/adm/ad/injectAd.iframe.html'; properNode.insertBefore(e, properNode.firstChild); } else if( isTrellix && !( properNode ) ) // Slap the ad eventhought there is no alocated slot { e.src = '/adm/ad/injectAd.iframe.html'; e.style.cssFloat = 'none'; var cdiv = document.createElement('div'); cdiv.style = "width:300px;margin:10px auto;"; cdiv.appendChild( e ); b.insertBefore(cdiv, b.lastChild); } else if( !isBlokedByDomain( location.href ) ) { var injF = document.createElement('iframe'); injF.style.border = '0'; injF.style.margin = 0; injF.style.display = 'block'; injF.style.cssFloat = 'none'; injF.style.height = '254px'; injF.style.overflow = 'hidden'; injF.style.padding = 0; injF.style.width = '300px'; injF.src = '/adm/ad/injectAd.iframe.html'; if( b && ( !isTrellix || ( typeof isTrellix == "undefined" ) ) ) // All other tripod props { var cdiv = document.createElement('div'); cdiv.style = "width:300px;margin:10px auto;"; cdiv.appendChild( injF ); b.insertBefore(cdiv, b.lastChild); } } }( document.isTrellix )); } </script> <div id="tb_container" style="background:#DFDCCF; border-bottom:1px solid #393939; position:relative; z-index:999999999!important">  <style> .adCenterClass{margin:0 auto} </style> <div id="tb_ad" class="adCenterClass" style="display:block!important; overflow:hidden; width:916px;"> <div id="ad_container" style="display:block!important; float:left; width:728px "> <script type="text/javascript"> if (typeof lycos_ad !== "undefined" && "leaderboard" in lycos_ad) { document.write(lycos_ad['leaderboard']); } </script> </div> </div> </div> <script type="text/javascript"> if (typeof lycos_ad !== "undefined" && "slider" in lycos_ad) { document.write(lycos_ad['slider']); } </script>  <div id="FooterAd" style="background:#DFDCCF; border-top:1px solid #393939; clear:both; display:none; width:100%!important; position:relative; z-index:999999!important; height:90px!important"> <div class="adCenterClass" style="display:block!important; overflow:hidden; width:916px;"> <div id="footerAd_container" style="display:block!important; float:left; width:728px"> <iframe id="lycosFooterAdiFrame" style="border:0; display:block; float:left; height:96px; overflow:hidden; padding:0; width:750px"></iframe> </div> </div> </div> <table cellpadding=0 cellspacing=0 border=0><tr> <td valign="top" colspan=2 height=40 BGCOLOR="#006699" TEXT="#080000"> <div> <B><U>BreakAway Soccer: International League</U></b></div> <bR> <div> </div> </td> </tr><tr> <td valign="top" width=175 BGCOLOR="#FFCC66" TEXT="#080000"> <div> <A HREF="index.htm" TARGET="_top" TITLE="BreakAway Soccer: International League"><U><B><U>Back to Home Page</U></b></U></A></div> <div> <A HREF="general.htm" TARGET="_top" TITLE="General Rules"><U>General Rules</U></A></div> <div> <A HREF="finance.htm" TARGET="_top" TITLE="Finance Rules"><U>Finance Rules</U></A></div> <div> <A HREF="transfer.htm" TARGET="_top" TITLE="Transfer Rules"><U>Transfer Rules</U></A></div> <div> <A HREF="stadimp.htm" TARGET="_top" TITLE="Stadium Improvements"><U>Stadium Improvements</U></A></div> <bR> <div> <A HREF="esmsinfo.htm" TARGET="_top" TITLE="ESMS Info"><U>ESMS Info</U></A></div> <div> <B>Understanding ESMS</b></div> <div> <A HREF="makets.htm" TARGET="_top" TITLE="Making a Teamsheet"><U>Making a Teamsheet</U></A></div> <div> <A HREF="gamecomp.htm" TARGET="_top" TITLE="Other Game Components"><U>Other Game Components</U></A></div> <div> <A HREF="aboutmc.htm" TARGET="_top" TITLE="About Match Commentary"><U>About Match Commentary</U></A></div> <div> <A HREF="tactics.htm" TARGET="_top" TITLE="Tactics Table"><U>Tactics Table</U></A></div> <bR> <div> <A HREF="tsmhelp.htm" TARGET="_top" TITLE="Teamsheet Maker Help"><U>Teamsheet Making Help</U></A></div> <div> <A HREF="tschelp.htm" TARGET="_top" TITLE="Teamsheet Checker Help"><U>Teamsheet Checker Help</U></A></div> <div> <A HREF="mchelp.htm" TARGET="_top" TITLE="EOFA MCV Help"><U>EOFA MCV Help</U></A></div> </td> <td valign="top" height=440 BGCOLOR="#FFFFFF" TEXT="#080000"> <div> <U>Understanding ESMS</U></div> <div> <B><U>2.0 HOW IS A GAME PLAYED ?</U></b></div> <bR> <div> <U>2.0.1</U> A team in ESMS is represented by a "roster". A roster is a text file in a special format, which includes all the players of the team and their attributes. </div> <bR> <div> <U>2.0.2</U> A "team sheet" in ESMS is a text file which includes orders for the game for each team. These orders include the list of 11 starting players, 5 subs and various commands for the program. The teamsheet is basically the instructions each manager gives to his team before the game. This is explained in "Making a Teamsheet".</div> <bR> <div> <U>2.0.3</U> To play a match each manager has to send the league administrator a teamsheet with instructions for the match. The administrator must have the rosters of the participating teams. It is very important to note here that the game is not run in "real-time", but all at once. Meaning that a manager can't interfere on a specific minute and tell the administrator to substitute a player or change tactic. The manager's work is concluded by sending a teamsheet with instructions to the admin. All these instructions are included in the team sheet sent by the managers in the correct format, the program reads these instructions and implements them during the game. After the game is finished, the program generates commentary file for the game and the admin sends it to the managers of the playing teams. The commentary files are discussed in further detail in "About Match Commentary Files". Then, the admin uses the various supplementary tools of ESMS to update the rosters and the league table.</div> <bR> <div> <B><U>2.1 ROSTERS & PLAYERS</U></b></div> <bR> <div> If you look at a valid roster of ESMS, you will see a header line and a list of players with a lot of numbers near them. This section will explain exactly what each number means.</div> <bR> <div> Let's first look at the player skills section of the roster file:</div> <div> <TABLE BORDER="2" CELLPADDING="2" CELLSPACING="1" WIDTH="471" BORDERCOLORLIGHT="#C0C0C0" BORDERCOLORDARK="#808080" FRAME="BOX" RULES="ALL" ALIGN="BOTTOM" HSPACE="0" VSPACE="0" > <tR> <tD VALIGN=TOP HEIGHT= 16 WIDTH="96"><div> <B>Name</b></div> </tD> <tD VALIGN=TOP WIDTH="26"><div> <B>Age</b></div> </tD> <tD VALIGN=TOP WIDTH="26"><div> <B>Nat</b></div> </tD> <tD VALIGN=TOP WIDTH="26"><div> <B>St</b></div> </tD> <tD VALIGN=TOP WIDTH="26"><div> <B>Tk</b></div> </tD> <tD VALIGN=TOP WIDTH="26"><div> <B>Ps</b></div> </tD> <tD VALIGN=TOP WIDTH="26"><div> <B>Sh</b></div> </tD> <tD VALIGN=TOP WIDTH="26"><div> <B>Ag</b></div> </tD> <tD VALIGN=TOP><NOBR><div> <B>KAb</b></div> </NOBR></tD> <tD VALIGN=TOP WIDTH="26"><div> <B>TAb</b></div> </tD> <tD VALIGN=TOP WIDTH="26"><div> <B>PAb</b></div> </tD> <tD VALIGN=TOP><NOBR><div> <B>SAb</b></div> </NOBR></tD> </tR> <tR> <tD VALIGN=CENTER HEIGHT= 16 WIDTH="96"><div> N_Amoruso</div> </tD> <tD VALIGN=TOP WIDTH="26"><div> 22</div> </tD> <tD VALIGN=TOP WIDTH="26"><div> ita</div> </tD> <tD VALIGN=TOP WIDTH="26"><div> 1</div> </tD> <tD VALIGN=TOP WIDTH="26"><div> 4</div> </tD> <tD VALIGN=TOP WIDTH="26"><div> 6</div> </tD> <tD VALIGN=TOP WIDTH="26"><div> 10</div> </tD> <tD VALIGN=TOP WIDTH="26"><div> 26</div> </tD> <tD VALIGN=TOP WIDTH="26"><div> 300</div> </tD> <tD VALIGN=TOP WIDTH="26"><div> 420</div> </tD> <tD VALIGN=TOP WIDTH="26"><div> 550</div> </tD> <tD VALIGN=TOP WIDTH="26"><div> 690</div> </tD> </tR> </TABLE></div> <bR> <div> <U>2.1.1 Name:</U> The name of the player. It's recommended not to create names longer than 12 characters. The name of a player mustn't include spaces, it is common to use underline '_' symbol instead (placing the first letter of the first name separated by '_' from the rest, ie. M_Owen or A_DelPiero).</div> <bR> <div> <U>2.1.2 Age:</U> Player's age. Each league sets different rules for player aging. The league may decide that each season each player is getting older by one year, etc. The age is placed in the roster with no use for the game running program and needed only for statistics and rules set up by each league.</div> <bR> <div> <U>2.1.3 Nat:</U> Player's nationality, abbreviated in 3 characters. As the age, it is not used by the game running program and placed in the roster only for statistics. </div> <bR> <div> These three attributed were mostly for statistics, and didn't really have any meaning to the program (except of maybe the name, which must be the same in the roster and in the teamsheets, to let ESMS recognize which players a manager wishes to use in a game). The rest of the attributes are used and changed by the program.</div> <bR> <div> This is the right place to say that in ESMS the player has no predifined position, and it is up to the manager to decide, depending on the player's skills, where he want the player to play in each game. A player can play as a goalkeeper (GK), defender (DF), midfielder (MF) or forward (FW). </div> <bR> <div> Now we'll move to the next attributes:</div> <div> <U>2.1.4 St:</U> Is the player's shot-stopping skill. In other words, his goalkeeping skill. For the best  performance, the manager has to place the player with the highest St as the goalkeeper. Of course the manager is not obligated to do so, and it is up to him to consider.</div> <bR> <div> <U>2.1.5 Tk:</U> Is the player's tackling skill. Mostly used by players playing in the defense.</div> <bR> <div> <U>2.1.6 Ps:</U> Is the player's passing skill. Mostly used by players in the midfield, for creating opportunities and assisting goals.</div> <bR> <div> <U>2.1.7 Sh:</U> Is the player's shooting skill. It defines the player's skill to shot to goal and reach these shooting chances.</div> <bR> <div> Note: From what you can see on the player in the example, his highest skill is shooting. Therefore this player will perform his best as a forward. Of course he can play in any position if needed, even as goalkeeper, but his contribution will be  worse than as a forward.</div> <bR> <div> <U>2.1.8 Ag:</U> Is the player's aggression. The aggression of a player doesn't change, it stays the same for his whole career. In ESMS the aggression is a value between 1 and 100 and it defines how aggressive a player plays. More on aggression can be read in "Other Game Components", paragraph 4.3.1</div> <bR> <div> <U>2.1.9 KAb, TAb, PAb, SAb:</U> Player ability for each skill. A number ranging from 0 to 1000 and can affect the player's skills. Abilities vary from game to game depending on the player's performance.</div> <bR> <div> Now we look at the stats section. This comes immediately after the players skills section of the roster:</div> <div> <TABLE BORDER="2" CELLPADDING="2" CELLSPACING="1" WIDTH="442" BORDERCOLORLIGHT="#C0C0C0" BORDERCOLORDARK="#808080" FRAME="BOX" RULES="ALL" ALIGN="BOTTOM" HSPACE="0" VSPACE="0" > <tR> <tD VALIGN=CENTER HEIGHT= 16 WIDTH="96"><div> <B>Name</b></div> </tD> <tD VALIGN=TOP WIDTH="30"><div> <B>Gam</b></div> </tD> <tD VALIGN=TOP WIDTH="26"><div> <B>Sav</b></div> </tD> <tD VALIGN=TOP WIDTH="26"><div> <B>Ktk</b></div> </tD> <tD VALIGN=TOP WIDTH="26"><div> <B>Kps</b></div> </tD> <tD VALIGN=TOP WIDTH="26"><div> <B>Sht</b></div> </tD> <tD VALIGN=TOP WIDTH="26"><div> <B>Gls</b></div> </tD> <tD VALIGN=TOP WIDTH="26"><div> <B>Ass</b></div> </tD> <tD VALIGN=TOP WIDTH="26"><div> <B>Dp</b></div> </tD> <tD VALIGN=TOP WIDTH="26"><div> <B>Inj</b></div> </tD> <tD VALIGN=TOP WIDTH="26"><div> <B>Sus</b></div> </tD> </tR> <tR> <tD VALIGN=TOP HEIGHT= 16 WIDTH="96"><div> N_Amoruso</div> </tD> <tD VALIGN=TOP WIDTH="30"><div> 5</div> </tD> <tD VALIGN=TOP WIDTH="26"><div> 0</div> </tD> <tD VALIGN=TOP WIDTH="26"><div> 2</div> </tD> <tD VALIGN=TOP WIDTH="26"><div> 4</div> </tD> <tD VALIGN=TOP WIDTH="26"><div> 12</div> </tD> <tD VALIGN=TOP WIDTH="26"><div> 4</div> </tD> <tD VALIGN=TOP WIDTH="26"><div> 0</div> </tD> <tD VALIGN=TOP WIDTH="26"><div> 8</div> </tD> <tD VALIGN=TOP WIDTH="26"><div> 0</div> </tD> <tD VALIGN=TOP WIDTH="26"><div> 0</div> </tD> </tR> </TABLE></div> <bR> <div> <U>2.1.10 Gam:</U> Simply the amount of games the player played. If the player participated in a game, even if he played a single minute, it will be counted as an another game when the admin runs the roster updating tool.</div> <bR> <div> <U>2.1.11 Sav:</U> The total amount of saves the player made. Only if the player played as a goalkeeper he can make saves.</div> <bR> <div> <U>2.1.12 Ktk:</U> The total amount of key tackles the player made to stop scoring opportunities. Usually defenders will make the highest amount of tackles, but midfielders and forwards tackle sometimes</div> <div> too.</div> <bR> <div> <U>2.1.13 Kps:</U> The total amount of key passes made by the player to create goalscoring opportunities.</div> <bR> <div> <U>2.1.14 Sht:</U> The total amount of shots to goal taken by the player.</div> <bR> <div> <U>2.1.15 Gls:</U> The total amount of goals scored by the player.</div> <bR> <div> <U>2.1.16 Ass:</U> The total amount of assists made by the player.</div> <bR> <div> <U>2.1.17 Dp:</U> The total amount of disciplinary points accumulated by the player. Disciplinary Points (DP) are "accumulated" when a player gets yellow/red cards. More on DP in "Other Game Components", section 4.4</div> <bR> <div> <U>2.1.18 Inj:</U> If a player isn't currently injured, Inj is 0. If a player is injured, it indicates the amount of weeks he can't play.</div> <bR> <div> <U>2.1.19 Sus:</U> If a player isn't currently suspended, Sus is 0. If a player is suspended, it indicates the amount of games he can't play. More on this in "Other Game Components", section 4.4</div> <bR> <div> Note the difference between "weeks" for Inj and "games" for suspensions... Think about this in "real life" terms: It is common to play league games once a week, with cup games in the middle of the week. A player is injured for a certain amount of time (eg. if he's injured for a week, he'll miss one game in a normal league run, but he'll miss more games if some cup games were played during the week), but suspended for an amount of games. You should keep this in mind while planning your league.</div> <bR> <div> <B><U>2.2 PLAYER POSITIONS</U></b></div> <bR> <div> As was stated earlier, a player in ESMS doesn't have a pre-defined position. The manager will have to decide where to play a player in a game.</div> <bR> <div> The ESMS system has 4 possible positions for players:</div> <bR> <div> GK: Goalkeepers, only one GK is allowed to play at the same time</div> <div> DF: Defender</div> <div> MF: Midfielder</div> <div> FW: Forward</div> <bR> <div> Each league must decide for itself the restrictions on the maximum and/or minimal number of DF's, MF's and FW's which can play at the same time.</div> <bR> <div> <B><U>2.3 PLAYERS' "ACTUAL" SKILLS DURING THE GAME</U></b></div> <bR> <div> As you saw in section 2.1, each player in ESMS has 4 different skills + aggression. These are his "raw skills", and he won't always play with the same skill in a game. An "actual skill", is the players's raw skill after some mathematical operations, which depend on tactics and player's fatigue during the game (more on fatigue in "Other Game Components", paragraph 4.2.1).</div> <bR> <div> In any case, if two different players have different raw skills, and they both play with the same conditions in the game (position and the tactic of the team), then the player with the higher raw skill will have a higher actual skill.</div> <bR> <div> Aggression of the player stays the same during the course of a game. The "Shot Stopping" (St) ability doesn't change either (affected only by fatigue).</div> <bR> <div> <B>How do actual skills depend on player's position?</b></div> <div> A player which plays as defender will never use his full shooting potential, as being a defender he will get almost no chances to score. It also depends on the tactic of the team, but it can be generally said that the full raw skill of the player will be preserved only if the player plays on a suitable position. For example if a player with Tk2, Ps4 and Sh10 playing in the defense will have a defensive skill of 2 (it also depends on the tactic, of course), but his actual Ps and Sh will be less than the raw values. Therefore, a player with skills Tk4 Ps3 Sh3 will be more efficient as a defender, despite being a generally worse player than the first one.</div> <bR> <div> Players with more than one high skill will be extremely useful as they will be able to perform well in several positions.</div> <bR> <div> <B><U>2.4 TEAM TACTICS</U></b></div> <bR> <div> Each manager may choose a tactic for his team for a game. The tactic can be changed during the game by suitable instructions in the teamsheets.</div> <bR> <div> This is the listing of possible tactics in ESMS:</div> <div> <U>2.4.1 N:</U> Normal. No specific style of play, just normal game, trying to use all parts of the team in the most suitable way.</div> <bR> <div> <U>2.4.2 D:</U> Defensive. Focusing more on the defense. D is hard to score against, but won't create many opportunities either, it is the most defensive tactic. Midfielders and even forwards will pay more attention to the defense. </div> <bR> <div> <U>2.4.3 A:</U> Attacking. The most offensive tactic. The players try to score as much as possible, effectively neglecting the defense. This tactic may get you to score more goals but also concede quite a few...</div> <bR> <div> <U>2.4.4 P:</U> Passing. The team tries to move the ball quickly using a lot of passes, even when these are not really needed. More players try to help in the midfield to create slow but efficient opportunities. This tactic is more offensive than Normal but less offensive than Attacking.</div> <bR> <div> <U>2.4.5 C:</U> Counter attack. The players concentrate on the defense, while the forwards are waiting for counter-opportunities. This tactic is more defensive than Normal but not as defensive as D.</div> <bR> <div> <U>2.4.6 L:</U> Long Ball. The most intriguing and unexpected tactic. Can easily win a game with some circumstances, and completely fail with other. The midfield is almost unsignificant, as the team tries to defend and reach the forwards with long balls. Thus, this tactic is especially useful for teams with weak midfielders, and against some tactics/formations can prove to be a lethal weapon.</div> <bR> <div> Note: Each tactic, except of Normal has some bonuses against some other tactics, which makes the decisions more complicated and challenging. The bonuses table is below. It also includes the 'Bonus type', which tells where is the bonus added.</div> <bR> <div> <TABLE BORDER="2" CELLPADDING="2" CELLSPACING="1" WIDTH="414" BORDERCOLORLIGHT="#C0C0C0" BORDERCOLORDARK="#808080" FRAME="BOX" RULES="ALL" ALIGN="LEFT" HSPACE="0" VSPACE="0" > <tR> <tD VALIGN=TOP HEIGHT= 16 WIDTH="116"><div> <B><U>Tactic</U></b></div> </tD> <tD VALIGN=TOP WIDTH="106"><div> <B><U>versus</U></b></div> </tD> <tD VALIGN=CENTER WIDTH="166"><div> <B><U>Bonus</U></b></div> </tD> </tR> <tR> <tD VALIGN=TOP HEIGHT= 16 WIDTH="116"><div> Normal</div> </tD> <tD VALIGN=TOP WIDTH="106"><div> -</div> </tD> <tD VALIGN=TOP WIDTH="166"><div> -</div> </tD> </tR> <tR> <tD VALIGN=TOP HEIGHT= 16 WIDTH="116"><div> Defensive</div> </tD> <tD VALIGN=TOP WIDTH="106"><div> Longball</div> </tD> <tD VALIGN=TOP WIDTH="166"><div> Defence</div> </tD> </tR> <tR> <tD VALIGN=TOP HEIGHT= 16 WIDTH="116"><div> Attacking</div> </tD> <tD VALIGN=TOP WIDTH="106"><div> Defensive</div> </tD> <tD VALIGN=TOP WIDTH="166"><div> Attack</div> </tD> </tR> <tR> <tD VALIGN=TOP HEIGHT= 32 ><NOBR><div> Counter Attack</div> </NOBR></tD> <tD VALIGN=TOP WIDTH="106"><div> Passing</div> <div> Attacking</div> </tD> <tD VALIGN=CENTER WIDTH="166"><div> Midfield</div> <div> Attack</div> </tD> </tR> <tR> <tD VALIGN=TOP HEIGHT= 32 WIDTH="116"><div> Longball</div> </tD> <tD VALIGN=TOP><NOBR><div> Attacking</div> <div> Counter Attack</div> </NOBR></tD> <tD VALIGN=TOP WIDTH="166"><div> Defence</div> <div> Attack</div> </tD> </tR> <tR> <tD VALIGN=TOP HEIGHT= 16 WIDTH="116"><div> Passing</div> </tD> <tD VALIGN=TOP WIDTH="106"><div> Longball</div> </tD> <tD VALIGN=TOP WIDTH="166"><div> Defence</div> </tD> </tR> </TABLE></div> <bR> <bR> <bR> <bR> <bR> <bR> <bR> <bR> <bR> <bR> <bR> <bR> <bR> <div> Conclusion: As you can see, the bonuses table is rather complicated, and you can benefit a lot from predicting correctly which tactic your opponent uses. If you aren't certain about which tactic your opponent uses, you can play the Normal tactic, as no other tactics has bonuses against it. Each manager will eventually have some "repertoire" of tactics for every case, when you must win, when you</div> <div> must not lose, etc...</div> <bR> <div> <B><U>2.5  TEAM FORMATIONS</U></b></div> <bR> <div> ESMS has no pre-defined formations for teams. The formation is simply the amount of DF's/MF's and FW's, so it is clear that a team with 3 defenders, 4 midfielders and 3 forwards plays a 3-4-3 formation. As stated above, the program itself poses no restrictions on the maximal/minimal amount of players </div> <div> in each position, each league must define these restrictions for itself. It is highly reccomended for each league to do so, in order not to have unusual situations, ie. a game between two teams with a 8-1-1 formation can be very boring, and it is doubtful if any scoring opportunities will be created.</div> <bR> <div> Each manager decides on his favourite formation either by his players' skills (if for example his team hasn't almost any good forwards, he will prefer formations with fewer players in the attack) or if a manager feels that a specific formation AND tactic just "works well" for his  team and sticks to it.</div> <bR> <div> Tactics and formation are very much linked, not by the program (ESMS doesn't mind which tactic/formation you play) but by the manager himself. It would be, of course, bizzare to play 2-2-6 Defensive, as the formation and the tactic contradict each other. </div> </td> </tr></table></body>