Estrutura inicial do cliente Unreal Zeus MMO alinhada ao padrao "cliente solto + servidor valida input/velocidade" (ADR 0038): - Source/ZMMO/Game/Entity/ — IZMMOEntityInterface, AZMMOEntity (base AActor para Mob/NPC/Object), AZMMOPlayerCharacter (player local com CMC livre, Enhanced Input, envio de C_INPUT_AXIS), AZMMOPlayerProxy (snapshot-only para players remotos). - Source/ZMMO/Game/Controller/ — AZMMOPlayerController com IMC defaults (IMC_Default + IMC_MouseLook) e suporte opcional a virtual joystick. - Source/ZMMO/Game/Modes/ — AZMMOGameMode (defaults para PlayerCharacter / PlayerController), UZMMOGameInstance (auto-connect ao servidor Zeus em Init e logging dos eventos OnConnected/OnDisconnected/...). - Source/ZMMO/Game/Network/ — UZMMOWorldSubsystem (registry EntityId -> AActor*, dispatch dos delegates OnPlayerSpawned/Despawned/ StateUpdate; ignora snapshots locais do cliente solto). - Config/DefaultEngine.ini — GlobalDefaultGameMode aponta para /Script/ZMMO.ZMMOGameMode; GameInstanceClass para /Script/ZMMO.ZMMOGameInstance; redirects para a nova hierarquia. - ZMMO.Build.cs — depende de ZeusNetwork; PublicIncludePaths para a nova arvore Game/Entity|Controller|Modes|Network. - Content — assets do template ThirdPerson (Mannequins, IAs/IMCs, Lvl_ThirdPerson + TestWorld). Os Variant_* levels ficam no commit inicial mas serao limpos numa proxima sessao com aprovacao explicita (Master Rule para .umap/.uasset). Notas: - BP_ThirdPersonCharacter/GameMode/PlayerController ainda apontam para a hierarquia antiga e estao a aguardar aprovacao para remocao (Master Rule). - README.md descreve a arquitectura e o smoke test de conexao.
42 lines
2.7 KiB
Markdown
42 lines
2.7 KiB
Markdown
<!-- BEGIN MICROSOFT SECURITY.MD V0.0.8 BLOCK -->
|
|
|
|
## Security
|
|
|
|
Microsoft takes the security of our software products and services seriously, which includes all source code repositories managed through our GitHub organizations, which include [Microsoft](https://github.com/microsoft), [Azure](https://github.com/Azure), [DotNet](https://github.com/dotnet), [AspNet](https://github.com/aspnet), [Xamarin](https://github.com/xamarin), and [our GitHub organizations](https://opensource.microsoft.com/).
|
|
|
|
If you believe you have found a security vulnerability in any Microsoft-owned repository that meets [Microsoft's definition of a security vulnerability](https://aka.ms/opensource/security/definition), please report it to us as described below.
|
|
|
|
## Reporting Security Issues
|
|
|
|
**Please do not report security vulnerabilities through public GitHub issues.**
|
|
|
|
Instead, please report them to the Microsoft Security Response Center (MSRC) at [https://msrc.microsoft.com/create-report](https://aka.ms/opensource/security/create-report).
|
|
|
|
If you prefer to submit without logging in, send email to [secure@microsoft.com](mailto:secure@microsoft.com). If possible, encrypt your message with our PGP key; please download it from the [Microsoft Security Response Center PGP Key page](https://aka.ms/opensource/security/pgpkey).
|
|
|
|
You should receive a response within 24 hours. If for some reason you do not, please follow up via email to ensure we received your original message. Additional information can be found at [microsoft.com/msrc](https://aka.ms/opensource/security/msrc).
|
|
|
|
Please include the requested information listed below (as much as you can provide) to help us better understand the nature and scope of the possible issue:
|
|
|
|
* Type of issue (e.g. buffer overflow, SQL injection, cross-site scripting, etc.)
|
|
* Full paths of source file(s) related to the manifestation of the issue
|
|
* The location of the affected source code (tag/branch/commit or direct URL)
|
|
* Any special configuration required to reproduce the issue
|
|
* Step-by-step instructions to reproduce the issue
|
|
* Proof-of-concept or exploit code (if possible)
|
|
* Impact of the issue, including how an attacker might exploit the issue
|
|
|
|
This information will help us triage your report more quickly.
|
|
|
|
If you are reporting for a bug bounty, more complete reports can contribute to a higher bounty award. Please visit our [Microsoft Bug Bounty Program](https://aka.ms/opensource/security/bounty) page for more details about our active programs.
|
|
|
|
## Preferred Languages
|
|
|
|
We prefer all communications to be in English.
|
|
|
|
## Policy
|
|
|
|
Microsoft follows the principle of [Coordinated Vulnerability Disclosure](https://aka.ms/opensource/security/cvd).
|
|
|
|
<!-- END MICROSOFT SECURITY.MD BLOCK -->
|