fnv1a | FNV-1a non-cryptographic hash function | Hashing library

It appears your goal is to generate a unique identifier for your database records. Usually your database system will allow you to set a primary key for your database records, which the system will then ensure is unique across the database. Such primary keys are generally enough for many applications. However, there are several other things to consider, such as:

• Whether identifiers have to be hard to guess, or merely "look random".
• Whether identifiers are the only thing that grants access to the record.

The best way to generate unique identifiers will depend on these and other questions, which I give in the section "Unique Random Identifiers". You should edit your question post with the answers to the six questions I give in that section; the answers will further suggest what kind of identifiers to use. However, if you can't tolerate the risk of duplicate identifiers, as in this case, then neither random numbers nor hashes of column values are appropriate as unique identifiers unless the application checks them for uniqueness.

The FNV1a-hash itself works in the C#-code. However, the C#-code differs from the Python-code in the following points regarding the processing of the input data:

• The C#-code doesn't remove \r\n at the end.
• The C#-code doesn't convert to lowercase letters.
• No 0-byte is appended in the C#-code.

Additionally, the C#-code doesn't use the text con_gameMsgWindow0MsgTime, but con_gameMsgWindow0LineCount.

The solution is to add the following line at the beginning of the ToHashFnv1a32-method of the C#-code: