-Item from the tool seems to reference dbo.item but there isn't an arcadia.dbo.item reference in this or really any of the Databases I've pulled... I'm assuming it means dbo.ItemResource but when I try to load that I get errors about missing columns and unexpected values.... I get a similar result dumping the sql into a csv. Inspecting the database and comparing it to the LUA I see they are different. I tried to reformat the LUA to be consistent with the table structure and while that allowed for the rdbtool to work I just end up with missing textures in game and almost all items showing up as broken.
I've also gone back and tried different version of the LUA from the tool and I found 91 would pull from sql but it still has the same issues in game.
-Item Reference I *think* with out item breaks the client. At least when I added it without the ITEM it broke.
-Summon is updated
I'm pretty sure I'm doing something wrong just not sure what it is.
Also as an update Staged Pet Dura is fixed. It was a graphic issue because I didn't have the stagedpet.rdb loaded.
-Item from the tool seems to reference dbo.item but there isn't an arcadia.dbo.item reference in this or really any of the Databases I've pulled... I'm assuming it means dbo.ItemResource but when I try to load that I get errors about missing columns and unexpected values.... I get a similar result dumping the sql into a csv. Inspecting the database and comparing it to the LUA I see they are different. I tried to reformat the LUA to be consistent with the table structure and while that allowed for the rdbtool to work I just end up with missing textures in game and almost all items showing up as broken.
I've also gone back and tried different version of the LUA from the tool and I found 91 would pull from sql but it still has the same issues in game.
-Item Reference I *think* with out item breaks the client. At least when I added it without the ITEM it broke.
-Summon is updated
I'm pretty sure I'm doing something wrong just not sure what it is.
Also as an update Staged Pet Dura is fixed. It was a graphic issue because I didn't have the stagedpet.rdb loaded.
dbo.item is there, its not table, its a view.
same for itemreferenceresource, its view
dbo.item is there, its not table, its a view.
same for itemreferenceresource, its view
I saw that shortly after making my post but I still am encountering the same issue. Where I get this error when trying to use Item95Database.lua in the rdbtool.
Quote:
04/02/2026 03:04:51:555 Error: SQL: SQLExecute error(-1):
04/02/2026 03:04:51:556 Error: SQL: query: SELECT "id", "name_id", "tooltip_id", "type", "group", "class", "wear_type", "set_id", "set_part_flag", "rank", "level", "enhance", "socket", "status_flag", "limit_deva", "limit_asura", "limit_gaia", "job_depth", "limit_fighter", "limit_hunter", "limit_magician", "limit_summoner", "use_min_level", "use_max_level", "range", "weight", "price", "huntaholic_point", "arena_point", "ethereal_durability", "endurance", "material", "summon_id", "item_use_flag", "available_period", "decrease_type", "throw_range", "base_type_0", "base_var1_0", "base_var2_0", "base_type_1", "base_var1_1", "base_var2_1", "base_type_2", "base_var1_2", "base_var2_2", "base_type_3", "base_var1_3", "base_var2_3", "opt_type_0", "opt_var1_0", "opt_var2_0", "opt_type_1", "opt_var1_1", "opt_var2_1", "opt_type_2", "opt_var1_2", "opt_var2_2", "opt_type_3", "opt_var1_3", "opt_var2_3", "effect_id", "enhance_id", "skill_id", "state_id", "state_level", "state_time", "cool_time", "cool_time_group", "model_type_dem", "model_type_def", "model_type_asm", "model_type_asf", "model_type_gam", "model_type_gaf", "deco_model_change", "model_00", "model_01", "model_02", "model_03", "model_04", "model_05", "model_06", "model_07", "model_08", "model_09", "model_10", "model_11", "model_12", "model_13", "model_14", "model_15", "model_16", "model_17", "texture_filename", "drop_type", "icon_id", "icon_file_name", "group_bit_set", "unknownValue1", "unknownValue2", "unknownValue3", "effect_id_01", "effect_id_02", "value_01", "value_02", "value_03", "value_04", "value_05", "value_06", "value_07", "value_08", "value_09", "value_10", "value_11", "value_12", "value_13", "value_14", "value_15", "value_16", "value_17", "value_18", "value_19", "value_20" FROM ArcadiaKiteKAt.dbo.Item;
04/02/2026 03:04:51:557 Error: SQL: 42S22:1:207:[Microsoft][ODBC SQL Server Driver][SQL Server]Invalid column name 'use_min_level'.
04/02/2026 03:04:51:557 Error: SQL: 42S22:2:207:[Microsoft][ODBC SQL Server Driver][SQL Server]Invalid column name 'use_max_level'.
04/02/2026 03:04:51:557 Error: SQL: 42S22:3:207:[Microsoft][ODBC SQL Server Driver][SQL Server]Invalid column name 'arena_point'.
04/02/2026 03:04:51:558 Error: SQL: 42S22:4:207:[Microsoft][ODBC SQL Server Driver][SQL Server]Invalid column name 'item_use_flag'.
04/02/2026 03:04:51:558 Error: SQL: 42S22:5:207:[Microsoft][ODBC SQL Server Driver][SQL Server]Invalid column name 'model_type_dem'.
04/02/2026 03:04:51:558 Error: SQL: 42S22:6:207:[Microsoft][ODBC SQL Server Driver][SQL Server]Invalid column name 'model_type_def'.
04/02/2026 03:04:51:558 Error: SQL: 42S22:7:207:[Microsoft][ODBC SQL Server Driver][SQL Server]Invalid column name 'model_type_asm'.
04/02/2026 03:04:51:558 Error: SQL: 42S22:8:207:[Microsoft][ODBC SQL Server Driver][SQL Server]Invalid column name 'model_type_asf'.
04/02/2026 03:04:51:558 Error: SQL: 42S22:9:207:[Microsoft][ODBC SQL Server Driver][SQL Server]Invalid column name 'model_type_gam'.
04/02/2026 03:04:51:558 Error: SQL: 42S22:10:207:[Microsoft][ODBC SQL Server Driver][SQL Server]Invalid column name 'model_type_gaf'.
04/02/2026 03:04:51:559 Error: SQL: 42S22:11:207:[Microsoft][ODBC SQL Server Driver][SQL Server]Invalid column name 'model_00'.
04/02/2026 03:04:51:559 Error: SQL: 42S22:12:207:[Microsoft][ODBC SQL Server Driver][SQL Server]Invalid column name 'model_01'.
04/02/2026 03:04:51:559 Error: SQL: 42S22:13:207:[Microsoft][ODBC SQL Server Driver][SQL Server]Invalid column name 'model_02'.
04/02/2026 03:04:51:559 Error: SQL: 42S22:14:207:[Microsoft][ODBC SQL Server Driver][SQL Server]Invalid column name 'model_03'.
04/02/2026 03:04:51:559 Error: SQL: 42S22:15:207:[Microsoft][ODBC SQL Server Driver][SQL Server]Invalid column name 'model_04'.
04/02/2026 03:04:51:559 Error: SQL: 42S22:16:207:[Microsoft][ODBC SQL Server Driver][SQL Server]Invalid column name 'model_05'.
04/02/2026 03:04:51:560 Error: SQL: 42S22:17:207:[Microsoft][ODBC SQL Server Driver][SQL Server]Invalid column name 'model_06'.
04/02/2026 03:04:51:560 Error: SQL: 42S22:18:207:[Microsoft][ODBC SQL Server Driver][SQL Server]Invalid column name 'model_07'.
04/02/2026 03:04:51:560 Error: SQL: 42S22:19:207:[Microsoft][ODBC SQL Server Driver][SQL Server]Invalid column name 'model_08'.
04/02/2026 03:04:51:560 Error: SQL: 42S22:20:207:[Microsoft][ODBC SQL Server Driver][SQL Server]Invalid column name 'model_09'.
04/02/2026 03:04:51:560 Error: SQL: 42S22:21:207:[Microsoft][ODBC SQL Server Driver][SQL Server]Invalid column name 'model_10'.
04/02/2026 03:04:51:560 Error: SQL: 42S22:22:207:[Microsoft][ODBC SQL Server Driver][SQL Server]Invalid column name 'model_11'.
04/02/2026 03:04:51:560 Error: SQL: 42S22:23:207:[Microsoft][ODBC SQL Server Driver][SQL Server]Invalid column name 'model_12'.
04/02/2026 03:04:51:561 Error: SQL: 42S22:24:207:[Microsoft][ODBC SQL Server Driver][SQL Server]Invalid column name 'model_13'.
04/02/2026 03:04:51:561 Error: SQL: 42S22:25:207:[Microsoft][ODBC SQL Server Driver][SQL Server]Invalid column name 'model_14'.
04/02/2026 03:04:51:561 Error: SQL: 42S22:26:207:[Microsoft][ODBC SQL Server Driver][SQL Server]Invalid column name 'model_15'.
04/02/2026 03:04:51:561 Error: SQL: 42S22:27:207:[Microsoft][ODBC SQL Server Driver][SQL Server]Invalid column name 'model_16'.
04/02/2026 03:04:51:561 Error: SQL: 42S22:28:207:[Microsoft][ODBC SQL Server Driver][SQL Server]Invalid column name 'model_17'.
04/02/2026 03:04:51:561 Error: SQL: 42S22:29:207:[Microsoft][ODBC SQL Server Driver][SQL Server]Invalid column name 'texture_filename'.
04/02/2026 03:04:51:561 Error: SQL: 42S22:30:207:[Microsoft][ODBC SQL Server Driver][SQL Server]Invalid column name 'drop_type'.
04/02/2026 03:04:51:562 Error: SQL: 42S22:31:207:[Microsoft][ODBC SQL Server Driver][SQL Server]Invalid column name 'icon_file_name'.
04/02/2026 03:04:51:562 Error: SQL: 42S22:32:207:[Microsoft][ODBC SQL Server Driver][SQL Server]Invalid column name 'unknownValue1'.
04/02/2026 03:04:51:562 Error: SQL: 42S22:33:207:[Microsoft][ODBC SQL Server Driver][SQL Server]Invalid column name 'unknownValue2'.
04/02/2026 03:04:51:562 Error: SQL: 42S22:34:207:[Microsoft][ODBC SQL Server Driver][SQL Server]Invalid column name 'unknownValue3'.
04/02/2026 03:04:51:562 Error: SQL: 42S22:35:207:[Microsoft][ODBC SQL Server Driver][SQL Server]Invalid column name 'effect_id_01'.
04/02/2026 03:04:51:562 Error: SQL: 42S22:36:207:[Microsoft][ODBC SQL Server Driver][SQL Server]Invalid column name 'effect_id_02'.
04/02/2026 03:04:51:563 Error: SQL: 42000:37:8180:[Microsoft][ODBC SQL Server Driver][SQL Server]Statement(s) could not be prepared.
If I use Item91Database.lua I get
Quote:
04/02/2026 03:09:40:863 Error: SQL: SQLExecute error(-1):
04/02/2026 03:09:40:864 Error: SQL: query: SELECT "id", "name_id", "tooltip_id", "type", "group", "class", "wear_type", "set_id", "set_part_flag", "grade", "rank", "level", "enhance", "socket", "status_flag", "limit_deva", "limit_asura", "limit_gaia", "job_depth", "limit_fighter", "limit_hunter", "limit_magician", "limit_summoner", "use_min_level", "use_max_level", "target_min_level", "target_max_level", "range", "weight", "price", "huntaholic_point", "arena_point", "ethereal_durability", "endurance", "material", "summon_id", "item_use_flag", "available_period", "decrease_type", "throw_range", "base_type_0", "base_var1_0", "base_var2_0", "base_type_1", "base_var1_1", "base_var2_1", "base_type_2", "base_var1_2", "base_var2_2", "base_type_3", "base_var1_3", "base_var2_3", "opt_type_0", "opt_var1_0", "opt_var2_0", "opt_type_1", "opt_var1_1", "opt_var2_1", "opt_type_2", "opt_var1_2", "opt_var2_2", "opt_type_3", "opt_var1_3", "opt_var2_3", "effect_id", "enhance_id", "skill_id", "state_id", "state_level", "state_time", "cool_time", "cool_time_group", "model_type_dem", "model_type_def", "model_type_asm", "model_type_asf", "model_type_gam", "model_type_gaf", "deco_model_change", "model_00", "model_01", "model_02", "model_03", "model_04", "model_05", "model_06", "model_07", "model_08", "model_09", "model_10", "model_11", "model_12", "model_13", "model_14", "model_15", "model_16", "model_17", "texture_filename", "drop_type", "icon_id", "icon_file_name", "script_text", "2nd_array", "group_bit_set" FROM ArcadiaKiteKat.dbo.Item;
04/02/2026 03:09:40:865 Error: SQL: 42S22:1:207:[Microsoft][ODBC SQL Server Driver][SQL Server]Invalid column name 'grade'.
04/02/2026 03:09:40:865 Error: SQL: 42S22:2:207:[Microsoft][ODBC SQL Server Driver][SQL Server]Invalid column name 'use_min_level'.
04/02/2026 03:09:40:865 Error: SQL: 42S22:3:207:[Microsoft][ODBC SQL Server Driver][SQL Server]Invalid column name 'use_max_level'.
04/02/2026 03:09:40:866 Error: SQL: 42S22:4:207:[Microsoft][ODBC SQL Server Driver][SQL Server]Invalid column name 'target_min_level'.
04/02/2026 03:09:40:866 Error: SQL: 42S22:5:207:[Microsoft][ODBC SQL Server Driver][SQL Server]Invalid column name 'target_max_level'.
04/02/2026 03:09:40:866 Error: SQL: 42S22:6:207:[Microsoft][ODBC SQL Server Driver][SQL Server]Invalid column name 'arena_point'.
04/02/2026 03:09:40:866 Error: SQL: 42S22:7:207:[Microsoft][ODBC SQL Server Driver][SQL Server]Invalid column name 'item_use_flag'.
04/02/2026 03:09:40:866 Error: SQL: 42S22:8:207:[Microsoft][ODBC SQL Server Driver][SQL Server]Invalid column name 'model_type_dem'.
04/02/2026 03:09:40:866 Error: SQL: 42S22:9:207:[Microsoft][ODBC SQL Server Driver][SQL Server]Invalid column name 'model_type_def'.
04/02/2026 03:09:40:867 Error: SQL: 42S22:10:207:[Microsoft][ODBC SQL Server Driver][SQL Server]Invalid column name 'model_type_asm'.
04/02/2026 03:09:40:867 Error: SQL: 42S22:11:207:[Microsoft][ODBC SQL Server Driver][SQL Server]Invalid column name 'model_type_asf'.
04/02/2026 03:09:40:867 Error: SQL: 42S22:12:207:[Microsoft][ODBC SQL Server Driver][SQL Server]Invalid column name 'model_type_gam'.
04/02/2026 03:09:40:867 Error: SQL: 42S22:13:207:[Microsoft][ODBC SQL Server Driver][SQL Server]Invalid column name 'model_type_gaf'.
04/02/2026 03:09:40:867 Error: SQL: 42S22:14:207:[Microsoft][ODBC SQL Server Driver][SQL Server]Invalid column name 'model_00'.
04/02/2026 03:09:40:867 Error: SQL: 42S22:15:207:[Microsoft][ODBC SQL Server Driver][SQL Server]Invalid column name 'model_01'.
04/02/2026 03:09:40:867 Error: SQL: 42S22:16:207:[Microsoft][ODBC SQL Server Driver][SQL Server]Invalid column name 'model_02'.
04/02/2026 03:09:40:868 Error: SQL: 42S22:17:207:[Microsoft][ODBC SQL Server Driver][SQL Server]Invalid column name 'model_03'.
04/02/2026 03:09:40:868 Error: SQL: 42S22:18:207:[Microsoft][ODBC SQL Server Driver][SQL Server]Invalid column name 'model_04'.
04/02/2026 03:09:40:868 Error: SQL: 42S22:19:207:[Microsoft][ODBC SQL Server Driver][SQL Server]Invalid column name 'model_05'.
04/02/2026 03:09:40:868 Error: SQL: 42S22:20:207:[Microsoft][ODBC SQL Server Driver][SQL Server]Invalid column name 'model_06'.
04/02/2026 03:09:40:868 Error: SQL: 42S22:21:207:[Microsoft][ODBC SQL Server Driver][SQL Server]Invalid column name 'model_07'.
04/02/2026 03:09:40:868 Error: SQL: 42S22:22:207:[Microsoft][ODBC SQL Server Driver][SQL Server]Invalid column name 'model_08'.
04/02/2026 03:09:40:869 Error: SQL: 42S22:23:207:[Microsoft][ODBC SQL Server Driver][SQL Server]Invalid column name 'model_09'.
04/02/2026 03:09:40:869 Error: SQL: 42S22:24:207:[Microsoft][ODBC SQL Server Driver][SQL Server]Invalid column name 'model_10'.
04/02/2026 03:09:40:869 Error: SQL: 42S22:25:207:[Microsoft][ODBC SQL Server Driver][SQL Server]Invalid column name 'model_11'.
04/02/2026 03:09:40:869 Error: SQL: 42S22:26:207:[Microsoft][ODBC SQL Server Driver][SQL Server]Invalid column name 'model_12'.
04/02/2026 03:09:40:869 Error: SQL: 42S22:27:207:[Microsoft][ODBC SQL Server Driver][SQL Server]Invalid column name 'model_13'.
04/02/2026 03:09:40:869 Error: SQL: 42S22:28:207:[Microsoft][ODBC SQL Server Driver][SQL Server]Invalid column name 'model_14'.
04/02/2026 03:09:40:869 Error: SQL: 42S22:29:207:[Microsoft][ODBC SQL Server Driver][SQL Server]Invalid column name 'model_15'.
04/02/2026 03:09:40:870 Error: SQL: 42S22:30:207:[Microsoft][ODBC SQL Server Driver][SQL Server]Invalid column name 'model_16'.
04/02/2026 03:09:40:870 Error: SQL: 42S22:31:207:[Microsoft][ODBC SQL Server Driver][SQL Server]Invalid column name 'model_17'.
04/02/2026 03:09:40:870 Error: SQL: 42S22:32:207:[Microsoft][ODBC SQL Server Driver][SQL Server]Invalid column name 'texture_filename'.
04/02/2026 03:09:40:870 Error: SQL: 42S22:33:207:[Microsoft][ODBC SQL Server Driver][SQL Server]Invalid column name 'drop_type'.
04/02/2026 03:09:40:870 Error: SQL: 42S22:34:207:[Microsoft][ODBC SQL Server Driver][SQL Server]Invalid column name 'icon_file_name'.
04/02/2026 03:09:40:870 Error: SQL: 42S22:35:207:[Microsoft][ODBC SQL Server Driver][SQL Server]Invalid column name 'script_text'.
04/02/2026 03:09:40:871 Error: SQL: 42S22:36:207:[Microsoft][ODBC SQL Server Driver][SQL Server]Invalid column name '2nd_array'.
04/02/2026 03:09:40:871 Error: SQL: 42000:37:8180:[Microsoft][ODBC SQL Server Driver][SQL Server]Statement(s) could not be prepared.
If I run Item91Database.lua against the dbo.ItemResource it pulls it into the tool but the game client has all sorts of missing items and textures.
I found issue. Fixed it, would repack the client datas with fresh rdbs and reupload the entire repack with new views/ updated tool/client today/tomorrow. If you have some things which you would like to share, send it to me, I will include it in the repack
Subject: SQL Version recommendation & DESUtil issue (Login failed for user 'sa')
Hi everyone,
I'm currently setting up this 9.5.2 repack and I'm running into the classic DB COM ERROR: Login failed for user 'sa' in my GameLog.
I have two specific questions for the community:
SQL Version: Which SQL Server version do you recommend for this specific repack? I am currently trying with SQL Server 2025 Express, but I suspect it might be too new for the binaries. Would SQL 2014 or 2016 be a better fit?
DESUtil Issue: When using DESUtil.exe, I enter my password, but nothing appears in the box below (it stays empty). Is the password supposed to be encrypted directly into the .opt file by the tool, or is it supposed to display the hash so I can copy-paste it manually?
Currently, my .opt has S:db.c._password:284850029C233306. If I want to use "Maxi2028", how can I get the correct hash if the tool isn't displaying anything?
Thanks for your help!
Subject: SQL Version recommendation & DESUtil issue (Login failed for user 'sa')
Hi everyone,
I'm currently setting up this 9.5.2 repack and I'm running into the classic DB COM ERROR: Login failed for user 'sa' in my GameLog.
I have two specific questions for the community:
SQL Version: Which SQL Server version do you recommend for this specific repack? I am currently trying with SQL Server 2025 Express, but I suspect it might be too new for the binaries. Would SQL 2014 or 2016 be a better fit?
DESUtil Issue: When using DESUtil.exe, I enter my password, but nothing appears in the box below (it stays empty). Is the password supposed to be encrypted directly into the .opt file by the tool, or is it supposed to display the hash so I can copy-paste it manually?
Currently, my .opt has S:db.c._password:284850029C233306. If I want to use "Maxi2028", how can I get the correct hash if the tool isn't displaying anything?
Thanks for your help!
U just opened DESUtil and worked fine. I pasted Maxi2028 in "decrypted", pressed encrypt and this appeared in "encrypted": 455600000300175f334b2f7d696cb12969cdee64cd38333333 3b06611333
Subject: SQL Version recommendation & DESUtil issue (Login failed for user 'sa')
Hi everyone,
I'm currently setting up this 9.5.2 repack and I'm running into the classic DB COM ERROR: Login failed for user 'sa' in my GameLog.
I have two specific questions for the community:
SQL Version: Which SQL Server version do you recommend for this specific repack? I am currently trying with SQL Server 2025 Express, but I suspect it might be too new for the binaries. Would SQL 2014 or 2016 be a better fit?
DESUtil Issue: When using DESUtil.exe, I enter my password, but nothing appears in the box below (it stays empty). Is the password supposed to be encrypted directly into the .opt file by the tool, or is it supposed to display the hash so I can copy-paste it manually?
Currently, my .opt has S:db.c._password:284850029C233306. If I want to use "Maxi2028", how can I get the correct hash if the tool isn't displaying anything?
Thanks for your help!
1. I'm running SQL 2022 and its working fine, not sure about another version.
2. You type the password, press encript and it will show the encrypted pass, you copy and paste the encrypted password into de .opt file manually.
Subject: SQL Version recommendation & DESUtil issue (Login failed for user 'sa')
Hi everyone,
I'm currently setting up this 9.5.2 repack and I'm running into the classic DB COM ERROR: Login failed for user 'sa' in my GameLog.
I have two specific questions for the community:
SQL Version: Which SQL Server version do you recommend for this specific repack? I am currently trying with SQL Server 2025 Express, but I suspect it might be too new for the binaries. Would SQL 2014 or 2016 be a better fit?
DESUtil Issue: When using DESUtil.exe, I enter my password, but nothing appears in the box below (it stays empty). Is the password supposed to be encrypted directly into the .opt file by the tool, or is it supposed to display the hash so I can copy-paste it manually?
Currently, my .opt has S:db.c._password:284850029C233306. If I want to use "Maxi2028", how can I get the correct hash if the tool isn't displaying anything?
Thanks for your help!
2025 should work fine. All of the database back up casts, .bak files, are backward compatible for newer SQL versions. Meaning as long as the new version can restore it then it can be used. Older versions can not restore a .bak file cast from a newer SQL version.
The express version I am unsure of as for how much it would allow database growth and still be useful. I know there is a database size limit that SQL express can restore.
I usually am just using the developer version of SQL because Microsoft allows you to obtain a license with a Microsoft account as long as you aren't using SQL for server deployment. That keeps me from having to be stuck on the express version.
Edit: It seems that the release is based on source code derived from 9.1 and 2022 is the latest SQL version that will work with it.
I found issue. Fixed it, would repack the client datas with fresh rdbs and reupload the entire repack with new views/ updated tool/client today/tomorrow. If you have some things which you would like to share, send it to me, I will include it in the repack
I don't have anything to share at this point, it seems all the issues I've run into so far have essentially been down to my own naivety.
- Unable to Get Pets to Level - Missing db_summonexp.rdb
The other problems I've encountered so far I'm thinking could be related to the item data / missing rdb issue. So before I spend to much time worrying about those other issues I'd like to see what things look like after you get things repacked and uploaded.
2025 should work fine. All of the database back up casts, .bak files, are backward compatible for newer SQL versions. Meaning as long as the new version can restore it then it can be used. Older versions can not restore a .bak file cast from a newer SQL version.
The express version I am unsure of as for how much it would allow database growth and still be useful. I know there is a database size limit that SQL express can restore.
I usually am just using the developer version of SQL because Microsoft allows you to obtain a license with a Microsoft account as long as you aren't using SQL for server deployment. That keeps me from having to be stuck on the express version.
2025 isnt fine, tryed it and its just simply dont work with GS, those drivers used in GS code arent supportet anymore at least for 9.1 source i use.
[Selling] KITEKAT 30 DAY KEY FOR SELL 08/14/2023 - Rust Trading - 0 Replies Selling a Kitekat rust cheat key
I have used it but dont need it anymore (will come with HWID Reset)
It is valid until 4th of September.
Original price: 31$
Want:17$ (Crypto LTC BTC or any crypto)
https://media.discordapp.net/attachments/10781259 96215111832/1079663174535610398/image.png?width=12 02&height=676
[Selling] RUST KITEKAT 20 DAYS REMAINING $15 08/14/2023 - Rust Trading - 0 Replies As title suggests I am selling my kitekat key since I am now playing EFT
There is 20ish days available and I am open to offers, would like around 15 dollars. For reference 7 days usually costs around 13.5 dollars.
My friend is also selling his key due to same situation so 2 keys available.
Add me on Discord .miraql
SUPPORTED OS:
Arcaida Repack 1.3..? ممكن ملفات Arcaida Repack 1.3 11/16/2011 - Rappelz Private Server - 1 Replies HI
Possible files Arcaida Repack 1.3 modern
ـــــــ ـــــــ& #1600;ــــــ&# 1600;ــــــ
السلام عليكم ورحمة الله وبركاته
ممكن ملفات
Arcaida Repack 1.3
جديدة وحديثة
UWC Repack 1.0.9.9 (aka Ramas Repack) 01/02/2008 - WoW Private Server - 16 Replies This is the newes release by Team UWC:
DL:
FULL RAR:
UWC Repack 1.0.9.9 (Rapidshare)
If you start the emu in the first time, you must type:
.create_auctiondb
.create_maildb
.create_buybackdb
