[{"data":1,"prerenderedAt":375},["ShallowReactive",2],{"\u002F2017-04-20-ue4-multiplayer-and-network-overview":3},{"id":4,"title":5,"body":6,"date":350,"description":12,"extension":351,"meta":352,"navigation":355,"path":367,"seo":368,"stem":369,"tags":370,"__hash__":374},"blogs\u002F_legacy\u002F2017\u002F2017-04-20-ue4-multiplayer-and-network-overview.md","UE4网络连接与多人游戏",{"type":7,"value":8,"toc":335},"minimark",[9,13,16,20,23,34,37,48,51,54,57,60,63,66,69,73,76,83,86,92,95,100,103,108,111,117,120,126,129,135,138,141,144,149,152,155,161,164,170,179,182,185,188,191,194,197,200,203,206,209,212,217,220,232,235,241,244,250,253,256,259,266,288,292,295,298,301,304,307,310,317,321,328],[10,11,12],"p",{},"UE4的Replication系统在设计上非常的高效和迅速，要制作联网游戏相关功能的话使用起来也很方便。",[10,14,15],{},"当前UE4版本为4.15.0。",[17,18,19],"h2",{"id":19},"概述",[10,21,22],{},"蓝图中的GameMode是自带支持Replication系统的，GameMode也是整个Replication系统在逻辑设计上的中心。如果在设计游戏时，不需要联网功能，目前引擎已经提供了一个新的基类GameModeBase来使用。",[10,24,25,26,33],{},"网络模式相关的官方文档在[",[27,28,32],"a",{"href":29,"rel":30},"https:\u002F\u002Fdocs.unrealengine.com\u002Flatest\u002FCHN\u002FGameplay\u002FNetworking\u002Findex.html",[31],"nofollow","这里","]。",[10,35,36],{},"网络模式的调试可以在PIE中进行，点击调试旁边的下拉三角就可以进行设置。Server的模式分为DedicatedServer和ListenServer，如果在多客户端模式下进行屏幕调试输出，会发现输出会自动表明输出者的身份，在源代码中可以找到它的实现方式：",[38,39,44],"pre",{"className":40,"code":42,"language":43},[41],"language-text","UWorld* World = GEngine->GetWorldFromContextObject(WorldContextObject, false);\nFString Prefix;\nif (World)\n{\n  if (World->WorldType == EWorldType::PIE)\n  {\n    switch(World->GetNetMode())\n    {\n      case NM_Client:\n        Prefix = FString::Printf(TEXT(\"Client %d: \"), GPlayInEditorID - 1);\n      break;\n      case NM_DedicatedServer:\n      case NM_ListenServer:\n        Prefix = FString::Printf(TEXT(\"Server: \"));\n      break;\n      case NM_Standalone:\n      break;\n    }\n  }\n}\n","text",[45,46,42],"code",{"__ignoreMap":47},"",[10,49,50],{},"这个宏也可以自己拿来做一些判断用，例如区分独立服务器与监听服务器。",[10,52,53],{},"另外，如果要使用官方模板进行功能测试的话需要注意：",[10,55,56],{},"TopDown模板的角色移动是基于NavMesh的，而这个机制本身是不支持直接联网的，因此角色不会移动。",[10,58,59],{},"而默认的Blank模板的Pawn是没有CharacterMoveMentComponent的，当然也就不会同步角色移动。",[17,61,62],{"id":62},"属性复制",[10,64,65],{},"Replication系统的核心是复制，“真正”的UWorld更新是在Server上运行的，而Client上的UWorld则接受来自Server的复制更新，同时Client也会进行一定的“预测”，但是一切状态值以Server上的为准。这样的设计下，只要采用合理的逻辑，就可以杜绝作弊。",[10,67,68],{},"UE4中Replication在设置完成后是自动运行的，在使用时只要留意，凡是需要所有客户端都获得的状态更新，包括Spawn、Replicate的值，都必须在服务器上进行。在客户端上进行修改只会让他们在下一次同步时被覆盖掉。",[70,71,72],"h3",{"id":72},"开启复制",[10,74,75],{},"属性复制可以在Actor的属性面板中开启",[10,77,78],{},[79,80],"img",{"alt":81,"src":82},"image","\u002Fwp-content\u002Fuploads\u002F2017\u002F04\u002Fimage_thumb.png",[10,84,85],{},"C++中则需要在构造函数中指定",[38,87,90],{"className":88,"code":89,"language":43},[41],"bReplicates = true;\n",[45,91,89],{"__ignoreMap":47},[10,93,94],{},"开启复制之后，对于具体的属性，只要指定为可复制即可：",[10,96,97],{},[79,98],{"alt":81,"src":99},"\u002Fwp-content\u002Fuploads\u002F2017\u002F04\u002Fimage_thumb-1.png",[10,101,102],{},"其中Replicated就是复制模式，而RepNotify会在属性被变更时触发一个通知事件，非常的有用。在蓝图下，这个事件会自动生成：",[10,104,105],{},[79,106],{"alt":81,"src":107},"\u002Fwp-content\u002Fuploads\u002F2017\u002F04\u002Fimage_thumb-2.png",[10,109,110],{},"而在C++模式下，就要做一些额外的设定操作，除了指定属性可复制之外",[38,112,115],{"className":113,"code":114,"language":43},[41],"UPROPERTY(Replicated)\nuint32 bFlag:1;\n",[45,116,114],{"__ignoreMap":47},[10,118,119],{},"还要设置同步属性表",[38,121,124],{"className":122,"code":123,"language":43},[41],"void AReplicatedActor::GetLifetimeReplicatedProps(TArray\u003C FLifetimeProperty > & OutLifetimeProps) const\n{\nDOREPLIFETIME(AReplicatedActor, bFlag);\nDOREPLIFETIME(AReplicatedActor, IntegerArray);\n}\n",[45,125,123],{"__ignoreMap":47},[10,127,128],{},"如果要使用RepNotify的话，就必须在UPROPERTY宏中进行指定",[38,130,133],{"className":131,"code":132,"language":43},[41],"UPROPERTY(ReplicatedUsing=OnRep_Flag)\nuint32 bFlag:1;\n",[45,134,132],{"__ignoreMap":47},[10,136,137],{},"然后实现这个函数方可。",[70,139,140],{"id":140},"条件复制",[10,142,143],{},"Replication有一个重要的设置是条件复制，在蓝图中可以看到选项",[10,145,146],{},[79,147],{"alt":81,"src":148},"\u002Fwp-content\u002Fuploads\u002F2017\u002F04\u002Fimage_thumb-3.png",[10,150,151],{},"意思都比较明显，关于Owner以及Simulated、Autonomous的意思在下面会有说明，而Replay指代的是官方的回放系统，如果没有使用到的话就可以不用管它。",[10,153,154],{},"C++中要调整这个属性则需要用到属性表：",[38,156,159],{"className":157,"code":158,"language":43},[41],"void AActor::GetLifetimeReplicatedProps( TArray\u003C FLifetimeProperty > & OutLifetimeProps ) const\n{\n  DOREPLIFETIME_CONDITION( AActor, ReplicatedMovement, COND_SimulatedOnly );\n}\n",[45,160,158],{"__ignoreMap":47},[10,162,163],{},"在C++中还可以使用额外的自定义标志位来进行更新控制：",[38,165,168],{"className":166,"code":167,"language":43},[41],"void AActor::PreReplication( IRepChangedPropertyTracker & ChangedPropertyTracker )\n{\n  DOREPLIFETIME_ACTIVE_OVERRIDE( AActor, ReplicatedMovement, bReplicateMovement );\n}\n",[45,169,167],{"__ignoreMap":47},[10,171,172,173,178],{},"但是这样可能会降低效率，更详细的说明可以参照[",[27,174,177],{"href":175,"rel":176},"https:\u002F\u002Fdocs.unrealengine.com\u002Flatest\u002FCHN\u002FGameplay\u002FNetworking\u002FActors\u002FProperties\u002FConditions\u002Findex.html",[31],"官方文档","]。另外，在文档中有说明，属性表是无法在同步确立之后进行修改的。",[70,180,181],{"id":181},"参数设置",[10,183,184],{},"Replication中还有一些可选参数，其中比较重要的是Relevant机制，这个机制通过判定Actor当前是否与Player相关来有效的削减同步的数据量",[10,186,187],{},"Always Relevant会使得Actor始终被同步到各个客户端",[10,189,190],{},"Net Use Owner Relevancy则会让Actor的同步相关性与持有者相同",[10,192,193],{},"Only Relevant To Owner使得Actor只与自己的持有者保持相关",[10,195,196],{},"这里Owner的定义指代持有其的PlayerController或者Pawn，而是否相关的判定机制是可以重载的，在类中对IsNetRelevantFor函数进行重载即可。",[10,198,199],{},"还有一个特殊的标志位是bTearOff，一旦Server设置了这个值，Replication机制会将控制权交给所有的Client，实质上Actor就变成了不同步的物体，由各个Client进行控制。",[10,201,202],{},"而ReplicateMovement将会使得物体的移动被同步，也就是速度、位置这些信息。",[10,204,205],{},"bNetLoadOnClient会使得物体在Server上加载\u002FSpawn后在Client上被自动加载。",[17,207,208],{"id":208},"远程调用",[10,210,211],{},"远程函数调用提供Clinet与Server之间的函数调用桥梁，调用模式分为三种：",[10,213,214],{},[79,215],{"alt":81,"src":216},"\u002Fwp-content\u002Fuploads\u002F2017\u002F04\u002Fimage_thumb-4.png",[10,218,219],{},"选中蓝图中的函数就能看到这个设置，它们之间的区别如下：",[221,222,223,226,229],"blockquote",{},[10,224,225],{},"NetMulticast: 多路传送，由服务器调用所有的客户端，比如用于播放特效",[10,227,228],{},"Server: 在服务器上运行，只有角色标志为ROLE_Authority或ROLE_AutonomousProxy的Actor才能调用",[10,230,231],{},"Client: 在其所属的客户端上运行",[10,233,234],{},"其中，Server函数还可以提供额外的校验函数以方便对传输到服务器的值进行检测，这个设置只能在C++中使用，蓝图中并未看到相关选项：",[38,236,239],{"className":237,"code":238,"language":43},[41],"UFUNCTION(Server, Reliable, WithValidation)\nvoid Server_ReliableFunctionCallThatRunsOnServer();   UFUNCTION(Client, Reliable)\nvoid Client_ReliableFunctionCallThatRunsOnOwningClientOnly();   UFUNCTION(NetMulticast, Unreliable)\nvoid Client_UnreliableFunctionCallThatRunsOnAllClients();\n",[45,240,238],{"__ignoreMap":47},[10,242,243],{},"对函数进行实现",[38,245,248],{"className":246,"code":247,"language":43},[41],"void AReplicatedActor::Server_ReliableFunctionCallThatRunsOnServer_Implementation()\n{\n}\nbool AReplicatedActor::Server_ReliableFunctionCallThatRunsOnServer_Validate()\n{\n   \u002F\u002F 返回FALSE的话该Server函数就不会被执行\n   return true;\n}\nvoid AReplicatedActor::Client_ReliableFunctionCallThatRunsOnOwningClientOnly()\n{\n}   \nvoid AReplicatedActor::Client_UnreliableFunctionCallThatRunsOnAllClients_Implementation()\n{\n\n}\n",[45,249,247],{"__ignoreMap":47},[10,251,252],{},"函数还可以选择是否为可靠函数，UnReliable的设定将会使得引擎在网络带宽压力大的情况下丢弃这个函数的执行。",[10,254,255],{},"应当尽量避免频繁的远程调用以及在远程调用中直接传输并设置Server参数的行为，而只将输入传递到Server。",[17,257,258],{"id":258},"游戏架构",[10,260,261,262,33],{},"官方的指引文档中就有介绍过游戏架构,但实际上在做单机游戏时,将逻辑放在很多类中其实是等效的,这点会让人很迷惑。其实架构中的许多类是在多人模式下才会体现出他们的不同的，详细的内容可以看[",[27,263,177],{"href":264,"rel":265},"https:\u002F\u002Fdocs.unrealengine.com\u002Flatest\u002FCHN\u002FGameplay\u002FNetworking\u002FBlueprints\u002Findex.html",[31],[267,268,269,273,276,279,282,285],"ul",{},[270,271,272],"li",{},"GameInstance: 不参与网络复制，作为游戏实例而存在，在关卡切换载入时依然存在，可以用于存储用户本身的数据",[270,274,275],{},"GameMode: 只存在于Server上，核心逻辑存在于这里",[270,277,278],{},"GameState: 在Server和所有Client之间复制，用于存储当前游戏相关的数据",[270,280,281],{},"PlayerController: 每个Client只持有自己的PlayerController，并与Server进行同步",[270,283,284],{},"PlayerState: 存储每个Player的信息，会同步到所有的Client。",[270,286,287],{},"Pawns: 与所有的Client同步，但是与PlayerController以及PlayerState不同的是，Pawn死亡之后会被销毁，直到Respawn为止。",[70,289,291],{"id":290},"role与同步","Role与同步",[10,293,294],{},"Server和Client都可以使用Role系统来判断持有的Actor状态，Role被分为四种",[10,296,297],{},"ROLE_Authority：对Actor拥有控制权",[10,299,300],{},"ROLE_None：不参与网络复制",[10,302,303],{},"ROLE_SimulatedProxy：接受来自服务器更新的模拟控制器，使用已知信息进行预判",[10,305,306],{},"ROLE_AutonomousProxy：接受来自玩家的直接控制，配合玩家输入进行预判",[10,308,309],{},"客户端的模拟预判可以有效防止网络延迟引起的Lag，但是在处理角色动作，尤其是Blink之类的操作时，依然会导致奇怪的现象。",[10,311,312,313,33],{},"为了防止这些现象，官方对CharacterMovmentComponent作了增强，这个类会维护一个动作列表，在同步时，Client会被要求进行动作列表的重放，而不是直接更新位置。详细的可以参考[",[27,314,177],{"href":315,"rel":316},"https:\u002F\u002Fdocs.unrealengine.com\u002Flatest\u002FCHN\u002FGameplay\u002FNetworking\u002FCharacterMovementComponent\u002Findex.html",[31],[17,318,320],{"id":319},"misc","Misc",[10,322,323,324,33],{},"UE4提供了服务器进行无缝和非无缝关卡切换的函数，其具体的限制和功能可参看[",[27,325,177],{"href":326,"rel":327},"https:\u002F\u002Fdocs.unrealengine.com\u002Flatest\u002FCHN\u002FGameplay\u002FNetworking\u002FTravelling\u002Findex.html",[31],[10,329,330,331,33],{},"同时，为了提供轻便的服务器状况查询，而不是被强制加载关卡，UE4有提供Online Beacons的功能，由于不会用到就没有继续研究了，详情见[",[27,332,177],{"href":333,"rel":334},"https:\u002F\u002Fdocs.unrealengine.com\u002Flatest\u002FCHN\u002FGameplay\u002FNetworking\u002FOnlineBeacons\u002Findex.html",[31],{"title":47,"searchDepth":336,"depth":337,"links":338},2,3,[339,340,345,346,349],{"id":19,"depth":336,"text":19},{"id":62,"depth":336,"text":62,"children":341},[342,343,344],{"id":72,"depth":337,"text":72},{"id":140,"depth":337,"text":140},{"id":181,"depth":337,"text":181},{"id":208,"depth":336,"text":208},{"id":258,"depth":336,"text":258,"children":347},[348],{"id":290,"depth":337,"text":291},{"id":319,"depth":336,"text":320},"2017-04-20","md",{"layout":353,"status":354,"published":355,"author":356,"author_login":358,"author_email":359,"wordpress_id":360,"wordpress_url":361,"date_gmt":362,"excerpt":363},"post","publish",true,{"display_name":357,"login":358,"email":359,"url":47},"风铃","flinkor","flinkor@foxmail.com",1599,"\u002F\u002F?p=1599","2017-04-20 15:03:17 +0000",{"type":7,"value":364},[365],[10,366,12],{},"\u002F2017-04-20-ue4-multiplayer-and-network-overview",{"title":5,"description":12},"_legacy\u002F2017\u002F2017-04-20-ue4-multiplayer-and-network-overview",[371,372,373],"UE4","MultiPlayer","Replication","PzRHWaoekIzNbx0GPfE_pJ_Ew2JUROcQg2OmymCgFC8",1788763180160]