Is this because of a client update?

In AzureWatch there’s a quest called “Learning the Language” where on the 3.3.5a server the quest chain completes as it should: you get the book and read it before that quest can complete and continue on to the quest given by the totem.

On the 6.x server once you accept the quest for the book the quest auto-completes (like the trigger is ignored or bypassed) and is ready to hand in at the totem before the book/primer is read.

Does this happen because of a dbc/core mismatch due to the client being updated that are not yet reflected in the core? ie.,. opcodes that changed. Or is this something in the data itself within the database?