久久不见久久见免费视频7,99久久国产亚洲高清观看2024 ,无码人妻久久一区二区三区蜜桃

(搬运�?Mangos代码阅读

点点滴滴 — Fri, 16 Dec 2016 03:28:00 GMT

逻辑层： �c�World实现了wow的World�Q�所有的逻辑处理
　　MaNGOS 下蝲�Q�编译，配置和运行的基本步骤下蝲和安装msysgit�Q�用于代码管理我使用的是Git-1.6.5.1-preview20091022.exe
　　下蝲和安装tortoisegit�Q�用于代码管理我使用的是TortoiseGit-1.3.2.0-32bit.msi
　　使用git://github.com/mangos/mangos.git�Q�从github提取mangos代码
　　采用Git GUI工具的Clone Existing Repository�Q�得�?mangos代码�Q�我的是9560�Q�安装UDB参考这�Q?nbsp;
　　使用git://github.com/scriptdev2/scriptdev2.git�Q�从github提取scriptdev2代码
　　采用Git GUI工具的Clone Existing Repository�Q�得�?scriptdev2代码.
　　�~�译mangos我用的是VC9,打开mangoswinmangosdVC90.sln�q�行构造，构造完成后�Q�会得到mangosbinWin32_Debug文�g�?nbsp;
　　�~�译scriptdev2我用的是VC9,打开mangoswinscriptdev2VC90.sln�q�行构造，构造完成后�Q�会得到scriptdev2binWin32_Debug文�g夹也可参�?nbsp;
　　pandore
　　拯��mangossrcmangosd目录下的mangosd.conf.dist.in为mangosbinWin32_Debugmangosd.conf
　　拯��mangossrcrealmd目录下的realmd.conf.dist.in为mangosbinWin32_Debugrealmd.conf
　　从http://www.wowtaiwan.com.tw/下蝲和安装台服WOW�Q��ƈ升��到最新版本我使用的是台服WOW 3.3.2 build 11403
　　�Q�采用MaNGOS的工具ad从wow的MPQ中抽取map�Q�得到的所有的map数据文�g�Q�文件命名规范�ؓmap_id�Q?位） tileY�Q?位） tileX�Q?位）.map�Q�如文�g名�ؓ0002035.map�Q�代表的是Azeroth(地图id�?00�Q�tile坐标�?35,20). 注：WOW客户端的Tile对应mangos中的grid�Q�WOW客户端的Chunk对应mangos中的cell(1cell = 4 chunk)
　　按照常规��程�Q�包括徏立数据库和配�|�服务器�Q�把服务器跑��h��Q��用account create zzh1234567 zzh1234567 创徏一个�̎��P��使用account set gmlevel zzh1234567 3讄��U�用�?nbsp;
　　配置好客��L��后，�q�行WOW�Q�顺利登陆，呵呵
　　通过安装UDB来丰富场景FULL DB 9560 : HERE�Q�参考这�Q�在我安装DB9560的时候，发现Mangos在LoadCreatureAddons的时候，加蝲creature template addons出错�Q�Mangos只要求creature template addons�?个字�D�，而creature template addons�?个字�D�|��现在只是��单地跌��LoadCreatureAddons的调�?nbsp;
　　
�q�行Mangos �Q�运行Mangos一节过期，是以前我针对国服3.1.3版本�q�行的安装配�|�） �Q�采用MaNGOS的工具ad从wow的MPQ中抽取map�Q�得到的所有的map数据文�g�Q�文件命名规范�ؓmap_id�Q?位） tileY�Q?位） tileX�Q?位）.map�Q�如文�g名�ؓ0002035.map�Q�代表的是Azeroth(地图id�?00�Q�tile坐标�?35,20). 注：WOW客户端的Tile对应mangos中的grid�Q�WOW客户端的Chunk对应mangos中的cell(1cell = 4 chunk)
　　配置好客��L��后，�q�行WOW�Q�顺利登陆，呵呵
　　
Mangos代码阅读
　　Mangos�?3个工�E?nbsp;
　　使用�?个外部工具库�Q�分别是�Q?跨��^台的�|�络通讯框架The ADAPTIVE Communication Environment (ACE)
　　压羃库zlib
　　Socket通信�?C++ Sockets Library (使用在realmd工程中，和��用在Mangosd工程中的RASocket�Q�负责处理Remote Administration其他地方没有使用到这个C++ Sockets Library �Q�发现在C++ Sockets Library的TcpSocket::Open中存在一个问题，在n = connect(s, ad, ad);语句执行后，如果n=-1�Q�C++ Sockets Library会检��是否ERR为WSAEWOULDBLOCK�Q�否则表�C�成功，但在动态库中��用TcpSocket的时候，我发现n = connect(s, ad, ad);语句执行后，n=-1�Q�ERR会�ؓ0�Q�这个时候连接也是成功了�Q�但TcpSocket::Open会当做不成功处理我发现这个问题，但没有时间去探究原因�Q�也许�ƈ不是一个问�?nbsp;
　　C++的�ƈ行编�E�模板库Threading Building Blocks �Q�tbb �?tbbmalloc�Q?nbsp;
　　Mangos的实现分为：��d��服务器（realmd�Q�和世界服务器（mangosd+game�Q�realmd和mangos��q��了Mangos公共库（shared�Q?nbsp;
　　工程shared
　　提供了通用功能�Q�包括了数据库的��装�c�，实现了对MySql的访问，同样�Q�我们可以编写派生类来支持其他的数据�?nbsp;
　　工程script
　　提供了脚本接口，�q�实��C��单的几个脚本�Q�封装�ؓDLL�Q�提供给game使用�Q�具体可参考：MaNGOS脚本接口
　　通过使用不同的脚本DLL来替换share的这个DLL,可以让game��h��更强的AIScriptDev2 ��是一个这��L��库ScriptDev2 is a replacement for the Script Library that comes with MaNGOS( http://www.getmangos.com ) written in C++ and is compatible with Windows and Linux. It provides scripts for NPCs, Boss events, and Items currently. Once ScriptDev2 is compiled it is automatically run by MaNGOS on server startup.
　　
工程mangosd
　　mangos是世界服务器的管理器�Q�负责初始化工作和启动世界服务器各层的线�E�，�q�些工作主要是由�c�Master来实现具体是�Q?使用三个数据库对象WorldDatabase和CharacterDatabase和loginDatabase�Q�初始化三大数据库：World Database和Character Database和login Database�Q��ƈ为每个数据库的访问都启动一个DB delay threads具体的数据库操作功能都是由Mangos公共库shared来提�?nbsp;
　　调用sWorld.SetInitialWorldSettings�Q�对World�q�行初始化，包括加蝲所有的游戏数据和初始化各种更新定时器和邮�g定时器，�q�有些其他的初始化工作类World的成员函数SetInitialWorldSettings调用成员函数LoadConfigSettings解析mangosd.conf�Q�解析后内容攑օ�uint32 m_configs[CONFIG_VALUE_COUNT]�?nbsp;
　　加蝲的游戏数据有�Q?nbsp;
　　DBC数据
　　Objects数据
　　Spells数据
　　Pooling数据
　　Game Event数据
　　loot数据
　　技能数�?nbsp;
　　所有其他的游戏数据�Q�包括Waypoints和Trainers�{�等�{?nbsp;
　　脚本数据
　　其他的初始化工作�?
　　初始化MapManager�Q�启动Map System
　　初始化Battlegrounds�Q�启动BattleGround System
　　初始化DailyQuestResetTime
　　初始化sGameEventMgr�Q�Starting Game Event system
　　�c�Master启动WorldRunnable�Q�开始游戏逻辑Heartbeat for the World�Q�由Master创徏�Q��ƈ讄��U�程为最高优先��
　　�c�Master启动CliRunnable�Q�Command Line Interface handling thread�Q�由Master创徏CliRunnable�q�行时候会生成一个WorldDatabase�U�程�Q�在接收到输入后会调用sWorld.QueueCliCommand把Cmd攑օ�到World::cliCmdQueue�?nbsp;
　　mangosd的线�E��d��有（1+3+1+1+1+2 +1 =10�Q?0个线�E?�ȝ��E�Master
　　2个网�l�线�E�ReactorRunnable�Q�可配置数目�Q�（�|�络层）
　　一个World�U�程�Q�逻辑层）
　　三个DB�U�程�Q�数据层�Q?nbsp;
　　一个CLI�U�程�Q�输入层�Q�，�q�行时候会生成一个WorldDatabase�U�程
　　一个RA�U�程�Q�管理层�Q?nbsp;
　　一个freeze catcher �U�程�Q�可选）
　　工程g3dlite�Q�游戏逻辑层的底层�?nbsp;
　　工程framework�Q�系�l�框�?nbsp;
　　工程realm
　　负责登陆和选择游戏服务器，�q�行负蝲均衡用到了C++ Sockets Library�q�行��d��处理�Q�采用select I/O模型实现了Wow, Mangos��d��时的SRP6认证客户端作为它的client�q�接到realm server认证和选择了mangos server��断开而mangos server和realm server则不�q�行�q�接�Q�只是通过数据库交互数据：mangos server把自��q��状态和拥有的角色数攑օ�库中realm server会读取数据库中的�q�些信息来获知mangos server的状�?数据库realm的realmlist表保存了realm的列�?nbsp;
　　realm通过如下事�g处理函数来负责登陆和选择游戏服务�?nbsp;
　　const AuthHandler table[] =
　　{
　　{ AUTH_LOGON_CHALLENGE, STATUS_CONNECTED, &AuthSocket::_HandleLogonChallenge },
　　{ AUTH_LOGON_PROOF, STATUS_CONNECTED, &AuthSocket::_HandleLogonProof },
　　{ AUTH_RECONNECT_CHALLENGE, STATUS_CONNECTED, &AuthSocket::_HandleReconnectChallenge},
　　{ AUTH_RECONNECT_PROOF, STATUS_CONNECTED, &AuthSocket::_HandleReconnectProof },
　　{ REALM_LIST, STATUS_AUTHED, &AuthSocket::_HandleRealmList },
　　{ XFER_ACCEPT, STATUS_CONNECTED, &AuthSocket::_HandleXferAccept },
　　{ XFER_RESUME, STATUS_CONNECTED, &AuthSocket::_HandleXferResume },
　　{ XFER_CANCEL, STATUS_CONNECTED, &AuthSocket::_HandleXferCancel }
　　}; ��d��处理�Q?nbsp;
　　user��d��到realm server�q�行�w�䆾认证�Q��ƈ选择��d��上哪个mangos serveruser��d��到mangos server后，��不再和realm server交互
　　参考： Wow 服务器解�?nbsp;
　　工程game
　　game�Q�是Mangos的核心代码，�|�络层和逻辑层代�?采用了ACE反应�?Reactor)模式�Q?nbsp;
　　�|�络层： WorldSocket �Q�负责网�l�IO,而类WorldSession负责逻辑处理WorldSocket和WorldSession分别在独立的�U�程ReactorRunnable和WorldRunnable中运行，使用WorldSession中的消息队列_recvQueue来进行数据缓冲在WorldSocket接收到网咯输入后�Q�会调用m_Session->QueuePacket (new_pct);把网�l�包攑օ�WorldSession的_recvQueue所以，可以看到WorldSocket 是Mangos game的网�l�层�Q�而WorldSession是逻辑处理层WorldSocketMgr是网�l�层的一个管理器�Q�它负责指派WorldSocket归哪个ReactorRunnable��理�Q�Mangos可创建多个ReactorRunnable�Q�缺省是2个）
　　WorldSocketMgr�Q�Manages all sockets connected to peers and network threads�Q�管理所有的�q�接WorldSocketWorldSocketMgr的WorldSocketMgr::StartNetwork�?085�Q�缺省）端口�q�行侦听逻辑处理的��@环是在World::Update中��@环处理包括：
　　��h��更新定时�?nbsp;
　　��h��游戏定时器和处理游戏关闭
　　处理日常��d��
　　处理拍卖
　　��h��SessionsWorld::UpdateSessions会调用所有WorldSession的WorldSession::Update在WorldSession::Update中进行逻辑处理
　　处理天气
　　��h��uptime table
　　��h��Objects�Q�包括maps�Q�transport�Q�creatures�Q�，�Q�，
　　��h��所有running battlegrounds
　　��h��SqlResultQueue, 逻辑层和数据层是通过Queue来进行异步操作的�Q�用了AsyncPQuery和SqlResultQueue�Q?nbsp;
　　处理��怽��U�除
　　处理游戏事�g
　　处理 Move all creatures with "delayed move" and remove and delete all objects with "delayed remove"
　　处理InstanceSaveManager的刷�?nbsp;
　　调用World::ProcessCliCommands�Q�处理CLI从cliCmdQueue取得cmd�q�行解析执行所有有效的Cmd�Q�都可以在ChatHandler::getCommandTable中找�?nbsp;
　　�c�WorldSession�Q?�c�WorldSession负责逻辑处理
　　void WorldSession::SendPacket(WorldPacket const* packet) 负责发包�l�客��L��Q�直接发包，没有输出�~�冲队列
　　在WorldSession::Update中进行逻辑处理World::UpdateSessions会调用所有WorldSession的WorldSession::Update
　　执行语句OpcodeHandler& opHandle = opcodeTable[packet->GetOpcode()];得到opHandle
　　�Ҏ��得到的opHandle�Q�执�?this->opHandle.handler)(packet);
　　WorldSession::HandlePlayerLogin处理玩家登陆游戏
　　构徏Player
　　Player::LoadFromDB从数据库中加载玩家数据在Player::LoadFromDB中会调用SetMap(MapManager::Instance().CreateMap(GetMapId() , this));加蝲当前player所在的map
　　Player::SetPosition在Player�q�动的时候，改变位置�Q�保存处理夸�?nbsp;
　　�c�Map实现了一个state machine�Q�采用state pattern�l�织了Gid�?个state object�Q�InvalidState�Q�ActiveState�Q�IdleState�Q�RemovalState
　　game中的��理器有�Q?ObjectMgr
　　mMangosStringLocaleMap 兌��到mangos_string table
　　m_scriptNames 兌��到tables: creature_template;gameobject_template;item_templat e;areatrigger_scripts;instance_template
　　mCreatureLocaleMap 兌��到locales_creature table
　　mGameObjectLocaleMap兌��到locales_gameobject table
　　mItemLocaleMap兌��到locales_item table
　　mQuestLocaleMap –> locales_quest
　　mNpcTextLocaleMap –> locales_npc_text
　　mPageTextLocaleMap –> locales_page_text
　　mGossipMenuItemsLocaleMap –> locales_gossip_menu_option
　　mPointOfInterestLocaleMap –> locales_points_of_interest
　　…
　　对象�c�d��?nbsp;
　　对象的类层次如下�Q�所有的Object都由ObjectMgr�q�行��理ObjectMgr以GUID方式�Q�管理了characters�Q�creature�Q�item_instance�Q�gameobject�Q�auctionhouse�Q�mail�Q�item_text�Q�corpse�Q�arena_team�Q�character_equipmentsets
　　
　　
　　
　　
　　
Player状�?nbsp;
　　/// Player state
　　enum SessionStatus
　　{
　　STATUS_AUTHED = 0, ///< Player authenticated (_player==NULL, m_playerRecentlyLogout = false or will be reset before handler call, m_GUID have garbage)
　　STATUS_LOGGEDIN, ///< Player in game (_player!=NULL, m_GUID == _player->GetGUID(), inWorld())
　　STATUS_TRANSFER, ///< Player transferring to another map (_player!=NULL, m_GUID == _player->GetGUID(), !inWorld())
　　STATUS_LOGGEDIN_OR_RECENTLY_LOGGOUT, ///< _player!= NULL or _player==NULL && m_playerRecentlyLogout, m_GUID store last _player guid)
　　STATUS_NEVER ///< Opcode not accepted from client (deprecated or server side only)
　　};
　　生物状�?nbsp;
　　enum DeathState
　　{
　　ALIVE = 0,
　　JUST_DIED = 1,
　　CORPSE = 2,
　　DEAD = 3,
　　JUST_ALIVED = 4,
　　DEAD_FALLING= 5
　　};
　　玩家登陆
　　服务器端在连接打开后，会发SMSG_AUTH_CHALLENGE到客��L��客户端从服务器端发送回来的�U�子�?SRP6 数据中��生随机种子，生成 SHA1 字符�Ԍ��用这些数据生�?CMSG_AUITH_SESSION 数据包，发送给服务端这个过�E�是没有�l�过加密�?nbsp;
　　
　　客户端发送SMSG_AUTH_SESSION到服务器
　　服务器处理SMSG_AUTH_SESSION
　　服务器发送SMSG_AUTH_RESPONSE�l�客��L��
　　服务器发送SMSG_ADDON_INFO�l�客��L��
　　服务器发送SMSG_CLIENTCACHE_VERSION�l�客��L��
　　服务器发送SMSG_TUTORIAL_FLAGS�l�客��L��
　　packet�l�构 SMSG_AUTH_SESSION 是client packet有一个头部（ClientPktHeader�Q�，后面是数据块
　　SMSG_AUTH_RESPONSE 是server packet有一个头部（ServicePktHeader�Q�，后面是数据块
　　SMSG_AUTH_RESPONSE 的包�l�织
　　SMSG_AUTH_RESPONSE 的opcode�?1EE�Q�ByteBuffer大小�? + 4 + 1 + 4 + 1=11一个SMSG_AUTH_RESPONSE 的数据如下：在构造了SMSG_AUTH_RESPONSE packet后，WorldSocket::SendPacket会根据SMSG_AUTH_RESPONSE packet构造出一个ServerPktHeader�Q��ƈ对ServerPktHeader中的数据header�q�行加密发送加密采用m_Crypt.EncryptSend ((uint8)header.header, header.getHeaderLength()); WorldSocket::handle_input_header会对从客��L��接收来的数据�q�行解密�Q�解密采用m_Crypt.DecryptRecv ((uint8) m_Header.rd_ptr (), sizeof (ClientPktHeader));
　　角色枚�D 玩家��M��服务器后�Q�从客户端发送SMSG_CHAR_ENUM到服务器
　　在服务器�?nbsp;
　　�Ҏ��{ "CMSG_CHAR_ENUM", STATUS_AUTHED, &WorldSession::HandleCharEnumOpcode }�Q�服务器会调用WorldSession::HandleCharEnumOpcode
　　WorldSession::HandleCharEnumOpcode会调用CharacterDatabase.AsyncPQuery�Q�进行异步查询后�Q�调用CharacterHandler::HandleCharEnumCallback
　　CharacterHandler::HandleCharEnumCallback会回头调用session->HandleCharEnum(result);
　　WorldSession::HandleCharEnum�Ҏ��characters数据库的查询�l�果�Q�调用Player::BuildEnumData�Q�加载角色数据，构造SMSG_CHAR_ENUM�q�回包，然后发送回客户�?nbsp;
　　
　　角色创徏
　　
　　角色的初始化装备在CharStartOutfit.dbc
　　角色的创建和选择的设�|�都�?ChrRaces.dbc
　　角色的创建属性都在Playercreateinfo�Q�包括出生地和出生属�?nbsp;
　　playercreateinfo_item表是创徏一个新人物�Ӟ��人物默认带的所有Item的表
　　playercreateinfo_spell表是创徏一个新人物�Ӟ��人物默认带的所有Spell的表
角色删除
　　

点点滴滴 2016-12-16 11:28 发表评论

点点滴滴 — Fri, 16 Dec 2016 03:16:00 GMT

# MaNGOS Configuration file 服务器配�|�文件中文说�?br style="box-sizing: border-box;" />ConfVersion=2007071001
# RealmID must match the realmlist (国度ID 必牒�?攘斜砝锩娴南�?
RealmID = 1

# 0 NORMAL 1 PVP 4 NORMAL 6 RP 8 RPPVP(服务器类�?
GameType = 1

# 扩展柚每 ?# 0 不检查扩展地�?不允许创建新�U�族,忽略账号的扩展设�|?
# 默认: 1 (如果客户端支持扩展且账号拥有扩展权限,卛_��怋�用新�U�族及访问新地图.)
Expansion = 1

#==================================服务端添加的参数===========================================================================
#世界聊天消费(默认�?G/��?
sjxf=10000

#初始人物金币�Q�以分�ؓ单位.
# 默认: 8
mymoney = 1000000

# 自动公告旉��间隔 1=1�U?br style="box-sizing: border-box;" />AutoBroadcastInterval=10

#初始怪物��怽�停留旉��
#单位/�U?nbsp;
# 默认: 60
MyCropseDelay = 60

#人物复活虚弱旉��
#默认: 1000
Playerdietime = 1000

#初始出生人物�{��
# 默认: 1
LevelFirst = 1

#加血技能治疗倍数
aurahealing = 5

#法术技能伤宛_��数
tmpDamage = 5

#物理技能伤宛_��数(数字别改的太大了)
pdaDamage = 2

#猎�h闪避率设�|?数字��大闪避率越�?

Rate.Hunter_Max.Dodge=31.4

#盗贼闪避率设�|?数字��大闪避率越�?

Rate.Roguer_Max.Dodge=19.5

#其他职业闪避率设�|?数字��大闪避率越�?

Rate.Else_Max.Dodge=27

#==================================服务端添加的参数===========================================================================
# 数据目录讄��?br style="box-sizing: border-box;" /># 重要说明�Q�数据目录需要放在引号里面，因�ؓ字符串可能包含空�?br style="box-sizing: border-box;" /># DataDir = "@MANGOSD_DATA@" //�q�个是默认目�?br style="box-sizing: border-box;" />DataDir = "./"

# Logs directory setting.
# Important: Logs dir must exists, or all logs be disable
# Default: "" - no log directory prefix, if used log names isn't absolute path then logs will be stored in current directory for run program.

LogsDir = ""

# 世界服务器的数据库连接设�|��?br style="box-sizing: border-box;" /># 格式�Q�主机地址(域名或IP�Q?端口;用户�?密码;数据库名�U?br style="box-sizing: border-box;" />#           .;somenumber;username;password;database - use named pipes at Windows
#                 Named pipes: mySQL required adding "enable-named-pipe" to [mysqld] section my.ini
#           .;/path/to/unix_socket;username;password;database - use Unix sockets at Unix/Linux
#                 Unix sockets: experimental, not tested
LoginDatabaseInfo = "127.0.0.1;3306;root;netspace;realmd"
WorldDatabaseInfo = "127.0.0.1;3306;root;netspace;mangos"

# 讄��最高ping数据库的旉��间隔(分钟)
MaxPingTime = 30

# DBC 语言讄��
#8 ��p��
#4 韩语
#3 法语
#3 徯��
#4 中文
#5 台湾�J�体
#6 西班牙语
#7 俄语
#8 未知
# 8 = Unknown
# 9 = Unknown
# 10 = Unknown
# 11 = Unknown
# 12 = Unknown
# 13 = Unknown
# 14 = Unknown
# 15 = Unknown
# 255 = 自动��?(默认)
DBC.Locale = 255

# 启用GM命��o记录-所有的SQL代码都将被记录在日记文�g�?br style="box-sizing: border-box;" /># All commands are written to a file: YYYY-MM-DD_logSQL.sql
# If a new day starts (00:00:00) then a new file is created - the old
# file will not be deleted.
# 0 - 不记�?br style="box-sizing: border-box;" /># 1 - 记录
LogSQL = 1

# 服务器控制台记录昄��的��?br style="box-sizing: border-box;" /># 0 = 最��? 1 = 基础和错�? 2 = 详细; 3 = 完全或侦�?br style="box-sizing: border-box;" /># 默认: 0
# 推荐: 1
LogLevel = 0

# 记录文�g 的名�?br style="box-sizing: border-box;" /># 文�g名�ؓ�I?则不创徏记录文�g,�? LogFile =
# 默认: ""
LogFile = "Server.log"

# Logfile with timestamp of server start in name
# Default: 0 - no timestamp in name
#           1 - add timestamp in name in form Logname_YYYY-MM-DD_HH-MM-SS.Ext for Logname.Ext

LogTimestamp = 0

# 记录文�g的记录��?br style="box-sizing: border-box;" /># 0 = 最��? 1 = 基础和错�? 2 = 详细; 3 = 完全或侦�?br style="box-sizing: border-box;" /># 默认: 0
LogFileLevel = 0

# Log filters
# 0 (default) - include in log if log level permit, 1 - not include with any log level
LogFilter_TransportMoves = 0
LogFilter_CreatureMoves = 0
LogFilter_VisibilityChanges = 0

# 控制��C��息的颜色 (格式: "正常颜色详情颜色 debug颜色错误颜色)
# 颜色: 0-黑色, 1-�U? 2-�l? 3-��? 4-�? 5-品红, 6-青绿, 7-灰色,
# 8-�? 9-淡红, 10-淡绿, 11-淡蓝, 12-淡品�U? 13-淡青�l? 14-白色
# 默认: "" 无颜�?白色)
# 例如: "13 7 11 9"
LogColors = "13 7 11 9"

# Packet logging file for the worldserver.
# Default: ""
WorldLogFile = "world.log"

# 记录数据库错误的文�g�?br style="box-sizing: border-box;" /># 默认: ""
DBErrorLogFile = "DBErrors.log"

# 记录GM命��o使用情况�?记录文�g�?br style="box-sizing: border-box;" /># 默认: "" (��止) 允许�?例如: "GMcommand.log"
GmLogFile = ""

# Log file of RA commands, "" for disable
# Default: "Ra.log"
RaLogFile = ""

# 在多�U�程�pȝ�� 使用�U�程MASK(只在Windows�pȝ��下��?
# 默认: 0 (操作�pȝ��来选择)
# 举例: 数字
UseProcessors = 80

# �q�程优先权设�|?只在Windows�pȝ��下��?
# 0 (正常优先�?
# 默认: 1 (高优�?
ProcessPriority = 1

#发送到客户端的更新数据包的压羃�U�别(1�?)
# 默认: 1 (速度�?不压�~?
# 9 (最好的压羃)
Compression = 1

# 除GM之外游戏最大在�U�玩家数限制
# 默认: 100
PlayerLimit = 100

# 玩家获得�l�验能升到的最高等�U?必须�?1 �?255).
# 不徏议修�?��用默认的 60 ��过60 可能影响游戏�q��
# 默认: 60
MaxPlayerLevel = 70

# 天气�pȝ��开�?br style="box-sizing: border-box;" /># 默认: 1 (开)
#           0 (�?
ActivateWeather = 1

# 是否忽略�q�入副本的等�U�需�?br style="box-sizing: border-box;" />#       1 (true)
# 默认: 0 (�?
IgnoreATLevelRequirement = 0

# 玩家最多可以学�?商业技�?br style="box-sizing: border-box;" /># 默认: 2
# 最�? 9
MaxPrimaryTradeSkill = 2

# 建立公会所需的最��玩家签名个�?(0..9).
# 默认: 9
MinPetitionSigns = 9

# ��队成员在生物死�?获得�l�验�?最大距��?同怪物的距��?
# 默认: 74
MaxGroupXPDistance = 74

# ��队成员在生物死�?获得�l�验�?最大等�U�差(同怪物的等�U?
# 默认: 10
MaxGroupXPLevelDiff = 10

# 是否�q�行�?个帐�?建立�?个不同阵营的角色 GM号�ؓ始终�?允许
# 默认: 0 (不允�?
# 1 (允许)
AllowTwoSide.Accounts = 0

# 是否允许不同阵营间的聊天频道聊天 �l�队交易
# 默认: 0 (不允�?
#     1 (允许)
AllowTwoSide.Interaction.Chat = 0
AllowTwoSide.Interaction.Channel = 0
AllowTwoSide.Interaction.Group = 0
AllowTwoSide.Interaction.Guild = 0
AllowTwoSide.Interaction.Trade = 0

# 是否�?在线玩家列表里显�C�敌寚w��营玩�?br style="box-sizing: border-box;" /># 默认: 0 (不允�?
# 1 (允许)
AllowTwoSide.WhoList = 0

# 防刷屏开�?多少条违规信息激�z�M��?br style="box-sizing: border-box;" />#           0 (为关闭防刷屏)
# 默认: 10
ChatFlood.MessageCount = 10

# 防刷屏开�?多少�U�间隔开始计��ؓ�q�规信息
# 默认: 1 (�U?
ChatFlood.MessageDelay = 1

# 防刷屏开�?��言旉��.
# 默认: 10 (�U?
ChatFlood.MuteTime = 10

# GM默认是否接受玩家的悄悄话.
# 默认: 0 (false)
#     1 (true)
GM.WhisperingTo = 0

# 当GM讄��为可见时是否在玩家列表显�C�GM.
# 默认: 0 (false)
#     1 (true)
GM.InGMList = 0

# 是否昄��GM名单 (if visible).
# 默认: 0 (false)
#           1 (true)
GM.InWhoList = 0

# GM模式在登陆时状�?br style="box-sizing: border-box;" />#           0 (��L��?
#           1 (��L��开)
# 默认: 2 (上次��d��时状�?
GM.LoginState = 2

# 如果打开则在GM LOG里记录GM的交易和交易信息
#           0 (不记�?
# 默认: 1 (记录)
GM.LogTrade = 1

# 团队可见模式
# 默认: 0-标准讄��Q�只有同一个团队的队友才可�?00%侦测隐�Ş玩家
#    1-只有同一个小队的队友才可�?00%侦测隐�Ş玩家
#    2-同一阵营的队友可�?00%侦测隐�Ş玩家
Visibility.GroupMode = 0

# 不同的游戏物体之间的可见�?nbsp;
# 最大设�|? ~ 166
# 最��设�|�以物体为准
# 默认: 66 (单元)
#
# Min limit is max aggro radius (45) * Rate.Creature.Aggro
Visibility.Distance.Creature    = 66
Visibility.Distance.Player       = 66

# gameobject, dynobject, bodies, corpses, bones
# Min limit is iteraction distance (5)
Visibility.Distance.Object       = 66

# visible distance for player in flight
# Min limit is 0 (not show any objects)
Visibility.Distance.InFlight    = 66

# Visibility grey distance for creatures/players (fast changing obects)
#     addition to appropriate object type Visibility.Distance.* use in case visibility removing to object (except corpse around distences)
#     If ?is distance and G is grey distance then object make visible if distance to it <= D but make non visible if distance > D+G
# Default: 1 yard
Visibility.Distance.Grey.Unit = 1

# Visibility grey distance for dynobjects/gameobjects/corpses/creature bodies
#
# Default: 10 yards
Visibility.Distance.Grey.Object = 10

# 如果邮寄物品延时多久收到�Q�？
# 默认: 3600 �U?(1 hour)
MailDeliveryDelay = 3600

# 每日消息。当玩家�q�入游戏的时候显�C�在聊天�H�口的信息�?br style="box-sizing: border-box;" />Motd = "Welcome to the Massive Network Game Object Server."

# Health and power regeneration and rage income from damage.
Rate.Health = 1;
Rate.Mana = 1;
Rate.Rage.Income = 1;
Rate.Rage.Loss = 1;
Rate.Focus = 1;

# 物品的掉率倍数
#poor,白色�Q?br style="box-sizing: border-box;" />#common,普通；
#uncommon,�|�见�?
#rare,贵重的；
#Epic,史诗;
#Legendary,传说;
#uest,��d��>
# 默认: 1
# Rate.Drop.Items = 1

Rate.Drop.Items.Quality.Poor = 1
Rate.Drop.Items.Quality.Common = 1
Rate.Drop.Items.Quality.Uncommon = 1
Rate.Drop.Items.Quality.Rare = 1
Rate.Drop.Items.Quality.Epic = 1
Rate.Drop.Items.Quality.Legendary = 1
Rate.Drop.Items.Quest = 1
Rate.Drop.Money = 1

# 杀�?��d��,探烦地图获得�l�验乘以的倍数
# 默认: 1
Rate.XP.Kill     = 20
Rate.XP.Quest = 30
Rate.XP.Explore = 10

# 普�?�_�英,�E�有精�?BOSS,�E�有普通�?的伤�?乘以的倍数
# 例如: 1.4 ��是增加0.4倍攻��M��?br style="box-sizing: border-box;" />Rate.Creature.Normal.Damage = 1
Rate.Creature.Elite.Elite.Damage = 1
Rate.Creature.Elite.RAREELITE.Damage = 1
Rate.Creature.Elite.WORLDBOSS.Damage = 1
Rate.Creature.Elite.RARE.Damage = 1

# 普�?�_�英,�E�有精�?BOSS,�E�有普通�?的血�?乘以的倍数
# 例如: 1.4 ��是增加0.4倍攻击血�?br style="box-sizing: border-box;" />Rate.Creature.Normal.HP = 1
Rate.Creature.Elite.Elite.HP = 1
Rate.Creature.Elite.RAREELITE.HP = 1
Rate.Creature.Elite.WORLDBOSS.HP = 1
Rate.Creature.Elite.RARE.HP = 1

#仇恨�p�L��Q�默�?.1f�Q�即有超�q�第一仇恨者造成伤害110%者就转变��d��对象�?br style="box-sizing: border-box;" />#注意�Q�必��ȝ��到��数点后1�?br style="box-sizing: border-box;" /># 默认: 1.1f
AggroThreat = 1.1f

# �_�֊�条增长倍数 (1 - normal, 2 - double rate, 0.5 - half rate, etc) from standard values
# 游戏�?br style="box-sizing: border-box;" />Rate.Rest.InGame = 1
# 在旅馆下�U�时
Rate.Rest.Offline.InTavernOrCity = 1
# 在野外下�U�时
Rate.Rest.Offline.InWilderness = 1

# �I�Z��跌落伤害倍数
Rate.Damage.Fall = 1

# 拍卖倍数
# Rate.Auction.Time (拍卖旉��倍率),Rate.Auction.Deposit(拍卖押金),Rate.Auction.Cut(拍卖上限)
Rate.Auction.Time = 1
Rate.Auction.Deposit = 1
Rate.Auction.Cut = 1

# 矿物倍数
#Rate.Mining.Next (采矿的几率倍数),Rate.Mining.Amount (产生矿最大最��的倍数)
Rate.Mining.Amount = 1
Rate.Mining.Next = 1

# 天赋点的升��倍率
# 默认: 1
Rate.Talent = 1

# 保存��h��旉�� 当生物死当物体被打开或��?br style="box-sizing: border-box;" />#           0 (保存�?物体的刷新时间在�|�格卸蝲的时�?
# 默认: 1 (不在�|�格卸蝲的时候保存�h/物体的刷新时�?
SaveRespawnTimeImmediately = 1

# 技能熟�l�度提升几率(0..100)
# 默认: 100-75-25-0
SkillChance.Orange = 100
SkillChance.Yellow = 75
SkillChance.Green = 25
SkillChance.Grey = 0

# 怪物自动��d��的范围乘以的倍数或�?关闭自动��d��
# 0 - 关闭(0%)
# 默认: 1 - 乘以100%
# 1.5 - 乘以150%
Rate.Creature.Aggro = 1

# 控制台开�?br style="box-sizing: border-box;" />#           0 - �?br style="box-sizing: border-box;" /># 默认: 1 - 开
Console.Enable = 1

# �q�程控制台开�?br style="box-sizing: border-box;" /># 默认: 0 - �?br style="box-sizing: border-box;" />#           1 - 开
Ra.Enable = 0

# 默认�q�程控制IP地址,0.0.0.0为所有IP皆可.
Ra.IP = 0.0.0.0

# 默认�q�程控制台端�?br style="box-sizing: border-box;" />Ra.Port = 3443

# �q�程控制台连接到服务器所需要的GM�{��Q�默认�ؓ3�Q�管理员�Q?br style="box-sizing: border-box;" />Ra.MinLevel = 3

# �t�出用户�Q�如果他输入了错误的密码 �Q�仅限远�E�控制台�Q?br style="box-sizing: border-box;" />Ra.Secure = 1

# 最大速度限制倍率
# 默认: 2 如果�?则关闭检查加�?br style="box-sizing: border-box;" />MaxOverspeedPings = 2

# 卸蝲Grids (如果里的内存够大,可以��用,提高玩家�W�二�ơ经�q�新Grids时候的速度)
# P.S: Grids��是地图上刷出来的东�?玩家�l�过一个地�?��׃��加蝲该地方的环境,��d��的时�?��卸载该地方的环�?br style="box-sizing: border-box;" /># 默认: 1 ( 卸蝲 grids) 0 ( 不卸�?grids)
GridUnload = 1;

# 以下所有的旉��讄��都以毫秒为单位�?br style="box-sizing: border-box;" /># 默认端口选择旉��
SocketSelectTime = 10000

# 默认地图�|�格清理延迟
GridCleanUpDelay = 300000

# 默认地图更新间隔
MapUpdateInterval = 100
# 默认天气更新间隔
ChangeWeatherInterval = 600000

# 默认玩家数据保存间隔
PlayerSaveInterval = 900000
# 默认世界服务器端�?mangosd.exe 的端口）
WorldServerPort = 8085

# 在mangos启动完毕后蜂鸣一�?通常只在Unix nux�pȝ��下工�?
# 默认: 1
BeepAtStart = 1

# 打开/关闭 VMmap 对视�U�和高度的推��支�?br style="box-sizing: border-box;" /># Default: 1 (true)
#       : 0 (false)
vmap.enableLOS = 1
vmap.enableHeight = 1

# 不��?VMap功能的地图ID
# 地图ID之间�?','分割
# 如果有多个地图ID使用 "号包�?br style="box-sizing: border-box;" />#vmap.ignoreMapIds = "369,0,1,530"
#DeeprunTram 没有包含在地图中
vmap.ignoreMapIds = "369"

# 不进行视�U�推��的技�?br style="box-sizing: border-box;" /># 技能之间��?','分割
vmap.ignoreSpellIds = "7720"

点点滴滴 2016-12-16 11:16 发表评论

点点滴滴 — Tue, 08 Nov 2016 13:18:00 GMT

The purpose of NMGen is to generate navigation meshes from arbitrary source geometry. Features fall into two categories: Core and 'standard build'.
NMGen用于��Q意网��D�{化�ؓ一个或多个NavMesh�?其所有功能都包含于两个目录： Core(核心) �?'standard build'(普�?;

The core features are located in the org.critterai.nmgen namespace and involve creating simplified polygon mesh data from detailed triangle-based source geometry. You can code your own build process from scratch using these features, but it will require a significant amount of work and detailed knowlege of all aspects of the process.
核心功能位于nmgen命名�I�间下，与将复杂的三角�Şmesh转化为简化的多边形mesh有关。你可以通过代码��d��重新规划生成�q�程(1)�Q�不�q�这里有很多事情要做�Q�而且你需要了解生成过�E�中各个斚w��的实现细�?2)�?/span>

The standard build process implements a flexible, extendable build process suitable for use at design time. It takes care of many of the mundane details for you. Its features are implemented in the following namespaces:
Common extentions: org.critterai.nmbuild
Unity extensions: org.critterai.nmbuild.u3d.editor
普通生成流�E��ؓ了满��编辑期的需要，被设计成可变的、可扩展的结构。它已经��Z��处理好了很多�l�枝末节的事�?3)。普通功能位于以下的命名�I�间中：
通用扩展(3): nmbuild
Unity扩展: nmbuild.u3d.editor

The standard build process has three main steps which will be covered in detail throughout the rest of this section.
Compile the input.
The NMGen Build. (Produces the polygon meshes.)
Create the navigation mesh.
普通生成流�E�有如下三个主要步骤�Q�稍后的章节会对�q�三个步骤进行详�l�的介绍�?/span>
�~�译数据�?
调用NMGen的生成功�?生成多边形网�?.
生成 Navigation Mesh.(��D��|�格)

Note Note:
CAINav uses the OpenGL coordinate system.

注意�Q?/span>
CAINav使用OpenGL坐标�pȝ��.(XYZ,左右手什么的);

(1)生成�q�程有哪些？
(2)哪些斚w��的细节需要了解？
(3)相对于recast的扩�?cai是基于recast的功能基��而实现的;

快速扫�?/span>
1、A* Path Finding是一个图最短�\径搜索算法，只要数据源支�?遍历��d��"的操作，��可以应用A*;
2、Ploygen Mesh 是凸多边形网��|��因�ؓ凸多边�Ş内�Q意两点可以直�?-在满��x��定的倾斜�?slope limit)和高度差(step height)的情况下�?/span>
3、如果有地�Ş的Triangle Mesh,其实已经可以��Z��它进行A*了，因�ؓ三角形也是凸多边形。大费周章的使用Nav Mesh是�ؓ�?、大�q�简化图的复杂度�Q�将不必要的信息�q�行合�ƈ�?、记录一些额外的信息�Q�比�?xxx xxx�?/span>

点点滴滴 2016-11-08 21:18 发表评论

点点滴滴 — Tue, 08 Nov 2016 13:17:00 GMT

The crowd manager is the big beast of the navigation components. It not only handles a lot of the path management for you, but also local steering and dynamic avoidance between navigation clients. I.e. It can keep your agents from running into each other.
【CrowdManager】类是十分庞杂的一个类。它不仅��Z��处理了非常多的�\径管理相关的事情�Q�同时也处理一些局部�{向和避开其它寻�\代理对象。也��是��_��他可以让所有的代理对象不会�怺��I�插�?br />

Core Class: CrowdManager
核心�c�：CrowdManager

The NavmeshQuery and PathCorridor classes provide perfectly good, easy to use path planning features. But in the end they only give you points that your navigation client should be moving toward. When it comes to deciding things like client velocity and steering to avoid other clients, that is up to you to implement. Unless, of course, you decide to use the crowd manager.
NavmeshQuery和PathCorridor�q�两个类已经很不错了�Q�用来做路径规划也��够简单。但是说到底它们只是�l�了你一堆指��D��色运动的路点。当你决定实��C��些角色之间不发生��撞的特性时�Q�只能你自己实现了。除非，当然�Q�你军_��使用CrowdManager�?br />

Basically, you add an navigation client (agent) to the crowd manager, providing various configuration settings such as maximum speed and acceleration. You also provide a local target to more toward. The crowd manager then provides, with every update, the new agent position and velocity for the frame. The movement will be constrained to the navigation mesh, and steering will be applied to ensure agents managed by the crowd manager do not collide with each other.
基本上来�Ԍ��你可以往CrowdManager��d��一个角�Ԍ��同时提供一些配�|�数据，例如最大速度和加速度。你也可以提供一个局部的目标(让角色自�ȝ��U�d��q�去(1))。然后CrowdManager会在每��更新的时候设�|�角色的最��C��|�和速度。运动会被约束在Navmesh内，CrowdManager会让角色在需要的时候进行�{向，以确保不会相互碰�?br />

This is very powerful feature set. But it comes with limitations.
The biggest limitation is that you must give control of the agent's position and velocity completely over to the crowd manager. You can update things like maximum speed and acceleration. But in order for the crowd manager to do its thing, it can't allow you to constantly be giving it overrides to position and velocity. So you give up direct control of the agent's movement. It belongs to the crowd manager.
The second biggest limitation revolves around the fact that the crowd manager deals with local planning. The agent's target should never be more than 256 polygons aways from its current position. If it is, you risk your agent failing to reach its target. So you may still need to do long distance planning and provide the crowd manager with intermediate targets.

�q�是一个非常强大的�Ҏ��集。但是它伴随着一些限制�?br />最大的限制在于你必��d��角色的位�|�和速度完全交给CrowdManager来控制。你可以更新�c�M��最大速度和加速度之类的参数。但是�ؓ了让CrowdManager能正常工作，你不能经常的改变角色的位�|�和速度。因此你需要放弃管理角色运动。这个工作现在属于CrowdManager�?br />

Other significant limitations:
All agents using the crowd manager use the same NavmeshQueryFilter.
Crowd management is relatively expensive. The maximum agents under crowd management at any one time is around 20.

其他明显的限�?br />所有托��的角色都��用同��L��查询�q��o�?br />人群��理的开销相对较大。可以管理的人群的个体数量最大约�?0�?1)�?br />

The Sample Pack includes a Crowd Manager Demo that lets you see the manager in action.

(1)需要实�?
(1)�q�个数量是一个�h为的限制�Q�可以通过修改代码�H�破此限制�?/div>

点点滴滴 2016-11-08 21:17 发表评论

点点滴滴 — Tue, 08 Nov 2016 13:16:00 GMT

The Path Corridor
��译�Q�kun 2014.12.4

The path corridor provides a way of moving along a navigation path without worrying about the minutiae of managing the path.
廊道提供了一�U�沿指定��D��路径�q�行�U�d��Q�而不必担心管理��用�\径数据时的细节问题�?/span>

Core Class: PathCorridor
核心�c�：PathCorridor

In the simplest scenario, a path is a list of waypoints from a starting point to an end point. The waypoints form a connected set of line segments along which a navigation client moves. But

navigation is much more complex in the real world. There are locomotion limitations, local steering restrictions, dynamic obstacle avoidance, and good old floating point errors. All of these

issues can make management of a path difficult.
在最��单的情景里，一个�\径是一�l�从开始点到结束点的�\点列表。如果能�_��的按照��用此��D��数据�q�动�Q�角色的轨迹会是一�l�相互连接的�U�段。但是在真实环境下进行导航比�q�个要复杂的多。你需要考虑角色的运

动能力的局限�?1)、局部�{向限制、避开动态障��物、以及一些常见的��点数错误。所有这些情况都会让��理一个�\径的使用变得困难�?/span>

Navigation based on a polygon mesh provides a different abstraction than just a list of waypoints. The path returned by the NavmeshQuery class is a list of polygons. Technically, a client can

move freely anywhere within this corridor of polygons. If a client strays outside the corridor, then the corridor can be patched up using local searches rather than full path replanning.
在一个多边�Ş�|�格上进行导航比在一堆�\点上�q�行��D��要更加抽象一些。NavmeshQuery�q�回的Path是一�l�多边�Ş。技术上�Ԍ��一个角色可以在�q�个廊道上的��L��多边形内自由的移动。如果一个角色跑��Z��q�个廊道的范

��_��廊道的范围可以��用局部搜索进行扩大，而不是重新规划整条�\径�?/span>

The path corridor is loaded with a path, a start point, and a target point. It is then used to move the navigation client through the corridor. It handles path straightening, constraining the

client to the navigation mesh, and adjusting the corridor due to inaccurate client locomotion.
廊道需要加载一个Path、一个�v始点、一个目标点。然后用于角色在�q�个廊道内移动。它处理路径的矫正、确保角色不会跑出Navmesh、以及当角色�U�d��出预期时修正廊道信息�?/span>

The PathCorridor API is well documented. The only thing worth repeating here is a warning: You can't just initialize a corridor with a path and forget long distance path planning. Since the

path corridor class uses local searches to maintain the corridor, attempting to apply large delta movement to the corridor's position or target can result in a malformed corridor. Details are

in the API documentation.
PathCorridor API已经有详�l�的文档说明了。在�q�里只有一点值得提一下：你不能只创徏一个廊道然后一切都交给它去做，而不�q�行长�\径规划。虽然廊道��用了局部搜索来�l�持廊道完整性，不过如果在廊道里产生一

个大的运动距��，或者目标点��d��很远�Q�会产生一个畸形的廊道(1)。更多的�l�节可以参考相关API文档�?/span>

(1)加速、减速、惯性之�cȝ��q�动参数.
(2)啥意�?

点点滴滴 2016-11-08 21:16 发表评论

点点滴滴 — Tue, 08 Nov 2016 13:15:00 GMT

��译�Q�kun 2014.12.4

The navigation mesh query is the most important class to understand since most navigation clients will interact with the query rather than the navigation mesh itself. The mesh contains the data, but the query provides almost all of the features necessary for pathfinding.
用户和navigation mesh query(Navmesh查询�?打交道的�ơ数比Navmes本��n多的多。网格包含数据，但是查询器提供了几乎全部的寻路特性�?/p>

Core Class: NavmeshQuery
核心�c�：NavmeshQuery

Query features fall into two general categories: Pathfinding and local search.
查询器的�Ҏ��包括两个大的方面：寻�\和局部搜索�?/span>

Pathfinding involves standard A* and Dijkstra searches that find the best path(s) between two points. Paths are made up of a list polygon references that represent a polygon corridor from the start to the end position. Path straightening is used to convert the path into a list of waypoints. (I.e. String pulling.)
寻�\使用标准的A*和Dijkstra��法�Q�用于找��Z��点之间最好的路径(可能不止一�?。Path(路径)是由一�l�Polygon的引�?1)�l�成数据�Q�从开始点到结束点。�\径矫正是��一个Path数据转�ؓ一�l��\�Ҏ��?即String pulling(�l�_��拉直))(2)�?/span>

The local search features offer various methods for locating polygons and points on polygons, and for querying the local environment. I.e. Raycasting, finding the distance to the nearest wall, etc.
局部搜索功能提供多�U�方式进行多边�Ş和多边�Ş上的点的定位�Q�以及查询局部的一些环境信息。比如射�U�查询、计��离最�q�的墙的距离之类的�?/span>

Many of the query methods require a NavmeshQueryFilter. Filters define area traversal costs as well as flags used for including/excluding polygons and off-mesh connections from results.
许多查询�Ҏ��要求一个NavmeshQueryFilter(查询�q��o�?。过滤器定义了Polygon和off-mesh connections的穿��代��P��代�h值可以参与启发式的计��，用来军_��是否在最�l��\径里包含/排除某个Polygon或off-mesh connections�?/span>

The best way to understand the query class is to play around with it. The Sample Pack includes the Query Explorer demo that permits experimentation with all of the main query features.
理解查询器的最好办法就是用一用。【Sample Pack(�C�Z��?】里的【Query Explorer(查询演示)】demo展示了查询器一些主要的�Ҏ��?/span>

Common Operations
通用操作

This section contains some simple examples of common query operations.
Finding a Point in the Navigation Mesh
You can't do much without first getting a valid point on the navigation mesh. So the first step is to find one.
GetNearestPoint(Vector3, Vector3, NavmeshQueryFilter, NavmeshPoint)
本节是例�?/span>
查询一个在Navmesh上的�?/span>
如果你没有一个Navmesh上的起始点的话，你能做的不多。所以第一部就是找一个点�?/span>
GetNearestPoint(Vector3, Vector3, NavmeshQueryFilter, NavmeshPoint)函数提供此功能�?/span>

CopyC#
// Where 'query' is a NavmeshQuery object and 'filter' is a NavmeshQueryFilter object.
// 'position' is a Vector3 indicating the world position of the client.
// 'query'是一�?NavmeshQuery对象�Q?filter'是一个NavmeshQueryFilter对象�?/span>
// 'position' 是一个Vector3对象�Q��gؓ角色的世界坐标�?/span>

NavmeshPoint result;
Vector3 extents = new Vector3(1, 1, 1); // Keep this to the minimum extents practical. // 范围��小��好�?/span>

NavStatus status = query.GetNearestPoly(position, extents, filter
, out result);

if (result.polyRef == Navmesh.NullPoly)
{
// Handle error. Could not find a result.
// The status can be checked to see if there was an error. If not, then
// the cause is that the search extents did not overlap any polygons.
// 错误处理。找不到�l�果�?/span>
// 可以��查状态看看是什么问题。如果没有问题，说明指定范围里不包含多边形�?/span>
}

// Use the result point, which includes a vector point and the reference of
// the polygon that contains the point.
//使用�l�果炏V��包括一个Vector3的点和包含这个点的Polygon的引用�?/span>

Basic Pathfinding
Even if you are planning to use PathCorridor or CrowdManager, you'll always need to do long distance planning using the basic NavmeshQuery features. First, get a path, then optionally straighten it.
基础的寻�?/span>
即��你打��用pathcorridor或crowdmanager,你也会需要NavmeshQuery的功能来完成一些长距离路径规划。第一�Q�获取一条�\径，然后选择性的弄直�?3)�?/span>

CopyC#
// Where 'query' is a NavmeshQuery object and 'filter' is a NavmeshQueryFilter object.
// 'start' and 'end' are NavmeshPoints known to be on the navigation mesh.
// 'query'是一�?NavmeshQuery对象�Q?filter'是一个NavmeshQueryFilter对象;
// 'start' �?'end' 是已知的在Navmesh上的�?

int pathCount;
// The path will be a list of polygon references.
// path是一�l�polygon的引�?
uint[] path = new uint[100]; // Size for maximum allowed path length. // 路径的最大长�?
NavStatus status;

if (start.polyRef == end.polyRef)
{
// No need to do any planning.
// 开始点和结束点在同一个多边�Ş内，不需要进行�\径规�?
pathCount = 1;
path[0] = start.polyRef;
}
else
{
status = query.FindPath(start, end, filter, path
, out pathCount);

if (NavUtil.Failed(status) || path.pathCount == 0)
{
// Handle pathfinding failure.
// 处理寻�\��p�|;
}
else if (end.polyRef != path[pathCount - 1])
{
// Handle a partial path.
// The query either could not reach the end point,
// or the path buffer was too small to hold the
// entire path. (A check of 'status' will reveal if
// the buffer was too small.)
// 处理只有一部分路径的情�?
// 可能是结束点不可�?
// 或者�\径的buffer长度太小�Q�装不下整条路径;
// 如果是buffer太小�Q�可以检查state;
}

}

// If you need to straighten the path...
// 如果你需要拉直�\�?

const int MaxStraightPath = 4; // Just getting the first 4 waypoints. // 只处理前4个�\�?
int wpCount;

// The waypoints.
// 路点列表;
Vector3[] wpPoints = new Vecotr3[MaxStraightPath];

// A list of polygon references. (The polygon being entered at each waypoint.)
// 一个多边�Ş引用列表;(路点是多边�Ş的入口点)
uint[] wpPath = new uint[MaxStraightPath];

// The type of each waypoint. (Start, end, off-mesh connection.)
// 每一个�\点的�c�d��信息.(开始点�Q�结束点, �q�接);
WaypointFlag[] wpFlags = new WaypointFlag[MaxStraightPath];

status = query.GetStraightPath(start.point
, goal.point
, path
, 0 // The index of the start of the path. // 路径的开始点;
, pathCount // The length of the path. // 路径的长�?
, wpPoints
, wpFlags
, wpPath
, out wpCount);

if (NavUtil.Failed(status) || wpCount == 0)
{
// Handle the failure. There should always be at least one waypoint
// (the goal) for a valid point/path combination,
// 处理��p�|。应该��L��存在一个点(目标�?用于路径合�ƈ.
}

// Use the path and waypoints.
// 使用路径和�\�?

(1)可以理解为句柄，或烦引�?/span>
(2)Path上每个多边�Ş中心之间的连�U�一般不会是直线�Q��\径如果有拐角也会造成一些美观上的问题，�q�个时候需要��用特定的�Ҏ��\径变得尽量笔��_��好像将一根��子拉直�?/span>

点点滴滴 2016-11-08 21:15 发表评论

点点滴滴 — Tue, 08 Nov 2016 13:14:00 GMT

The Navigation Mesh
��译�Q�kun 2014.12.4

The navigation mesh is the primary data model for the navigation system. The only user component that deals directly with the mesh on a regular basis is the component that is responsible for creating the mesh and managing its state. Normal navigation clients, the one's needing to perform pathfinding and such, rarely if ever interact directly with the navigation mesh.
NavigationMesh是导航系�l�的主要数据模型。用户只需要创建导航网格数据和�l�护数据状态。需要��用导航的地方一般是�q�行寻�\操作�Q�偶��也可以使用navmesh�q�行一些交互�?/span>

Core Class: Navmesh
核心�c�：Navmesh

The Data Model
数据模型

Tiles
At the core of the navigation mesh is the tile. Tiles hold the vast majority of structural and state information. In fact, the Navmesh class is little more than a tile manager. It may consist of a single tile, or many tiles laid out in a grid that can be swapped in and out at runtime.
The tile based structure of the navigation mesh adds a lot of flexibility. As mentioned, tiles can be swapped in and out at runtime. This means that the mesh can represent a large area, but not all tiles have to be loaded and active, reducing the mesh's memory footprint. This also allows for a situation where individual tiles can be rebuilt without the need to rebuild the entire mesh.

Tiles(片区)
Navmesh的核心概念之一��是Tile。Tiles存放了大多数的结构信息和状态信息。事实上�Q�Navmesh�c�L��点像一个TileManager。Navmesh可以由单个Tile构成�Q�也可以向网��g��L��q�铺开来，以便在运行期动态的替换其中的某个Tile�?/span>

Structural Elements
The tile's structural data is what defines the navigation graph used for pathfinding. It consists of two types of elements: Polygons and off-mesh connections.
The core of the structure is a mesh of convex polygons with between three and MaxAllowedVertsPerPoly vertices. This mesh is in the same format as NMGen's PolyMesh structure, and usually represents an abstraction of a scene's static geometry.
Off-mesh connections are optional. They consist of two connected endpoints, at least one of which resides within a polygon in the polygon mesh. Off-mesh connections are added to the navigation graph as a single edge and represent special travel routes not defined by scene geometry. Think: The route an agent travels if it jumps over a railing that normally blocks movement.

节点元素
Tile的数据结构是一个用于寻路的graph(�?。它�׃��U�数据结构组成：Polygons(多边形集�?和off-mesh connections(分离的网��g��间的�q�接关系集合)�?/span>
Off-mesh connections(分离的网��g��间的�q�接关系集合)可以没有。它�׃��个相互连接的端点构成�Q�至��一边在某个多边形里。Off-mesh connections作�ؓ单独的边��d��到图的数据结构里。它代表着一�U�特�D�的行走路线�Q��ƈ且不是由原始场景的几何体生成的。想象一下，一个角色蟩�q�一个栏�?栏杆可以�ȝ��普通的前进�?/span>

State Data
Tiles also contain state data. This data is associated with individual polygons and off-mesh connections. State data includes area and flags.
Areas are used to associate traversal cost to structural elements. This effects pathfinding. For example, the area representing swampland can have a higher cost than the area representing smooth surfaces such as meadowland.
Flags can be used to control when a structural element is traversable. For example, a flag can be set on the polygon below a door to indicate that it is closed and locked. Or a flag can indicate that only agents of a particular type are allowed to traverse the element.
It is important to note that areas and flags have no meaning within the navigation mesh itself. The interpretation of the values is dependant on the NavmeshQueryFilter used by each navigation client. For example: One filter may define a cost of 10 for area id 5, while another may define a cost of 2 for the same area. One flag may be set when a door is closed with one filter checking for the flag during pathfinding, while another filter, used by a ghost, ignores the flag completely.

状�?/span>
Tile包括了一些状态信息。状态用来区分不同的Polygons和off-mesh connections。状态数据包括areas(区域信息)和flags(标志�?�?/span>
Areas(区域)一般用来定义移动代��L��。代价媄响寻路。�D个例子，�I�越被标��Cؓ沼泽的区域时的代仯��费可能比�I�越标记��地的区域的代仯��高�?/span>
Flags(标志�?可以用来控制一个节点的可行走属性。�D个例子，一个作�?�?的多边�Ş�Q�在门关闭的时候，可以�l�这个多边�Ş讄��一个特�D�的标志位，以表�C�它是不可通过的。或者设�|�一个特�D�的标志位，只允许特定类型的角色通过�?/span>
Areas和Flags的意义不是由Navmesh定义的，�q�非帔R��要。这些特别指定的数字都是由导航系认的用户�pȝ��自定义的NavmeshQueryFilter来解释的。�D个例子：一个过滤器认�ؓID�?的区域具�?0点�\径代��P��而另一个过滤器则认为只�?的�\径代仗��当一个关闭的门的标志位被讄��?1)�Q�一�U�过滤器在寻路的时候就会考虑�q�种情况而将�q�个门视��Z��可通过�Q�另外一�U�过滤器-可能是用于鬼��的寻�\-��׃��完全忽略�q�个标志位而将此节点认为是可通过的�?/span>

Structure Versus State
Why is it important to know the difference between structural elements and state data?
The first reason is that it is possible to save and load state separately from structure. One common use case is to have a serialized version of the full navigation mesh that represents its default state. Then serialized versions of various states, such as the last runtime state, are used to overwrite the default state as needed.
The main limitation is that a state is only valid for a particular structure. So you can't, for example, save the state, change the tile structure, then load the original state into the new structure.
The second reason for understanding the difference between structure and state has to to with tile and polygon references...

�l�构VS状�?/span>
节点元素和状态之间进行了分离�Q�理解这炚w��帔R��要�?/span>
首先�Q�这样它们可以独立的�q�行保存和加载。一个通常的情冉|��Q�加载一个预制的Navmesh数据后，其中的状态可能都是默认��|��而利用一个上一�ơ运行时保存的串行化的状态缓存，可以覆盖原始的状态信息�?/span>
不过�q�里有一个限�Ӟ��状态信息和节点自��n是精��匹配的。你不能在更改完一个节点的信息后，又将一个老的状态赋�l�它�?/span>
�W�二点则是对Tile和Polygon的引用方式�?/span>

Tile and Polygon References
The last bit of information needed to understand the navigation mesh is the concept of tile and polygon references. These values are one of the few data types that are defined by the navigation mesh rather than the tiles within the mesh. It is important to understand what references are because they are used by various classes to automatically invalidate pathfinding data if the structure of a navigation mesh changes.
Essentially, tile and polygon references are unsigned integer 'handles' to structural elements within a navigation mesh. Tile references are rarely used by navigation clients, while polygon references are all over the place. Polygon references are unique for the navigation mesh, so they are useful for easily identifying a polygon without needing to know which tile it belongs to.
Despite the name, polygon references can refer to a either a polygon or an off-mesh connection.
References can become invalid. If they are used after they are invalidated, then methods will return a failure status. Polygon references are based on the tile reference. So they will be invalidated whenever their associated tile reference is invalidated.
Structural changes govern the life of a reference. Changing the configuration of a navigation mesh or the internal structure of a tile will invalidate all associated references.
References are preserved during tile state changes such as changes flags and areas. They are also preserved during normal runtime loading and unloading of tiles, and during normal serialization/de-serialization of a navigation mesh.

Tile和Polygon的引用方�?/span>
要完全理解Navmesh�Q�最后一点信息是关于Tile和Polygon的引用这个概��c��这些引用是Navmesh为数不多的数据结构之一�Q�而不是由Tile定义的。理解引用是什么很重要�Q�因为通过它可以实现当��D��|�格发生变化的时候，一些类似寻路功能的模块能自动的��引用的多边形置为无效�?/span>
本质上来��_��Tile和Polygon的引用是一个uint32(无符��h��?。Tile的引用很��被客户代码直接使用�Q�因��Z��用场合基本上都可以被Polygon代替。Navmesh里的每个Polygon的引用都是唯一的，因此它们能够非常方便的定位到指定的Polygon�Q�而不需要知道这个Polygon属于哪个Tile�?/span>
虽然名字差别比较大，Polygon的引用概念同时也�늛�了off-mesh connections对象�?/span>
引用可以变成无效的。如果在无效之后�q��用引用，函数会返回一个失败信息。Polygon的引用有效性是��Z��Tile的引用的。因此当Tile的引用无效了�Q�所有属于Tile的Polygon的引用也会无效�?/span>
构造的变化会媄响引用的生命周期。改变Navmesh的配�|�或者Tile的内部结构会引�v相关的引用全部失效�?/span>
引用会在Tile的状态发生变化的时候进行保存，比如指定Area或Flag值的时候。在�q�行期动态的加蝲或卸载Tile也会使引用自动保存，�q�有当正�怸�行化/反串行化一个Navmesh的时候�?/span>

Creating a Navigation Mesh

There are various pipelines for creating a navigation mesh. If you are using Unity, the Unity extensions make it easier. Otherwise, the basic steps are as follows:
Generate packed tile data:
Generate PolyMesh and PolyMeshDetail data using NMGen.
Optionally create a ConnectionSet. (Off-mesh connections.)
Load the data into a NavmeshTileBuildData object.
Create a NavmeshTileData object from the build data.

The tile's structure and default state is now locked into a packed data format that is ready to be loaded into a navigation mesh.

创徏一个Navigation Mesh
创徏一个Navmesh有一些流�E�。如果你在��用Unity�Q�那么CAI提供的Unity扩展会让�q��g事情�E�微��单点。否则，基本��程如下�Q?/span>
生成打包好的Tile数据.
使用NMGen生成PolyMesh和PolyMeshDetail�?/span>
创徏个ConnectionSet(Off-mesh connections的容�?�Q�这是可选的�?/span>
��这些数�?tile,PolyMesh,PolyMeshDetail,ConnectionSet)加蝲到NavmeshTileBuildData对象里�?/span>
创徏一个NavmeshTileDatad数据�?/span>

现在Tile的构成关�p�d��默认状态已�l�都��装到NavmeshTileData里了�Q��ƈ且�ؓ生成Navmesh而做了数据结构的改变�?/span>

Note Note:
Using the NavmeshTileBuildData class directly can be a bit daunting. The GetBuildData(BuildContext, Int32, Int32, PolyMeshData, PolyMeshDetailData, ConnectionSet, Boolean) utility method provides a standard way of
creating the build data.

注意�Q?/span>
直接使用NavmeshTileBuildData�c�d��能有炚w��搞。GetBuildData�q�个工具函数提供了一�U�标准流�E��?/span>

Create a navigation mesh:
Single tile navigation meshes are created using the the single step Create(NavmeshTileBuildData, Navmesh) method.
Multi-tile navigation meshes are created then loaded using multiple methods. Use the Create(NavmeshParams, Navmesh) method to initialize an empty mesh. then add tile data using the AddTile(NavmeshTileData, UInt32, UInt32) method.

创徏一个Navmesh
如果创徏只有个Tile的Navmesh,只需要调用一�ơCreate(【NavmeshTileBuildData�? Navmesh)函数�?/span>
创徏多Tile的Navmesh需要多�ơ调用函数。��用Create(【NavmeshParams�? Navmesh)函数创徏一个空的navmesh,然后使用AddTile函数��Tile��d��q�去(1)�?/span>

Navigation Mesh Serialization

The Navmesh class supports byte serialization using the GetSerializedMesh() method. This saves the entire mesh.
It is possible to serialize state separately from structure on a tile-by-tile basis. Get the tile from the mesh using the GetTile(Int32) method, then use the GetState(Byte[]) and SetState(Byte[]) methods.

Navmesh的串行化
Namvesh�c�L��持二�q�制串行化，使用GetSerializedMesh来完成。这会将整个mesh转成二进制数据�?/span>
它可以每Tile的、状态和拓扑�l�构分离的进行串行化。从mesh里取Tile使用GetTile(Int32)函数�Q�然后��用GetState(Byte[])函数和SetState(Byte[])函数�q�行状态的赋倹{�?/span>

(1)Tile数据有自��q��生成��程�Q�可以参考An Introduction to NMGen

点点滴滴 2016-11-08 21:14 发表评论

(搬运�?CritterAI官方文档��译【An Introduction to Navigation�?

点点滴滴 — Tue, 08 Nov 2016 13:13:00 GMT

An Introduction to Navigation
��译�Q�kun 2014.12.4

The navigation side of CAINav consists of features used to create and use navigation meshes for pathfinding and local steering.
CAINav提供创徏Navmesh、基于Navmesh的寻路和局部�{向避障�?br />

Core: org.critterai.nav
Unity extensions: org.critterai.nav.u3d
核心命名�I�间�Q�org.critterai.nav
Unity扩展�Q�org.critterai.nav.u3d

There are five main classes you'll be dealing with:
�l�常和你打交道的�c�L��五个�Q?br />

Note Note:
CAINav uses the OpenGL coordinate system.
注意�Q?br />CAINav使用OpenGL坐标�p�R�?br />

The Navmesh class defines the structure and state of the navigation mesh. The only user component that deals directly with this class on a regular basis is the component responsible for creating the mesh and managing its state. Normal navigation clients, the one's needing to perform pathfinding and such, rarely if ever interact directly with the navigation mesh.
【Navmesh】类定义了导航网格的数据�l�构和状态。这个类用于保存用户创徏的导航网格数据和数据状态。需要��用导航的地方一般是�q�行寻�\操作�Q�偶��也可以使用navmesh�q�行一些交互�?br />

The most important class to understand and become comfortable with is the NavmeshQuery class. It provides almost all of the client navigation features, including A* and Dijkstra path searches, string pulling, point and polygon searches, raycasting, etc.
【NavmeshQuery】类是需要理解透彻的最重要的类。它提供了所有用��L�的导航功能，包括使用A*��法和Dijkstra��法�q�行寻�\、��索牵引、搜索点和多边�Ş、射�U�查询等�{��?br />

The NavmeshQueryFilter is a seemingly minor class, but it has a large impact on navigation. Filters are used to define the costs of traversing the mesh and flags that control which parts of the navigation mesh are included in operations. Multiple filters can be used to customize the navigation behavior on a per client basis.
【NavmeshQueryFilter】是一个看��h��很小的类�Q�但是它对导航的影响很大。过滤器用来定义�I�过某个区域时的代�h。可以��用多个过滤器来实现自定义的导航行为�?br />

The PathCorridor class provides a way of moving along a navigation path without worrying about the minutiae of managing the path.
【PathCorridor】类提供了一�U�沿��D��路径�Q�而不必担心管理�\径的�l�节(1)�?br />

The CrowdManager is the big beast of the navigation classes. It not only handles a lot of the path management for you, but also local steering and dynamic avoidance between navigation clients. I.e. It can keep your agents from running into each other.
【CrowdManager】类是十分庞杂的一个类。它不仅��Z��处理了非常多的�\径管理相关的事情�Q�同时也处理一些局部避障和避开其它寻�\代理对象。也��是��_��他可以让所有的代理对象不会�怺��I�插�?br />

(1)需要实验�?nbsp;

点点滴滴 2016-11-08 21:13 发表评论

(搬运�?五种开源协议的比较(BSD,Apache,GPL,LGPL,MIT)

点点滴滴 — Tue, 28 Dec 2010 09:07:00 GMT

当Adobe、Microsoft、Sun�{�一�p�d��巨头开始表现出�?#8221;开�?#8221;的青睐时�Q?#8221;开�?#8221;的时代即��到来！

最初来自：sinoprise.com/read.php?tid-662-page-e-fpage-1.html�Q�遗憄��是这个链接已�l�打不开了）�Q�我基本未改动，只是�q�行了一些排版和整理�?br>参考文献：http://www.fsf.org/licensing/licenses/

��C��存在的开源协议很多，而经�q�Open Source Initiative�l�织通过批准的开源协议目前有58�U�（http://www.opensource.org/licenses/alphabetical�Q�。我们在常见的开源协议如BSD, GPL, LGPL,MIT�{�都是OSI批准的协议。如果要开源自��q��代码�Q�最好也是选择�q�些被批准的开源协议�?/p>

�q�里我们来看四种最常用的开源协议及它们的适用范围�Q�供那些准备开源或者��用开源��品的开发�h�?厂家参考�?/p>

BSD开源协议（original BSD license�?/strong>FreeBSD license�?/strong>Original BSD license�Q?/strong>

BSD开源协议是一个给于��用者很大自��q��协议。基本上使用者可�?#8221;为所�Ʋ�ؓ”,可以自由的��用，修改源代码，也可以将修改后的代码作�ؓ开源或者专有��Y件再发布�?/p>
�?#8221;为所�Ʋ�ؓ”的前提当你发布��用了BSD协议的代码，或则以BSD协议代码为基��做二�ơ开发自��q��产品�Ӟ��需要满��三个条�Ӟ��

如果再发布的产品中包含源代码�Q�则在源代码中必��d��有原来代码中的BSD协议�?
如果再发布的只是二进制类�?软�g�Q�则需要在�c�d��/软�g的文档和版权声明中包含原来代码中的BSD协议�?
不可以用开源代码的作�?机构名字和原来��品的名字做市场推�qѝ�?

BSD 代码鼓励代码�׃�n�Q�但需要尊重代码作者的著作权。BSD�׃��允许使用者修改和重新发布代码�Q�也允许使用或在BSD代码上开发商业��Y件发布和销售，因此是对商业集成很友好的协议。而很多的公司企业在选用开源��品的时候都首选BSD协议�Q�因为可以完全控制这些第三方的代码，在必要的时候可以修�Ҏ��者二�ơ开发�?/p>
Apache Licence 2.0�Q?/strong>Apache License, Version 2.0�?a >Apache License, Version 1.1�?a >Apache License, Version 1.0�Q?/strong>

Apache Licence是著名的非盈利开源组�l�Apache采用的协议。该协议和BSD�c�M��Q�同样鼓�׃��码共享和��重原作者的著作权，同样允许代码修改�Q�再发布�Q�作为开源或商业软�g�Q�。需要满��的条�g也和BSD�c�M��Q?/p>

需要给代码的用户一份Apache Licence
如果你修改了代码�Q�需要再被修改的文�g中说明�?
在�g伸的代码中（修改和有源代码衍生的代码中）需要带有原来代码中的协议，商标�Q�专利声明和其他原来作者规定需要包含的说明�?
如果再发布的产品中包含一个Notice文�g�Q�则在Notice文�g中需要带有Apache Licence。你可以在Notice中增加自��q��许可�Q�但不可以表��Cؓ对Apache Licence构成更改�?

Apache Licence也是对商业应用友好的许可。��用者也可以在需要的时候修改代码来满��需要�ƈ作�ؓ开源或商业产品发布/销售�?/p>
GPL�Q?/strong>GNU General Public License�Q?/strong>

我们很熟悉的Linux��是采用了GPL。GPL协议和BSD, Apache Licence�{�鼓�׃��码重用的许可很不一栗��GPL的出发点是代码的开�?免费使用和引�?修改/衍生代码的开�?免费使用�Q�但不允�怿�改后和衍生的代码做�ؓ闭源的商业��Y件发布和销售。这也就是�ؓ什么我们能用免费的各种linux�Q�包括商业公司的linux和linux上各�U�各��L��׃��人，�l�织�Q�以及商业��Y件公司开发的免费软�g了�?/p>
GPL协议的主要内�Ҏ��只要在一个��Y件中使用(“使用”指类库引用，修改后的代码或者衍生代�?GPL 协议的��品，则该软�g产品必须也采用GPL协议�Q�既必须也是开源和免费�?strong>�q�就是所谓的”传染�?#8221;。GPL协议的��品作��Z��个单独的产品使用没有��M��问题�Q�还可以享受免费的优�ѝ�?/p>
�׃��GPL严格要求使用了GPL�c�d��的��Y件��品必��M��用GPL协议�Q�对于��用GPL协议的开源代码，商业软�g或者对代码有保密要求的部门��׃��适合集成/采用作�ؓ�c�d��和二�ơ开发的基础�?/p>
其它�l�节如再发布的时候需要伴随GPL协议�{�和BSD/Apache�{�类伹{�?/p>
LGPL�Q?/strong>GNU Lesser General Public License�Q?/strong>

LGPL是GPL的一个�ؓ主要为类库��用设计的开源协议。和GPL要求��M��使用/修改/衍生之GPL�c�d��的的软�g必须采用GPL协议不同。LGPL允许商业软�g通过�c�d��引用(link)方式使用LGPL�c�d��而不需要开源商业��Y件的代码。这使得采用LGPL协议的开源代码可以被商业软�g作�ؓ�c�d��引用�q�发布和销售�?/p>
但是如果修改LGPL协议的代码或者衍生，则所有修改的代码�Q�涉及修攚w��分的额外代码和衍生的代码都必��采用LGPL协议。因此LGPL协议的开源代码很适合作�ؓ�W�三方类库被商业软�g引用�Q�但不适合希望以LGPL协议代码为基��Q�通过修改和衍生的方式做二�ơ开发的商业软�g采用�?/p>
GPL/LGPL都保障原作者的知识产权�Q�避免有人利用开源代码复制�ƈ开发类似的产品

MIT�Q?a >MIT�Q?/strong>

MIT是和BSD一样宽范的许可协议,作者只想保留版�?而无��M��其他了限�?也就是说,你必��d��你的发行版里包含原许可协议的声明,无论你是以二�q�制发布的还是以源代码发布的.

点点滴滴 2010-12-28 17:07 发表评论

久久不见久久见免费视频7,99久久国产亚洲高清观看2024 ,无码人妻久久一区二区三区蜜桃

(搬运�?Mangos代码阅读

(搬运�?CritterAI官方文档���译【An Introduction to Navigation�?

(搬运�?五种开源协议的比较(BSD,Apache,GPL,LGPL,MIT)

(搬运�?CritterAI官方文档��译【An Introduction to Navigation�?