Resolved merge main new

zerohero

zerohero

Heir
Customer
I’m looking for people who are experienced with the merge process to help create a solid script for merging from new into main. Participants will be selected based on their positive reviews on the forum.
 
Deazer

Thread 'Instructions for merging game and login databases'

Database Merge Software: HeidiSQL or DataGrip

Script location: gameserver\sql\maintenance\server_merge.sql

Preparation process:
You must first make a backup of your databases - let's say Serverx2019 and Server2020. For example, we transfer data from the Serverx2019 database (src_db) to the Server2020 database (dst_db)
Create 2 databases - src_db (upload data from Serverx2019) and dst_db (upload data from Server2020)
1. src_db - base from which the data will be transferred to the one you need (Serverx2019)
2. dst_db - base to which you will transfer data (Server2020)...
 
DeadAngel said:
Deazer

Thread 'Instructions for merging game and login databases'

Database Merge Software: HeidiSQL or DataGrip

Script location: gameserver\sql\maintenance\server_merge.sql

Preparation process:
You must first make a backup of your databases - let's say Serverx2019 and Server2020. For example, we transfer data from the Serverx2019 database (src_db) to the Server2020 database (dst_db)
Create 2 databases - src_db (upload data from Serverx2019) and dst_db (upload data from Server2020)
1. src_db - base from which the data will be transferred to the one you need (Serverx2019)
2. dst_db - base to which you will transfer data (Server2020)...
Click to expand...

we know this, my friend, we have merged in this way, but there are some problems after 2 or 3 merges in account and name char
 
DeadAngel said:
Deazer

Thread 'Instructions for merging game and login databases'

Database Merge Software: HeidiSQL or DataGrip

Script location: gameserver\sql\maintenance\server_merge.sql

Preparation process:
You must first make a backup of your databases - let's say Serverx2019 and Server2020. For example, we transfer data from the Serverx2019 database (src_db) to the Server2020 database (dst_db)
Create 2 databases - src_db (upload data from Serverx2019) and dst_db (upload data from Server2020)
1. src_db - base from which the data will be transferred to the one you need (Serverx2019)
2. dst_db - base to which you will transfer data (Server2020)...
Click to expand...

я попробовал сделать то, что предлагает zero, но у нас возникла большая проблема, например:

в базе данных № 1: учетная запись с именем «pelelulelule»

и в базе данных № 2: учетная запись с именем «pelelulelule»

тогда слияние происходит автоматически:

если учетная запись «pelelulelule» содержит более «x» букв, удаляются 2 буквы и добавляется префикс

количество букв >= 12, затем удаляется первая буква, в результате получается «pelelulelu_1», и удаляются буквы «L» и «E»

--------------------------------------------------

тогда нет возможности увеличить максимальное количество с 12 до 14? Таким образом, это не повлияет на исходные имена учетных записей и, так сказать, на персонажей.
 
Since yesterday, while I started working on the merge process, I discovered additional issues.
For example, on the main server there are two similar names: admin and adminxl, and on the new server the same name admin exists again.
 
  • Like
Reactions: L2g
zerohero said:
Procuro pessoas com experiência no processo de mesclagem para ajudar a criar um script robusto para mesclar a nova versão na versão principal. Os participantes serão selecionados com base em suas avaliações positivas no fórum.
Click to expand...
Eu mantive um servidor on-line por 2 anos. A cada 4 meses fazia um novo e juntava com o antigo. Nunca tive problemas, tudo sempre funcionou bem após as fusões.

Quais suas dificuldades?
 
L2g said:
Eu mantive um servidor on-line por 2 anos. A cada 4 meses fazia um novo e juntava com o antigo. Nunca tive problemas, tudo sempre funcionou bem após as fusões.

Quais suas dificuldades?
Click to expand...

Do you have a common login? when you merge, what happens to the accounts? and after names?
 
zerohero said:
Vocês têm um login em comum? Quando vocês fizerem a fusão, o que acontece com as contas? E os nomes depois?
Click to expand...
Não tinha login comum, após a fusão dos logons recebiam um prefixo no final, assim como os nicks, isso tudo feito com o script disponibilizado pelo deazer.

Único problema é nas contas VIPs que não passam e os clan Halls e castelos,

Ao final de dois anos eu tinha mais de 20 mil contas registradas
 
L2g said:
Não tinha login comum, após a fusão dos logons recebiam um prefixo no final, assim como os nicks, isso tudo feito com o script disponibilizado pelo deazer.

