The DmN CMS 1.2.3 setup does more than create its own tables:
- It ALTERs the game databases: adds columns from its version files, for example MEMB_INFO Admin, last_login, activated, activation_id, last_login_ip, dmn_country, country and Character last_reset_time, resets, grand_resets, last_greset_time, dmn_pk_count, dmn_last_server_pk_count, mu_id.
- If Character has no identity column it adds
Character.id int IDENTITY; an existing id column that is not an identity is DROPPED first. - It DROPS and REPLACES WZ_CONNECT_MEMB and WZ_DISCONNECT_MEMB in the account database. Its versions also write to the web database (
[web db].dbo.DmN_IP_Logat login,[web db].dbo.DmN_OnlineCheckat logout). On MuDevs files (MEMB_STAT has HWID) it installs a variant with @hwid. - With an MD5 database it installs DmN_Check_Acc_MD5 (XP_MD5_EncodeKeyVal @pass, @username), and Add_Credits for its DmN_Shop_Credits table.
So: back up MuOnline (and Me_MuOnline) before the setup, keep your pack's original WZ_CONNECT_MEMB / WZ_DISCONNECT_MEMB text, and never rename or drop the DmN web database afterwards (logins and logouts then fail inside those procedures). Check what you have now:
SELECT name, modify_date FROM sys.procedures WHERE name IN ('WZ_CONNECT_MEMB', 'WZ_DISCONNECT_MEMB');
SELECT OBJECT_DEFINITION(OBJECT_ID('dbo.WZ_DISCONNECT_MEMB'));Password type detection: memb__pwd not varchar = WebZen MD5, varchar(32) = md5 text, anything else = plain.
Source: DmN CMS 1.2.3 (free-mu-cms-1.2.3) setup/application/controllers/controller.setup.php, setup/application/models/model.setup.php, setup/data/columns/required_columns[*].json, setup/data/procedures/required_stored_procedures[20.05.2015].json.