pa/eqemu-server
2
0
Fork 0
mirror of https://github.com/EQEmu/Server.git synced 2026-09-08 10:16:37 +00:00
Code Issues Actions Packages Projects Releases Wiki Activity

Updated EQDictionary (markdown)

Uleat
2019-01-17 22:53:15 -05:00
parent 08857d44cb
commit 963a6a67dd
1 changed files with 31 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files
EQDictionary.md
+30
@@ -1,5 +1,35 @@
### What is it?
EQDictionary is a collection of lookup references, accessed by specific namespaces and referenced by client or mob version.
References are tied back to the originating client definition..but, are available through an indexed lookup system.
The purpose of this system is to allow cyclic or minimum conditional evaluations in order to transform data.
### What can you do with it?
Simplifying coding methodology can change current standards from this:
`if (ClientVersion() >= EQEmu::versions::ClientVersion::SoF) { bank_slot_count = 24; }`
`else { bank_slot_count = 16; }`
`if (current_slot >= bank_slot_count) { return; }`
Or this:
`if (m_ClientBitmask & EQEmu::versions::maskSoFAndLater) { bank_slot_count = 24; }`
`else { bank_slot_count = 16; }`
`if (current_slot >= bank_slot_count) { return; }`
To this:
`if (current_slot >= m_inv.GetInv().GetLookup()->InventoryTypeSize.Bank) { return; }`
The first case requires that clients to be added in order of release.
The second case will allow clients to be added in any order..but, requires awkward manipulation of mask bits.
The EQDictionary (last) case does not require any special ordering of clients or manipulation of mask bits.
In fact, this system makes ClientVersion bitmask use obselete.