{"id":37812,"date":"2019-10-31T22:19:55","date_gmt":"2019-10-31T19:19:55","guid":{"rendered":"https:\/\/prohoster.info\/blog\/megapaket-kak-razrabotchikam-factorio-udalos-reshit-problemu-s-multipleerom-na-200-igrokov\/"},"modified":"2019-10-31T22:19:55","modified_gmt":"2019-10-31T19:19:55","slug":"megapaket-kak-razrabotchikam-factorio-udalos-reshit-problemu-s-multipleerom-na-200-igrokov","status":"publish","type":"post","link":"https:\/\/prohoster.info\/sq\/blog\/administrirovanie\/megapaket-kak-razrabotchikam-factorio-udalos-reshit-problemu-s-multipleerom-na-200-igrokov","title":{"rendered":"Megan\u00ebpako: si arrit\u00ebn zhvilluesit e Factorio t\u00eb zgjidhin problemin me multiplayer me 200 lojtar\u00eb","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"

\"Megan\u00ebpako:
\nN\u00eb maj t\u00eb k\u00ebtij viti, un\u00eb mora pjes\u00eb si lojtar n\u00eb eventin MMO KatherineOfSky<\/a><\/noindex>. Vura re se kur numri i lojtar\u00ebve arrin nj\u00eb num\u00ebr t\u00eb caktuar, pas \u00e7do disa minutash, nj\u00eb pjes\u00eb e tyre \"bien\". Me fat p\u00ebr ju (por jo p\u00ebr mua), un\u00eb isha nj\u00eb nga ata lojtar\u00eb q\u00eb \u00e7aktivizoheshin \u00e7do her\u00eb<\/b>, edhe me nj\u00eb lidhje t\u00eb mir\u00eb. E mora k\u00ebt\u00eb si nj\u00eb sfid\u00eb personale dhe fillova t\u00eb k\u00ebrkoj arsyet e problemit. Pas tre jav\u00ebsh debugging, testimi dhe rregullimesh, gabimi u eliminua p\u00ebrfundimisht, por ky udh\u00ebtim nuk ishte aq i leht\u00eb.<\/p>\n

Problemet e loj\u00ebrave multiplayer jan\u00eb shum\u00eb t\u00eb v\u00ebshtira p\u00ebr t'u gjurmuar. Ato zakonisht lindin n\u00eb kushte shum\u00eb specifike t\u00eb parametra t\u00eb rrjetit dhe n\u00eb gjendje shum\u00eb specifike t\u00eb loj\u00ebs (n\u00eb k\u00ebt\u00eb rast - pranin\u00eb e mbi 200 lojtar\u00ebve). Dhe edhe kur arrin t\u00eb riprodhosh problemin, \u00ebsht\u00eb e pamundur ta debugosh si\u00e7 duhet, sepse vendosja e pikave kontrolli ndalon loj\u00ebn, ngat\u00ebrroj tempor\u00ebt dhe zakonisht \u00e7on n\u00eb p\u00ebrfundimin e lidhjes p\u00ebr shkak t\u00eb tejkalimit t\u00eb afatit. Por fal\u00eb k\u00ebmb\u00ebnguljes dhe nj\u00eb mjeti t\u00eb mrekulluesh\u00ebm t\u00eb quajtur clumsy<\/a><\/noindex> , arrita t\u00eb zbuloj se \u00e7far\u00eb po ndodhte.<\/p>\n

N\u00eb p\u00ebrmbledhje: p\u00ebr shkak t\u00eb nj\u00eb gabimi dhe implementimi t\u00eb pap\u00ebrfunduar t\u00eb simulimit t\u00eb gjendjes s\u00eb vones\u00ebs, klienti ndonj\u00ebher\u00eb gjendej n\u00eb nj\u00eb situat\u00eb ku duhej t\u00eb d\u00ebrgonte nj\u00eb paket\u00eb rrjeti, e cila p\u00ebrmbante veprimet e lojtar\u00ebve n\u00eb lidhje me rreth 400 entitete lojrash (ne e quajm\u00eb \"megapaketa\"). Pas k\u00ebsaj, serveri duhet jo vet\u00ebm t\u00eb marr\u00eb sakt\u00ebsisht t\u00eb gjitha k\u00ebto veprime hyr\u00ebse, por gjithashtu t\u00eb d\u00ebrgoj\u00eb ato te t\u00eb gjith\u00eb klient\u00ebt e tjer\u00eb. N\u00ebse ke 200 klient\u00eb, kjo b\u00ebhet shpejt nj\u00eb problem. Kanali drejt serverit shpejt mbushet, \u00e7ka \u00e7on n\u00eb humbje paketash dhe nj\u00eb kaskad\u00eb t\u00eb k\u00ebrkesave t\u00eb rip\u00ebrs\u00ebritura p\u00ebr paketa. Vonimi i veprimeve hyr\u00ebse pastaj \u00e7on n\u00eb at\u00eb q\u00eb edhe m\u00eb shum\u00eb klient\u00eb fillojn\u00eb t\u00eb d\u00ebrgojn\u00eb megapaketa, dhe mbingarkesa e tyre b\u00ebhet edhe m\u00eb e fort\u00eb. Klient\u00ebt me fat arrijn\u00eb t\u00eb rikuperohen, t\u00eb tjer\u00ebt \"bien\".
\n<\/a><\/noindex>
\n\"Megan\u00ebpako:
\nProblemi ishte mjaft themelor dhe m\u00eb zuri dy jav\u00eb p\u00ebr ta zgjidhur. Ajo \u00ebsht\u00eb mjaft teknike, prandaj m\u00eb posht\u00eb do t\u00eb shpjegoj detajet teknike t\u00eb holl\u00ebsishme. Por fillimisht duhet t\u00eb dini se nga versioni 0.17.54, i l\u00ebshuar m\u00eb 4 qershor, n\u00eb kushtet e problemeve t\u00eb p\u00ebrkohshme me lidhjen, multiplayer b\u00ebhet m\u00eb i q\u00ebndruesh\u00ebm, dhe fshehja e vonesave \u00ebsht\u00eb shum\u00eb m\u00eb pak me defekte (m\u00eb pak ngecje dhe teleporter). P\u00ebr m\u00eb tep\u00ebr, e kam ndryshuar m\u00ebnyr\u00ebn e fshehjes s\u00eb vonesave n\u00eb luftime dhe shpresoj q\u00eb p\u00ebr k\u00ebt\u00eb arsye ato do t\u00eb jen\u00eb pak m\u00eb t\u00eb buta.<\/p>\n

Megan multiplayer - detajet teknike<\/h3>\n

\nN\u00ebse e shpjegojm\u00eb thjesht, multiplayer n\u00eb loj\u00eb funksionon si m\u00eb posht\u00eb: t\u00eb gjith\u00eb klient\u00ebt simulojn\u00eb gjendjen e loj\u00ebs, duke marr\u00eb dhe d\u00ebrguar vet\u00ebm hyrjen e lojtarit (t\u00eb quajtur \"veprimet e hyrjes\", Input Actions<\/i>). Detyra kryesore e serverit \u00ebsht\u00eb t\u00eb transferoj\u00eb Input Actions<\/i> dhe t\u00eb kontrolloj\u00eb q\u00eb t\u00eb gjith\u00eb klient\u00ebt t\u00eb realizojn\u00eb t\u00eb nj\u00ebjtat veprime n\u00eb nj\u00eb cik\u00ebl. M\u00eb shum\u00eb informacion rreth k\u00ebsaj mund t\u00eb lexoni n\u00eb postimin FFF-149<\/a><\/noindex>.<\/p>\n

Duke qen\u00eb se serveri duhet t\u00eb marr\u00eb vendime n\u00eb lidhje me veprimet q\u00eb duhet t\u00eb realizohen, veprimi i lojtarit kalon n\u00ebp\u00ebr nj\u00eb rrug\u00eb t\u00eb till\u00eb: veprimi i lojtarit -> klienti i loj\u00ebs -> rrjeti -> serveri -> rrjeti -> klienti i loj\u00ebs. Kjo do t\u00eb thot\u00eb se \u00e7do veprim i lojtarit b\u00ebhet vet\u00ebm pasi kalon n\u00eb rrug\u00ebn e tij p\u00ebrmes rrjetit. P\u00ebr k\u00ebt\u00eb arsye, loja do t\u00eb dukej shum\u00eb e ndaluar, prandaj pothuajse menj\u00ebher\u00eb pas shfaqjes s\u00eb multiplayer-it n\u00eb loj\u00eb u krijua nj\u00eb mekaniz\u00ebm p\u00ebr fshehjen e vonesave. Fshehja e vonesave imiton hyrjen e lojtarit pa marr\u00eb parasysh veprimet e lojtar\u00ebve t\u00eb tjer\u00eb dhe vendimet e serverit.<\/p>\n

\"Megan\u00ebpako:
\nN\u00eb Factorio ka nj\u00eb gjendje loj\u00eb Game State<\/i> \u2014 kjo \u00ebsht\u00eb gjendja e plot\u00eb e Hart\u00ebs, lojtarit, entiteteve dhe gjith\u00e7kaje tjet\u00ebr. Ajo simulohet n\u00eb m\u00ebnyr\u00eb determinuese n\u00eb t\u00eb gjith\u00eb klient\u00ebt n\u00eb baz\u00eb t\u00eb veprimeve t\u00eb marra nga serveri. Gjendja e loj\u00ebs \u00ebsht\u00eb e shenjt\u00eb, dhe n\u00ebse ndonj\u00ebher\u00eb fillon t\u00eb ndryshoj\u00eb nga serveri ose nga ndonj\u00eb klient tjet\u00ebr, ndodh nj\u00eb desinkronizim.<\/p>\n

P\u00ebrve\u00e7 Game State<\/i> ne kemi nj\u00eb gjendje vonesash Latency State<\/i>. Ajo p\u00ebrmban nj\u00eb n\u00ebn-grup t\u00eb vog\u00ebl t\u00eb gjendjes kryesore. Latency State<\/i> nuk \u00ebsht\u00eb e shenjt\u00eb dhe thjesht paraqet nj\u00eb pamje t\u00eb asaj si do t\u00eb duket gjendja e loj\u00ebs n\u00eb t\u00eb ardhmen bazuar n\u00eb hyrjet e lojtar\u00ebve. Input Actions<\/i>.<\/p>\n

P\u00ebr k\u00ebt\u00eb, ne ruajm\u00eb nj\u00eb kopje t\u00eb krijuar Input Actions<\/i> n\u00eb radh\u00ebn e vonesave.<\/p>\n

\"Megan\u00ebpako:
\nPra fillon, skena n\u00eb an\u00ebn e klientit duket pak a shum\u00eb k\u00ebshtu:<\/p>\n

    \n
  1. Aplikojm\u00eb Input Actions<\/i> t\u00eb gjith\u00eb lojtar\u00ebt n\u00eb Game State<\/i> ashtu si\u00e7 k\u00ebto veprime hyr\u00ebse u mor\u00ebn nga serveri.<\/li>\n
  2. Fshijm\u00eb nga radh\u00ebt e vonesave t\u00eb gjitha Input Actions<\/i>, q\u00eb sipas t\u00eb dh\u00ebnave t\u00eb serverit, tashm\u00eb ishin aplikuar n\u00eb Game State<\/i>.<\/li>\n
  3. Fshijm\u00eb Latency State<\/i> dhe e rivendosim, q\u00eb t\u00eb duket sakt\u00ebsisht si Game State<\/i>.<\/li>\n
  4. Aplikojm\u00eb t\u00eb gjitha veprimet nga radh\u00ebt e vonesave n\u00eb Latency State<\/i>.<\/li>\n
  5. N\u00eb baz\u00eb t\u00eb t\u00eb dh\u00ebnave Game State<\/i> dhe Latency State<\/i> rend\u00ebrtojm\u00eb loj\u00ebn p\u00ebr lojtarin.<\/li>\n<\/ol>\n

    \nE gjith\u00eb kjo p\u00ebrs\u00ebritet n\u00eb \u00e7do cik\u00ebl.<\/p>\n

    P\u00ebr shum\u00eb t\u00eb komplikuar? Mos u relaksoni, kjo nuk \u00ebsht\u00eb e gjith\u00eb historia. P\u00ebr t\u00eb kompensuar pasigurin\u00eb e lidhjeve t\u00eb internetit, ne kemi krijuar dy mekanizma:<\/p>\n