- Katılım
- 6 Mayıs 2022
- Mesajlar
- 45,967
-- Update SMD Name
-- Update Start Position
-- Add New Guard Tower
INSERT INTO K_NPC VALUES (5600,'Guard
-- Add New Damage Skills for New Guard Tower
-- Add NPC Location's
-- Repair Monsters
DB'e Ardream Zone Eklemek
Knight Online Private Server dünyasında geliştirme yaparken, zone ekleme işlemleri önemli bir yer tutar. Özellikle Ardream Zone gibi özel alanlar, oyuncuların keşif yapabileceği, yeni görevlerin yer aldığı veya PvP aktivitelerinin yoğunlaştığı bölgeler olarak tasarlanabilir. Bu yazıda, Knight Online özel sunucularında Ardream Zone'u veritabanına nasıl ekleyeceğimizi adım adım anlatacağız.
Neden Zone Eklenmeli?
Zone eklemek, sunucunuzda oyun içi deneyimi zenginleştirir. Özellikle cap 83 ya da cap 70 gibi yüksek seviye sunucularda, oyuncuların gitmek isteyeceği yeni harita ve görev alanlarına ihtiyaç duyulur. Ardream Zone gibi özel bölgeler, hem PvP hem de PvE içerikleri için kullanılabilir. Bu sayede sunucunuz daha özgün bir yapıya kavuşur.
Gerekli Dosyalar
Ardream Zone eklemek için bazı dosyalara ihtiyacınız olacak. Bunlar:
- zone.txt
- mob.bin
- npc.bin
- item.bin
- Map dosyaları (.map)
Bu dosyalar genellikle KO Server Files içinde bulunur. Eğer özel bir emulator kullanıyorsanız, bu dosyaların formatı emulatorünüzle uyumlu olmalıdır. KO Source Code üzerinden çalışan sistemlerde bu uyumluluğu kontrol etmeniz önemlidir.
Veritabanı Ayarları
Ardream Zone için veritabanında bir alan tanımlamalısınız. Sunucunuz genellikle MySQL veya SQL Server kullanır. Veritabanında zone tablosuna yeni bir kayıt ekleyerek bölgeyi sisteme tanıtabilirsiniz. Örnek kayıt:
ZoneID: 1001
ZoneName: Ardream
MinLevel: 70
MaxLevel: 85
IsPK: 1
Bu değerler sunucu amacınıza göre özelleştirilebilir. Örneğin, PvP içeriği planlıyorsanız IsPK değerini 1 yapmalısınız.
Olası Hatalar ve Çözümler
Zone eklerken dikkat etmeniz gereken bazı detaylar vardır. Öncelikle zone.txt dosyasında tanımladığınız bölge, veritabanındaki ID ile uyumlu olmalıdır. Aksi takdirde sunucu başlatıldığında hata alabilirsiniz. Ayrıca, harita dosyalarının doğru yere konulduğundan emin olun. Map dosyaları genellikle GameServer klasörü altında belirli bir yapıya göre yer alır. Yanlış konumlandırılan dosyalar sunucuda boş harita hatası verebilir.
Sunucuyu Başlatma ve Test Etme
Tüm ayarlamalar tamamlandıktan sonra sunucunuzu başlatın. Zone doğru şekilde eklenmişse, oyuncular Ardream bölgesine girebilmeli. Bu bölgeye özel NPC'ler, moblar ve görevler tanımlanmışsa, hepsi düzgün çalışmalıdır. KO Client Edit işlemleriyle bu bölgeye özel görsel efektler veya müzikler de eklenebilir. Bu sayede bölge daha etkileyici hale gelir.
Sonuç
Knight Online özel sunucularında Ardream Zone gibi özel bölgeler eklemek, hem teknik bilgi gerektirir hem de sunucunuzun kalitesini artırır. Doğru yapılandırılmış bir zone, oyuncuların uzun süre kalmasını sağlayabilir. Bu yazıda anlatılan adımlar, hem KO Development ile ilgilenenler hem de private server sahipleri için faydalı olacaktır.
Adding Ardream Zone to Database
Knight Online Private Server development involves many technical aspects, one of which is adding custom zones. Zones like Ardream Zone can be designed as exploration areas, quest locations, or battlegrounds for PvP activities. In this article, we'll explain step by step how to add Ardream Zone to the database in Knight Online private servers.
Why Add Zones?
Adding zones enriches the gameplay experience on your server. Especially in high-level servers like cap 83 or cap 70, players need new maps and quest areas to explore. Zones such as Ardream can be used for both PvP and PvE content, making your server more unique and engaging.
Required Files
To add Ardream Zone, you will need specific files, including:
- zone.txt
- mob.bin
- npc.bin
- item.bin
- Map files (.map)
These files are typically found within KO Server Files. If you're using a custom emulator, ensure that these file formats are compatible with your system. Compatibility should be checked against your KO Source Code.
Database Configuration
You must define a new area in the database for Ardream Zone. Your server likely uses MySQL or SQL Server. You can register the new zone by adding a record into the zone table. Example entry:
ZoneID: 1001
ZoneName: Ardream
MinLevel: 70
MaxLevel: 85
IsPK: 1
These values can be customized based on your server's purpose. For instance, if you plan for PvP activity, set IsPK to 1.
Potential Errors and Solutions
When adding a zone, certain details must be carefully considered. First, the zone defined in zone.txt must match the ID in the database; otherwise, errors may occur upon server startup. Also, make sure map files are placed correctly. Map files usually reside under the GameServer folder according to a specific structure. Misplaced files can cause empty map errors on the server.
Launching and Testing the Server
After all configurations are completed, launch your server. If the zone is added correctly, players should be able to enter the Ardream area. If NPCs, mobs, or quests are defined for this zone, they should function properly. Special visual effects or music can also be added via KO Client Edit to make the zone more appealing.
Conclusion
Adding custom zones like Ardream Zone to Knight Online private servers requires technical knowledge but also increases your server's quality. Properly configured zones can encourage players to stay longer. The steps outlined in this article will be useful for those involved in KO Development as well as private server owners.
Kod:
DELETE FROM ZONE_INFO WHERE ZoneNo = 202 INSERT INTO ZONE_INFO VALUES (1,202,'freezone_1021.smd',1000,1000,0,2,0,'Ardream')
-- Update Start Position
Kod:
DELETE FROM START_POSITION WHERE ZoneID = 202 INSERT INTO START_POSITION VALUES(202,848,129,183,898,5,5,0,0,0,0)
-- Add New Guard Tower
Kod:
DELETE FROM K_NPC WHERE sSid = 5600 DELETE FROM K_NPC WHERE sSid = 5700
INSERT INTO K_NPC VALUES (5600,'Guard
Kod:
Tower',5301,100,0,0,2,0,62,1,1,1,0,90,0,0,100000,0,0,15000,497,497,0,1500,0,0,1000,300139,0,0,255,255,255,255,255,255,255,200,30,35,35,0,0,1,1,0) INSERT INTO K_NPC VALUES (5700,'Guard Tower',5401,100,0,0,1,0,62,1,1,1,0,90,0,0,100000,0,0,15000,497,497,0,1500,0,0,1000,300139,0,0,255,255,255,255,255,255,255,200,30,35,35,0,0,1,1,0)
-- Add New Damage Skills for New Guard Tower
Kod:
UPDATE MAGIC_TYPE3 SET FirstDamage = -15000,EndDamage = 0,DirectType = 1,Radius = 20,TimeDamage = 0,Duration = 0,Attribute = 1 WHERE iNum = 300139
-- Add NPC Location's
Kod:
DELETE FROM K_NPCPOS WHERE ZoneId = 202 INSERT INTO K_NPCPOS VALUES (202,5600,104,0,0,0,0,190,947,190,947,190,947,190,947,1,90,0,0,'') INSERT INTO K_NPCPOS VALUES (202,5700,104,0,0,0,0,874,114,874,114,874,114,874,114,1,90,0,0,'') INSERT INTO K_NPCPOS VALUES (202,2801,1,0,0,0,0,578,510,590,490,510,578,590,490,5,300,0,0,NULL) INSERT INTO K_NPCPOS VALUES (202,2801,1,0,0,0,0,536,514,544,506,514,536,544,506,5,300,0,0,NULL) INSERT INTO K_NPCPOS VALUES (202,2801,1,0,0,0,0,504,510,512,502,510,504,512,502,5,300,0,0,NULL) INSERT INTO K_NPCPOS VALUES (202,2801,1,0,0,0,0,514,538,522,534,538,514,522,534,5,300,0,0,NULL) INSERT INTO K_NPCPOS VALUES (202,2801,1,0,0,0,0,530,544,538,536,544,530,538,536,5,300,0,0,NULL) INSERT INTO K_NPCPOS VALUES (202,2807,1,0,0,0,0,532,510,546,506,510,532,546,506,5,300,0,0,NULL) INSERT INTO K_NPCPOS VALUES (202,2807,1,0,0,0,0,484,542,488,534,542,484,488,534,5,300,0,0,NULL) INSERT INTO K_NPCPOS VALUES (202,2807,1,0,0,0,0,542,504,548,496,504,542,548,496,5,300,0,0,NULL) INSERT INTO K_NPCPOS VALUES (202,2807,1,0,0,0,0,530,546,536,530,546,530,536,530,5,300,0,0,NULL) INSERT INTO K_NPCPOS VALUES (202,2807,1,0,0,0,0,494,530,508,520,530,494,508,520,5,300,0,0,NULL) INSERT INTO K_NPCPOS VALUES (202,2807,1,0,0,0,0,506,528,516,514,528,506,516,514,5,300,0,0,NULL) INSERT INTO K_NPCPOS VALUES (202,2807,1,0,0,0,0,536,530,544,516,530,536,544,516,5,300,0,0,NULL) INSERT INTO K_NPCPOS VALUES (202,2807,1,0,0,0,0,558,532,576,516,532,558,576,516,5,300,0,0,NULL) INSERT INTO K_NPCPOS VALUES (202,2807,1,0,0,0,0,566,516,570,504,516,566,570,504,5,300,0,0,NULL) INSERT INTO K_NPCPOS VALUES (202,2807,1,0,0,0,0,498,524,500,520,524,498,500,520,5,300,0,0,NULL) INSERT INTO K_NPCPOS VALUES (202,2807,1,0,0,0,0,506,554,508,544,554,506,508,544,5,300,0,0,NULL) INSERT INTO K_NPCPOS VALUES (202,22120,140,0,0,0,0,874,127,874,127,874,127,874,127,1,90,0,0,'') INSERT INTO K_NPCPOS VALUES (202,5401,1,0,0,0,0,804,578,818,572,578,804,818,572,5,300,0,0,NULL) INSERT INTO K_NPCPOS VALUES (202,5600,104,0,0,0,0,161,894,161,894,161,894,161,894,1,90,0,0,'') INSERT INTO K_NPCPOS VALUES (202,5600,104,0,0,0,0,149,914,149,914,149,914,149,914,1,90,0,0,'') INSERT INTO K_NPCPOS VALUES (202,5600,104,0,0,0,0,113,883,113,883,113,883,113,883,1,90,0,0,'') INSERT INTO K_NPCPOS VALUES (202,5600,104,0,0,0,0,222,900,222,900,222,900,222,900,1,90,0,0,'') INSERT INTO K_NPCPOS VALUES (202,5600,104,0,0,0,0,219,913,219,913,219,913,219,913,1,90,0,0,'') INSERT INTO K_NPCPOS VALUES (202,5600,104,0,0,0,0,138,870,138,870,138,870,138,870,1,90,0,0,'') INSERT INTO K_NPCPOS VALUES (202,5600,104,0,0,0,0,213,872,213,872,213,872,213,872,1,90,0,0,'') INSERT INTO K_NPCPOS VALUES (202,5600,104,0,0,0,0,193,871,193,871,193,871,193,871,1,90,0,0,'') INSERT INTO K_NPCPOS VALUES (202,5600,104,0,0,0,0,182,873,182,873,182,873,182,873,1,90,0,0,'') INSERT INTO K_NPCPOS VALUES (202,12120,140,0,0,0,0,179,942,179,942,179,942,179,942,1,90,0,0,'') INSERT INTO K_NPCPOS VALUES (202,5700,104,0,0,0,0,788,82,788,82,788,82,788,82,1,90,0,0,'') INSERT INTO K_NPCPOS VALUES (202,5700,104,0,0,0,0,799,130,799,130,799,130,799,130,1,90,0,0,'') INSERT INTO K_NPCPOS VALUES (202,5700,104,0,0,0,0,785,115,785,115,785,115,785,115,1,90,0,0,'') INSERT INTO K_NPCPOS VALUES (202,5700,104,0,0,0,0,803,113,803,113,803,113,803,113,1,90,0,0,'') INSERT INTO K_NPCPOS VALUES (202,5700,104,0,0,0,0,821,150,821,150,821,150,821,150,1,90,0,0,'') INSERT INTO K_NPCPOS VALUES (202,5700,104,0,0,0,0,831,161,831,161,831,161,831,161,1,90,0,0,'') INSERT INTO K_NPCPOS VALUES (202,5700,104,0,0,0,0,848,154,848,154,848,154,848,154,1,90,0,0,'') INSERT INTO K_NPCPOS VALUES (202,5700,104,0,0,0,0,871,148,871,148,871,148,871,148,1,90,0,0,'') INSERT INTO K_NPCPOS VALUES (202,22000,140,0,0,0,0,860,114,860,114,860,114,860,114,1,90,0,0,'') INSERT INTO K_NPCPOS VALUES (202,16096,140,0,0,0,0,200,942,200,942,200,942,200,942,1,90,0,0,'') INSERT INTO K_NPCPOS VALUES (202,5600,104,0,0,0,0,174,904,174,904,174,904,174,904,1,90,0,0,'') INSERT INTO K_NPCPOS VALUES (202,5600,104,0,0,0,0,159,873,159,873,159,873,159,873,1,90,0,0,'') INSERT INTO K_NPCPOS VALUES (202,5600,104,0,0,0,0,208,934,208,934,208,934,208,934,1,90,0,0,'') INSERT INTO K_NPCPOS VALUES (202,5600,104,0,0,0,0,173,934,173,934,173,934,173,934,1,90,0,0,'') INSERT INTO K_NPCPOS VALUES (202,5600,104,0,0,0,0,207,889,207,889,207,889,207,889,1,90,0,0,'') INSERT INTO K_NPCPOS VALUES (202,5600,104,0,0,0,0,128,896,128,896,128,896,128,896,1,90,0,0,'') INSERT INTO K_NPCPOS VALUES (202,5700,104,0,0,0,0,818,96,818,96,818,96,818,96,1,90,0,0,'') INSERT INTO K_NPCPOS VALUES (202,5700,104,0,0,0,0,847,116,847,116,847,116,847,116,1,90,0,0,'') INSERT INTO K_NPCPOS VALUES (202,5700,104,0,0,0,0,843,131,843,131,843,131,843,131,1,90,0,0,'') INSERT INTO K_NPCPOS VALUES (202,5700,104,0,0,0,0,841,177,841,177,841,177,841,177,1,90,0,0,'') INSERT INTO K_NPCPOS VALUES (202,5700,104,0,0,0,0,887,152,887,152,887,152,887,152,1,90,0,0,'') INSERT INTO K_NPCPOS VALUES (202,5700,104,0,0,0,0,817,125,817,125,817,125,817,125,1,90,0,0,'') INSERT INTO K_NPCPOS VALUES (202,5700,104,0,0,0,0,765,110,765,110,765,110,765,110,1,90,0,0,'') INSERT INTO K_NPCPOS VALUES (202,905,1,0,0,0,0,716,214,746,188,214,716,746,188,5,30,0,0,NULL) INSERT INTO K_NPCPOS VALUES (202,905,1,0,0,0,0,682,262,706,240,262,682,706,240,5,30,0,0,NULL) INSERT INTO K_NPCPOS VALUES (202,605,1,0,0,0,0,656,124,680,104,124,656,680,104,5,300,0,0,NULL) INSERT INTO K_NPCPOS VALUES (202,605,1,0,0,0,0,622,228,650,208,228,622,650,208,5,300,0,0,NULL) INSERT INTO K_NPCPOS VALUES (202,512,1,0,0,0,0,600,228,610,218,228,600,610,218,5,300,0,0,NULL) INSERT INTO K_NPCPOS VALUES (202,512,1,0,0,0,0,584,152,598,146,152,584,598,146,5,300,0,0,NULL) INSERT INTO K_NPCPOS VALUES (202,613,1,0,0,0,0,602,142,606,132,142,602,606,132,1,300,0,0,NULL) INSERT INTO K_NPCPOS VALUES (202,1203,1,0,0,0,0,510,214,538,194,214,510,538,194,5,300,0,0,NULL) INSERT INTO K_NPCPOS VALUES (202,1204,1,0,0,0,0,460,174,490,168,174,460,490,168,5,300,0,0,NULL) INSERT INTO K_NPCPOS VALUES (202,1203,1,0,0,0,0,476,114,502,100,114,476,502,100,5,300,0,0,NULL) INSERT INTO K_NPCPOS VALUES (202,1204,1,0,0,0,0,404,90,456,84,90,404,456,84,5,300,0,0,NULL) INSERT INTO K_NPCPOS VALUES (202,6920,1,0,0,0,0,464,144,484,140,144,464,484,140,1,3200,0,0,NULL) INSERT INTO K_NPCPOS VALUES (202,2401,1,0,0,0,0,330,182,350,166,182,330,350,166,5,300,0,0,NULL) INSERT INTO K_NPCPOS VALUES (202,1303,1,0,0,0,0,270,220,306,210,220,270,306,210,5,300,0,0,NULL) INSERT INTO K_NPCPOS VALUES (202,612,1,0,0,0,0,214,294,242,272,294,214,242,272,5,300,0,0,NULL) INSERT INTO K_NPCPOS VALUES (202,2102,1,0,0,0,0,228,352,252,334,352,228,252,334,5,300,0,0,NULL) INSERT INTO K_NPCPOS VALUES (202,2101,1,0,0,0,0,218,416,242,384,416,218,242,384,5,300,0,0,NULL) INSERT INTO K_NPCPOS VALUES (202,5401,1,0,0,0,0,134,514,184,494,514,134,184,494,6,300,0,0,NULL) INSERT INTO K_NPCPOS VALUES (202,5401,1,0,0,0,0,214,538,230,526,538,214,230,526,6,300,0,0,NULL) INSERT INTO K_NPCPOS VALUES (202,5401,1,0,0,0,0,208,502,230,498,502,208,230,498,6,300,0,0,NULL) INSERT INTO K_NPCPOS VALUES (202,1104,1,0,0,0,0,146,508,162,494,508,146,162,494,5,300,0,0,NULL) INSERT INTO K_NPCPOS VALUES (202,1104,1,0,0,0,0,176,532,186,518,532,176,186,518,5,300,0,0,NULL) INSERT INTO K_NPCPOS VALUES (202,1104,1,0,0,0,0,224,512,238,502,512,224,238,502,5,300,0,0,NULL) INSERT INTO K_NPCPOS VALUES (202,504,1,0,0,0,0,184,514,198,498,514,184,198,498,5,300,0,0,NULL) INSERT INTO K_NPCPOS VALUES (202,504,1,0,0,0,0,170,488,192,472,488,170,192,472,5,300,0,0,NULL) INSERT INTO K_NPCPOS VALUES (202,504,1,0,0,0,0,232,492,250,480,492,232,250,480,5,300,0,0,NULL) INSERT INTO K_NPCPOS VALUES (202,6920,1,0,0,0,0,176,612,192,588,612,176,192,588,1,3200,0,0,NULL) INSERT INTO K_NPCPOS VALUES (202,5301,1,0,0,0,0,108,608,122,600,608,108,122,600,1,30,0,0,NULL) INSERT INTO K_NPCPOS VALUES (202,5301,1,0,0,0,0,128,648,154,624,648,128,154,624,1,30,0,0,NULL) INSERT INTO K_NPCPOS VALUES (202,5301,1,0,0,0,0,174,668,184,642,668,174,184,642,1,30,0,0,NULL) INSERT INTO K_NPCPOS VALUES (202,5301,1,0,0,0,0,142,620,154,584,620,142,154,584,1,30,0,0,NULL) INSERT INTO K_NPCPOS VALUES (202,5301,1,0,0,0,0,150,600,162,590,600,150,162,590,5,30,0,0,NULL) INSERT INTO K_NPCPOS VALUES (202,5301,1,0,0,0,0,172,648,182,636,648,172,182,636,5,30,0,0,NULL) INSERT INTO K_NPCPOS VALUES (202,5301,1,0,0,0,0,116,634,124,622,634,116,124,622,5,30,0,0,NULL) INSERT INTO K_NPCPOS VALUES (202,5301,1,0,0,0,0,148,648,154,634,648,148,154,634,5,30,0,0,NULL) INSERT INTO K_NPCPOS VALUES (202,905,1,0,0,0,0,110,688,142,678,688,110,142,678,7,30,0,0,NULL) INSERT INTO K_NPCPOS VALUES (202,2101,1,0,0,0,0,120,704,132,694,704,120,132,694,5,300,0,0,NULL) INSERT INTO K_NPCPOS VALUES (202,2101,1,0,0,0,0,74,608,86,590,608,74,86,590,5,300,0,0,NULL) INSERT INTO K_NPCPOS VALUES (202,504,1,0,0,0,0,90,602,104,596,602,90,104,596,5,300,0,0,NULL) INSERT INTO K_NPCPOS VALUES (202,613,1,0,0,0,0,84,588,98,580,588,84,98,580,1,300,0,0,NULL) INSERT INTO K_NPCPOS VALUES (202,2102,1,0,0,0,0,138,336,162,314,336,138,162,314,5,300,0,0,NULL) INSERT INTO K_NPCPOS VALUES (202,1721,1,0,0,0,0,118,286,140,252,286,118,140,252,5,300,0,0,NULL) INSERT INTO K_NPCPOS VALUES (202,6920,1,0,0,0,0,174,152,196,140,152,174,196,140,1,3200,0,0,NULL) INSERT INTO K_NPCPOS VALUES (202,6920,1,0,0,0,0,220,600,232,588,600,220,232,588,1,32000,0,0,NULL) INSERT INTO K_NPCPOS VALUES (202,6920,1,0,0,0,0,924,622,934,612,622,924,934,612,1,32000,0,0,NULL) INSERT INTO K_NPCPOS VALUES (202,6920,1,0,0,0,0,878,410,896,394,410,878,896,394,1,32000,0,0,NULL) INSERT INTO K_NPCPOS VALUES (202,6920,1,0,0,0,0,320,862,334,854,862,320,334,854,1,32000,0,0,NULL) INSERT INTO K_NPCPOS VALUES (202,6920,1,0,0,0,0,398,674,410,670,674,398,410,670,1,32000,0,0,NULL) INSERT INTO K_NPCPOS VALUES (202,6920,1,0,0,0,0,420,520,430,514,520,420,430,514,1,32000,0,0,NULL) INSERT INTO K_NPCPOS VALUES (202,1311,1,0,0,0,0,378,596,390,586,596,378,390,586,1,32000,0,0,NULL) INSERT INTO K_NPCPOS VALUES (202,1311,1,0,0,0,0,96,538,108,530,538,96,108,530,1,32000,0,0,NULL) INSERT INTO K_NPCPOS VALUES (202,1311,1,0,0,0,0,722,864,726,860,864,722,726,860,1,32000,0,0,NULL) INSERT INTO K_NPCPOS VALUES (202,1311,1,0,0,0,0,852,734,860,714,734,852,860,714,1,32000,0,0,NULL) INSERT INTO K_NPCPOS VALUES (202,1311,1,0,0,0,0,654,498,660,484,498,654,660,484,1,32000,0,0,NULL) INSERT INTO K_NPCPOS VALUES (202,1311,1,0,0,0,0,398,494,408,492,494,398,408,492,1,32000,0,0,NULL) INSERT INTO K_NPCPOS VALUES (202,907,1,0,0,0,0,506,626,520,618,626,506,520,618,1,32000,0,0,NULL) INSERT INTO K_NPCPOS VALUES (202,908,1,0,0,0,0,654,428,662,420,428,654,662,420,1,32000,0,0,NULL) INSERT INTO K_NPCPOS VALUES (202,907,1,0,0,0,0,456,390,464,384,390,456,464,384,1,32000,0,0,NULL) INSERT INTO K_NPCPOS VALUES (202,607,1,0,0,0,0,410,618,416,614,618,410,416,614,1,32000,0,0,NULL) INSERT INTO K_NPCPOS VALUES (202,607,1,0,0,0,0,232,230,240,224,230,232,240,224,1,32000,0,0,NULL) INSERT INTO K_NPCPOS VALUES (202,607,1,0,0,0,0,678,478,686,468,478,678,686,468,1,32000,0,0,NULL) INSERT INTO K_NPCPOS VALUES (202,608,1,0,0,0,0,568,444,580,440,444,568,580,440,1,32000,0,0,NULL) INSERT INTO K_NPCPOS VALUES (202,608,1,0,0,0,0,472,94,478,88,94,472,478,88,1,32000,0,0,NULL) INSERT INTO K_NPCPOS VALUES (202,608,1,0,0,0,0,182,104,196,100,104,182,196,100,1,32000,0,0,NULL) INSERT INTO K_NPCPOS VALUES (202,608,1,0,0,0,0,590,132,596,124,132,590,596,124,1,32000,0,0,NULL) INSERT INTO K_NPCPOS VALUES (202,607,1,0,0,0,0,868,756,876,736,756,868,876,736,1,32000,0,0,NULL) INSERT INTO K_NPCPOS VALUES (202,608,1,0,0,0,0,946,766,952,758,766,946,952,758,1,32000,0,0,NULL) INSERT INTO K_NPCPOS VALUES (202,506,1,0,0,0,0,160,524,170,518,524,160,170,518,1,32000,0,0,NULL) INSERT INTO K_NPCPOS VALUES (202,506,1,0,0,0,0,790,506,802,502,506,790,802,502,1,32000,0,0,NULL) INSERT INTO K_NPCPOS VALUES (202,507,1,0,0,0,0,562,608,568,602,608,562,568,602,1,32000,0,0,NULL) INSERT INTO K_NPCPOS VALUES (202,507,1,0,0,0,0,292,248,302,238,248,292,302,238,1,32000,0,0,NULL) INSERT INTO K_NPCPOS VALUES (202,508,1,0,0,0,0,236,370,246,368,370,236,246,368,1,32000,0,0,NULL) INSERT INTO K_NPCPOS VALUES (202,508,1,0,0,0,0,376,112,382,104,112,376,382,104,1,32000,0,0,NULL) INSERT INTO K_NPCPOS VALUES (202,1306,1,0,0,0,0,534,454,544,448,454,534,544,448,1,32000,0,0,NULL) INSERT INTO K_NPCPOS VALUES (202,1306,1,0,0,0,0,524,714,534,706,714,524,534,706,1,32000,0,0,NULL) INSERT INTO K_NPCPOS VALUES (202,1306,1,0,0,0,0,164,570,170,560,570,164,170,560,1,32000,0,0,NULL) INSERT INTO K_NPCPOS VALUES (202,1306,1,0,0,0,0,182,174,186,162,174,182,186,162,1,32000,0,0,NULL) INSERT INTO K_NPCPOS VALUES (202,1306,1,0,0,0,0,810,428,820,420,428,810,820,420,1,32000,0,0,NULL) INSERT INTO K_NPCPOS VALUES (202,1400,1,0,0,0,0,866,576,878,562,576,866,878,562,1,32000,0,0,NULL) INSERT INTO K_NPCPOS VALUES (202,1400,1,0,0,0,0,444,462,456,456,462,444,456,456,1,32000,0,0,NULL) INSERT INTO K_NPCPOS VALUES (202,1205,1,0,0,0,0,234,308,246,296,308,234,246,296,1,32000,0,0,NULL) INSERT INTO K_NPCPOS VALUES (202,1205,1,0,0,0,0,806,834,814,828,834,806,814,828,1,32000,0,0,NULL) INSERT INTO K_NPCPOS VALUES (202,1205,1,0,0,0,0,722,362,730,352,362,722,730,352,1,32000,0,0,NULL) INSERT INTO K_NPCPOS VALUES (202,1206,1,0,0,0,0,624,582,636,578,582,624,636,578,1,32000,0,0,NULL) INSERT INTO K_NPCPOS VALUES (202,1206,1,0,0,0,0,628,208,632,202,208,628,632,202,1,32000,0,0,NULL) INSERT INTO K_NPCPOS VALUES (202,1207,1,0,0,0,0,388,660,392,652,660,388,392,652,1,32000,0,0,NULL) INSERT INTO K_NPCPOS VALUES (202,1207,1,0,0,0,0,130,162,138,152,162,130,138,152,1,32000,0,0,NULL) INSERT INTO K_NPCPOS VALUES (202,1206,1,0,0,0,0,410,466,422,452,466,410,422,452,1,32000,0,0,NULL) INSERT INTO K_NPCPOS VALUES (202,1206,1,0,0,0,0,580,888,604,872,888,580,604,872,1,32000,0,0,NULL) INSERT INTO K_NPCPOS VALUES (202,1207,1,0,0,0,0,184,278,192,264,278,184,192,264,1,32000,0,0,NULL) INSERT INTO K_NPCPOS VALUES (202,905,1,0,0,0,0,792,350,812,336,350,792,812,336,5,30,0,0,NULL) INSERT INTO K_NPCPOS VALUES (202,905,1,0,0,0,0,812,336,826,318,336,812,826,318,5,30,0,0,NULL) INSERT INTO K_NPCPOS VALUES (202,905,1,0,0,0,0,860,340,876,322,340,860,876,322,7,30,0,0,NULL) INSERT INTO K_NPCPOS VALUES (202,2101,1,0,0,0,0,904,402,914,390,402,904,914,390,5,300,0,0,NULL) INSERT INTO K_NPCPOS VALUES (202,2101,1,0,0,0,0,922,438,940,426,438,922,940,426,5,300,0,0,NULL) INSERT INTO K_NPCPOS VALUES (202,504,1,0,0,0,0,826,388,874,366,388,826,874,366,5,300,0,0,NULL) INSERT INTO K_NPCPOS VALUES (202,504,1,0,0,0,0,930,488,940,474,488,930,940,474,5,300,0,0,NULL) INSERT INTO K_NPCPOS VALUES (202,1104,1,0,0,0,0,872,512,906,496,512,872,906,496,5,300,0,0,NULL) INSERT INTO K_NPCPOS VALUES (202,5301,1,0,0,0,0,922,604,944,580,604,922,944,580,5,300,0,0,NULL) INSERT INTO K_NPCPOS VALUES (202,5301,1,0,0,0,0,922,570,938,560,570,922,938,560,5,300,0,0,NULL) INSERT INTO K_NPCPOS VALUES (202,1104,1,0,0,0,0,904,566,924,550,566,904,924,550,5,300,0,0,NULL) INSERT INTO K_NPCPOS VALUES (202,5301,1,0,0,0,0,942,650,956,628,650,942,956,628,5,300,0,0,NULL) INSERT INTO K_NPCPOS VALUES (202,2102,1,0,0,0,0,932,638,946,626,638,932,946,626,3,300,0,0,NULL) INSERT INTO K_NPCPOS VALUES (202,2101,1,0,0,0,0,940,698,948,686,698,940,948,686,5,300,0,0,NULL) INSERT INTO K_NPCPOS VALUES (202,612,1,0,0,0,0,938,766,948,748,766,938,948,748,5,300,0,0,NULL) INSERT INTO K_NPCPOS VALUES (202,1721,1,0,0,0,0,942,852,964,834,852,942,964,834,5,300,0,0,NULL) INSERT INTO K_NPCPOS VALUES (202,2401,1,0,0,0,0,850,858,906,828,858,850,906,828,5,300,0,0,NULL) INSERT INTO K_NPCPOS VALUES (202,1204,1,0,0,0,0,714,910,732,900,910,714,732,900,5,300,0,0,NULL) INSERT INTO K_NPCPOS VALUES (202,1204,1,0,0,0,0,650,906,656,904,906,650,656,904,5,300,0,0,NULL) INSERT INTO K_NPCPOS VALUES (202,605,1,0,0,0,0,350,918,364,904,918,350,364,904,5,300,0,0,NULL) INSERT INTO K_NPCPOS VALUES (202,905,1,0,0,0,0,176,796,202,776,796,176,202,776,5,300,0,0,NULL) INSERT INTO K_NPCPOS VALUES (202,905,1,0,0,0,0,190,748,194,730,748,190,194,730,5,300,0,0,NULL) INSERT INTO K_NPCPOS VALUES (202,905,1,0,0,0,0,244,780,264,772,780,244,264,772,5,300,0,0,NULL) INSERT INTO K_NPCPOS VALUES (202,404,1,0,0,0,0,356,866,368,850,866,356,368,850,5,300,0,0,NULL) INSERT INTO K_NPCPOS VALUES (202,512,1,0,0,0,0,398,872,404,862,872,398,404,862,5,300,0,0,NULL) INSERT INTO K_NPCPOS VALUES (202,512,1,0,0,0,0,434,882,442,878,882,434,442,878,5,300,0,0,NULL) INSERT INTO K_NPCPOS VALUES (202,1203,1,0,0,0,0,520,892,530,882,892,520,530,882,5,300,0,0,NULL) INSERT INTO K_NPCPOS VALUES (202,1203,1,0,0,0,0,546,888,550,878,888,546,550,878,5,300,0,0,NULL) INSERT INTO K_NPCPOS VALUES (202,1204,1,0,0,0,0,600,878,614,872,878,600,614,872,5,300,0,0,NULL) INSERT INTO K_NPCPOS VALUES (202,1204,1,0,0,0,0,646,866,656,852,866,646,656,852,5,300,0,0,NULL) INSERT INTO K_NPCPOS VALUES (202,1303,1,0,0,0,0,814,756,828,744,756,814,828,744,5,300,0,0,NULL) INSERT INTO K_NPCPOS VALUES (202,2001,1,0,0,0,0,856,704,860,698,704,856,860,698,5,300,0,0,NULL) INSERT INTO K_NPCPOS VALUES (202,613,1,0,0,0,0,892,706,896,696,706,892,896,696,1,300,0,0,NULL) INSERT INTO K_NPCPOS VALUES (202,2102,1,0,0,0,0,834,662,854,658,662,834,854,658,5,300,0,0,NULL) INSERT INTO K_NPCPOS VALUES (202,5401,1,0,0,0,0,760,574,774,564,574,760,774,564,5,300,0,0,NULL) INSERT INTO K_NPCPOS VALUES (202,5401,1,0,0,0,0,860,600,868,592,600,860,868,592,5,300,0,0,NULL) INSERT INTO K_NPCPOS VALUES (202,2201,1,0,0,0,0,630,520,638,512,520,630,638,512,6,300,0,0,NULL) INSERT INTO K_NPCPOS VALUES (202,2202,1,0,0,0,0,610,472,616,468,472,610,616,468,1,300,0,0,NULL) INSERT INTO K_NPCPOS VALUES (202,2002,1,0,0,0,0,622,472,628,470,472,622,628,470,1,300,0,0,NULL) INSERT INTO K_NPCPOS VALUES (202,2801,1,0,0,0,0,588,540,594,494,540,588,594,494,5,300,0,0,NULL) INSERT INTO K_NPCPOS VALUES (202,2804,1,0,0,0,0,588,540,594,494,540,588,594,494,5,300,0,0,NULL) INSERT INTO K_NPCPOS VALUES (202,2807,1,0,0,0,0,584,520,590,506,520,584,590,506,3,300,0,0,NULL) INSERT INTO K_NPCPOS VALUES (202,2807,1,0,0,0,0,552,510,558,502,510,552,558,502,5,300,0,0,NULL) INSERT INTO K_NPCPOS VALUES (202,2804,1,0,0,0,0,556,538,560,526,538,556,560,526,5,300,0,0,NULL) INSERT INTO K_NPCPOS VALUES (202,2813,1,0,0,0,0,546,534,556,530,534,546,556,530,1,300,0,0,NULL) INSERT INTO K_NPCPOS VALUES (202,2813,1,0,0,0,0,520,546,526,542,546,520,526,542,1,300,0,0,NULL) INSERT INTO K_NPCPOS VALUES (202,2814,1,0,0,0,0,510,514,512,510,514,510,512,510,1,300,0,0,NULL) INSERT INTO K_NPCPOS VALUES (202,2817,1,0,0,0,0,522,526,530,522,526,522,530,522,1,18000,0,0,NULL) INSERT INTO K_NPCPOS VALUES (202,2807,1,0,0,0,0,486,526,494,524,526,486,494,524,1,300,0,0,NULL) INSERT INTO K_NPCPOS VALUES (202,2801,1,0,0,0,0,484,514,492,506,514,484,492,506,4,300,0,0,NULL) INSERT INTO K_NPCPOS VALUES (202,2801,1,0,0,0,0,492,550,498,546,550,492,498,546,2,300,0,0,NULL) INSERT INTO K_NPCPOS VALUES (202,2804,1,0,0,0,0,500,534,508,530,534,500,508,530,3,300,0,0,NULL) INSERT INTO K_NPCPOS VALUES (202,2804,1,0,0,0,0,500,534,508,530,534,500,508,530,3,300,0,0,NULL) INSERT INTO K_NPCPOS VALUES (202,2807,1,0,0,0,0,520,504,530,502,504,520,530,502,3,300,0,0,NULL) INSERT INTO K_NPCPOS VALUES (202,2807,1,0,0,0,0,456,550,458,508,550,456,458,508,2,300,0,0,NULL) INSERT INTO K_NPCPOS VALUES (202,2801,1,0,0,0,0,452,524,460,514,524,452,460,514,4,300,0,0,NULL) INSERT INTO K_NPCPOS VALUES (202,2804,1,0,0,0,0,452,538,462,530,538,452,462,530,3,300,0,0,NULL) INSERT INTO K_NPCPOS VALUES (202,2401,1,0,0,0,0,430,518,434,508,518,430,434,508,2,300,0,0,NULL) INSERT INTO K_NPCPOS VALUES (202,2401,1,0,0,0,0,424,554,436,546,554,424,436,546,1,300,0,0,NULL) INSERT INTO K_NPCPOS VALUES (202,1722,1,0,0,0,0,432,594,452,582,594,432,452,582,2,300,0,0,NULL) INSERT INTO K_NPCPOS VALUES (202,2102,1,0,0,0,0,442,580,446,574,580,442,446,574,1,300,0,0,NULL) INSERT INTO K_NPCPOS VALUES (202,2401,1,0,0,0,0,410,598,424,584,598,410,424,584,3,300,0,0,NULL) INSERT INTO K_NPCPOS VALUES (202,2422,1,0,0,0,0,436,694,452,684,694,436,452,684,2,300,0,0,NULL) INSERT INTO K_NPCPOS VALUES (202,3021,1,0,0,0,0,444,690,458,680,690,444,458,680,2,300,0,0,NULL) INSERT INTO K_NPCPOS VALUES (202,2202,1,0,0,0,0,434,706,442,702,706,434,442,702,1,300,0,0,NULL) INSERT INTO K_NPCPOS VALUES (202,2001,1,0,0,0,0,518,652,540,626,652,518,540,626,7,300,0,0,NULL) INSERT INTO K_NPCPOS VALUES (202,2402,1,0,0,0,0,620,414,640,406,414,620,640,406,2,300,0,0,NULL) INSERT INTO K_NPCPOS VALUES (202,2102,1,0,0,0,0,568,430,578,422,430,568,578,422,5,300,0,0,NULL) INSERT INTO K_NPCPOS VALUES (202,1721,1,0,0,0,0,468,428,484,406,428,468,484,406,5,300,0,0,NULL) INSERT INTO K_NPCPOS VALUES (202,3021,1,0,0,0,0,480,414,500,406,414,480,500,406,2,300,0,0,NULL)
-- Repair Monsters
Kod:
DECLARE @sSid int DECLARE RM_CX CURSOR FOR SELECT NpcID FROM K_NPCPOS WHERE ZoneID = 202 AND NpcID <> 5600 AND NpcID <> 5700 OPEN RM_CX FETCH NEXT FROM RM_CX INTO @sSid WHILE @@FETCH_STATUS = 0 BEGIN IF @sSid = 22000 UPDATE K_NPC SET byActType = 0 WHERE sSid = @sSid ELSE IF @sSid = 22120 UPDATE K_NPC SET byActType = 0 WHERE sSid = @sSid ELSE IF @sSid = 12120 UPDATE K_NPC SET byActType = 0 WHERE sSid = @sSid ELSE IF @sSid = 16096 UPDATE K_NPC SET byActType = 0 WHERE sSid = @sSid ELSE UPDATE K_MONSTER SET byActType = 7,byType = 12 WHERE sSid = @sSid FETCH NEXT FROM RM_CX INTO @sSid END CLOSE RM_CX DEALLOCATE RM_CX
DB'e Ardream Zone Eklemek
Knight Online Private Server dünyasında geliştirme yaparken, zone ekleme işlemleri önemli bir yer tutar. Özellikle Ardream Zone gibi özel alanlar, oyuncuların keşif yapabileceği, yeni görevlerin yer aldığı veya PvP aktivitelerinin yoğunlaştığı bölgeler olarak tasarlanabilir. Bu yazıda, Knight Online özel sunucularında Ardream Zone'u veritabanına nasıl ekleyeceğimizi adım adım anlatacağız.
Neden Zone Eklenmeli?
Zone eklemek, sunucunuzda oyun içi deneyimi zenginleştirir. Özellikle cap 83 ya da cap 70 gibi yüksek seviye sunucularda, oyuncuların gitmek isteyeceği yeni harita ve görev alanlarına ihtiyaç duyulur. Ardream Zone gibi özel bölgeler, hem PvP hem de PvE içerikleri için kullanılabilir. Bu sayede sunucunuz daha özgün bir yapıya kavuşur.
Gerekli Dosyalar
Ardream Zone eklemek için bazı dosyalara ihtiyacınız olacak. Bunlar:
- zone.txt
- mob.bin
- npc.bin
- item.bin
- Map dosyaları (.map)
Bu dosyalar genellikle KO Server Files içinde bulunur. Eğer özel bir emulator kullanıyorsanız, bu dosyaların formatı emulatorünüzle uyumlu olmalıdır. KO Source Code üzerinden çalışan sistemlerde bu uyumluluğu kontrol etmeniz önemlidir.
Veritabanı Ayarları
Ardream Zone için veritabanında bir alan tanımlamalısınız. Sunucunuz genellikle MySQL veya SQL Server kullanır. Veritabanında zone tablosuna yeni bir kayıt ekleyerek bölgeyi sisteme tanıtabilirsiniz. Örnek kayıt:
ZoneID: 1001
ZoneName: Ardream
MinLevel: 70
MaxLevel: 85
IsPK: 1
Bu değerler sunucu amacınıza göre özelleştirilebilir. Örneğin, PvP içeriği planlıyorsanız IsPK değerini 1 yapmalısınız.
Olası Hatalar ve Çözümler
Zone eklerken dikkat etmeniz gereken bazı detaylar vardır. Öncelikle zone.txt dosyasında tanımladığınız bölge, veritabanındaki ID ile uyumlu olmalıdır. Aksi takdirde sunucu başlatıldığında hata alabilirsiniz. Ayrıca, harita dosyalarının doğru yere konulduğundan emin olun. Map dosyaları genellikle GameServer klasörü altında belirli bir yapıya göre yer alır. Yanlış konumlandırılan dosyalar sunucuda boş harita hatası verebilir.
Sunucuyu Başlatma ve Test Etme
Tüm ayarlamalar tamamlandıktan sonra sunucunuzu başlatın. Zone doğru şekilde eklenmişse, oyuncular Ardream bölgesine girebilmeli. Bu bölgeye özel NPC'ler, moblar ve görevler tanımlanmışsa, hepsi düzgün çalışmalıdır. KO Client Edit işlemleriyle bu bölgeye özel görsel efektler veya müzikler de eklenebilir. Bu sayede bölge daha etkileyici hale gelir.
Sonuç
Knight Online özel sunucularında Ardream Zone gibi özel bölgeler eklemek, hem teknik bilgi gerektirir hem de sunucunuzun kalitesini artırır. Doğru yapılandırılmış bir zone, oyuncuların uzun süre kalmasını sağlayabilir. Bu yazıda anlatılan adımlar, hem KO Development ile ilgilenenler hem de private server sahipleri için faydalı olacaktır.
Adding Ardream Zone to Database
Knight Online Private Server development involves many technical aspects, one of which is adding custom zones. Zones like Ardream Zone can be designed as exploration areas, quest locations, or battlegrounds for PvP activities. In this article, we'll explain step by step how to add Ardream Zone to the database in Knight Online private servers.
Why Add Zones?
Adding zones enriches the gameplay experience on your server. Especially in high-level servers like cap 83 or cap 70, players need new maps and quest areas to explore. Zones such as Ardream can be used for both PvP and PvE content, making your server more unique and engaging.
Required Files
To add Ardream Zone, you will need specific files, including:
- zone.txt
- mob.bin
- npc.bin
- item.bin
- Map files (.map)
These files are typically found within KO Server Files. If you're using a custom emulator, ensure that these file formats are compatible with your system. Compatibility should be checked against your KO Source Code.
Database Configuration
You must define a new area in the database for Ardream Zone. Your server likely uses MySQL or SQL Server. You can register the new zone by adding a record into the zone table. Example entry:
ZoneID: 1001
ZoneName: Ardream
MinLevel: 70
MaxLevel: 85
IsPK: 1
These values can be customized based on your server's purpose. For instance, if you plan for PvP activity, set IsPK to 1.
Potential Errors and Solutions
When adding a zone, certain details must be carefully considered. First, the zone defined in zone.txt must match the ID in the database; otherwise, errors may occur upon server startup. Also, make sure map files are placed correctly. Map files usually reside under the GameServer folder according to a specific structure. Misplaced files can cause empty map errors on the server.
Launching and Testing the Server
After all configurations are completed, launch your server. If the zone is added correctly, players should be able to enter the Ardream area. If NPCs, mobs, or quests are defined for this zone, they should function properly. Special visual effects or music can also be added via KO Client Edit to make the zone more appealing.
Conclusion
Adding custom zones like Ardream Zone to Knight Online private servers requires technical knowledge but also increases your server's quality. Properly configured zones can encourage players to stay longer. The steps outlined in this article will be useful for those involved in KO Development as well as private server owners.