Único problema é nas contas VIPs que não passam e os clan Halls e castelos,

Ao final de dois anos eu tinha mais de 20 mil contas registradas
Click to expand...
you probably don't understand what I mean, my friend, all the accounts are made on the main server and there is no need when I open a new one to make another account
 
L2g said:
Não tinha login comum, após a fusão dos logons recebiam um prefixo no final, assim como os nicks, isso tudo feito com o script disponibilizado pelo deazer.

Único problema é nas contas VIPs que não passam e os clan Halls e castelos,

Ao final de dois anos eu tinha mais de 20 mil contas registradas
Click to expand...
Deazer's script is good for 1 merge, zero is making more than 1 merge. That's why he have issues.
 
  • There is a common login and 2 game servers:
    • Main (Lucera)
    • New (Season1)
  • All accounts created on the website go to the Lucera database.
    • This database contains everything: accounts, old characters (chars), items, etc.
  • In the Season1 database:
    • Accounts are not created.
    • Only characters, items, clans, and other related data are stored.
  • When a merge occurs, the script:
    • Shortens names if they are too long.
    • Example: deazerlucera2 → deazerluce_1.
  • After the merge:
    • Players search for their accounts but don’t know where they are.
    • There are many support messages, and we have to tell each player individually how to find their account (deazerluce_1).
  • In the first database (main, Lucera), names are also altered:
    • Example: deazer → deazerxl.
    • If another merge happens and someone has the same name, it causes an error, because the name already exists (deazerxl) and cannot be created again.
 
zerohero said:
  • Existe um login comum e 2 servidores de jogo:
    • Principal (Lucera)
    • Novo (Temporada 1)
  • Todas as contas criadas no site são armazenadas no banco de dados da Lucera.
    • Este banco de dados contém tudo: contas, personagens antigos (chars), itens, etc.
  • Na base de dados da 1ª temporada:
    • Não foram criadas contas .
    • Apenas personagens, itens, clãs e outros dados relacionados são armazenados.
  • Quando ocorre uma mesclagem, o script:
    • Abrevia nomes se forem muito longos.
    • Exemplo: deazerlucera2 → deazerluce_1.
  • Após a fusão:
    • Os jogadores procuram suas contas, mas não sabem onde elas estão .
    • Há muitas mensagens de suporte e temos que dizer a cada jogador individualmente como encontrar sua conta (deazerluce_1).
  • No primeiro banco de dados (principal, Lucera), os nomes também foram alterados:
    • Exemplo: deazer → deazerxl.
    • Se ocorrer outra mesclagem e alguém já tiver o mesmo nome, isso causará um erro , porque o nome já existe (deazerxl) e não pode ser criado novamente.
Click to expand...
I understand, my case was actually different. I used separate accounts for each server, but I had this problem as well.

I made an official announcement telling anyone who was having issues to recover their account via email, since the email address was still the same and they could recover it, or at least check how their new account turned out (in my case).

You can edit the abbreviation and prefix it adds to each merge.
 
SELECT '-- check char_name ---';
UPDATE src_db.characters
SET char_name = CONCAT(char_name,'XL')
WHERE char_name in (SELECT char_name FROM dst_db.characters);

SELECT '-- check clan_name ---';
UPDATE src_db.clan_subpledges
SET name = CONCAT(name,'XL')
WHERE name in (SELECT name FROM dst_db.clan_subpledges);

SELECT '-- check ally_name ---';
UPDATE src_db.ally_data
SET ally_name = CONCAT(ally_name,'XL')
WHERE ally_name in (SELECT ally_name FROM dst_db.ally_data);
Click to expand...
 
MrTitan said:
Deazer's script is good for 1 merge, zero is making more than 1 merge. That's why he have issues.
Click to expand...
If you edit the script, it will still work even after several merges. I did 3 or 4 merges here and it worked fine.

The difference is that I used one account per server, not multi-login like Zero.
 
L2g said:
If you edit the script, it will still work even after several merges. I did 3 or 4 merges here and it worked fine.

The difference is that I used one account per server, not
Click to expand...

Good morning, we are talking about a common login and a proper merge without any questions and without putting the players in a position to look for an account, this is what we are trying to do and the right thing would be for all the characters to go to the main account simply with a different name without creating separate accounts and we fill the database with duplicates and triples of the same account
 
You must log in or register to reply here.
Back
Top