-
Posts
659 -
Joined
-
Last visited
-
Days Won
9
Content Type
Profiles
Forums
Downloads
Jobs Available
Server Database
Third-Party Services
Top Guides
Store
Crowdfunding
Posts posted by Gidz Cross
-
-
Or could someone update that stat points up to 300 lines. That only supports lvl 255. I really need needed that.
-
-
No i mean what does buyingstore do. I found out that its an item if you click it you can open a shop. And it works to non merchant class. credits goes to iRO.
-
Uhm. Whats this for? I dont know this.
-
Download a fresh data translation and diff your client to use english texts. About sa rubbish chat. You can double click it to rename.
-
Download a fresh kRO.
-
you helped me a lot actually. Thank you!
-
Imo, Elemental shield is buggy at the moment. You can check my report. http://rathena.org/board/tracker/issue-9016-about-sorcerers-elemental-shield/ but it was closed saying that its already fixed but it not.
you can check my other thread about this.
http://rathena.org/board/tracker/issue-9025-about-sorcerers-elemental-shield-re-open/
-
Okay i think that since i dont use any other SQL files beside MAIN and LOGS. And @aleos told me that i still need to apply the update even so. I think that it is okay to ignore the the error like mob_db since like i said i dont use it.
So only these part is necessary right?
UPDATE `auction` SET `card0` = 256 WHERE `card0` = -256; UPDATE `cart_inventory` SET `card0` = 256 WHERE `card0` = -256; UPDATE `guild_storage` SET `card0` = 256 WHERE `card0` = -256; UPDATE `inventory` SET `card0` = 256 WHERE `card0` = -256; UPDATE `mail` SET `card0` = 256 WHERE `card0` = -256; UPDATE `storage` SET `card0` = 256 WHERE `card0` = -256; ALTER TABLE `auction` MODIFY `nameid` smallint(5) unsigned NOT NULL default '0'; ALTER TABLE `auction` MODIFY `card0` smallint(5) unsigned NOT NULL default '0'; ALTER TABLE `auction` MODIFY `card1` smallint(5) unsigned NOT NULL default '0'; ALTER TABLE `auction` MODIFY `card2` smallint(5) unsigned NOT NULL default '0'; ALTER TABLE `auction` MODIFY `card3` smallint(5) unsigned NOT NULL default '0'; ALTER TABLE `cart_inventory` MODIFY `nameid` smallint(5) unsigned NOT NULL default '0'; ALTER TABLE `cart_inventory` MODIFY `card0` smallint(5) unsigned NOT NULL default '0'; ALTER TABLE `cart_inventory` MODIFY `card1` smallint(5) unsigned NOT NULL default '0'; ALTER TABLE `cart_inventory` MODIFY `card2` smallint(5) unsigned NOT NULL default '0'; ALTER TABLE `cart_inventory` MODIFY `card3` smallint(5) unsigned NOT NULL default '0'; ALTER TABLE `guild_storage` MODIFY `nameid` smallint(5) unsigned NOT NULL default '0'; ALTER TABLE `guild_storage` MODIFY `card0` smallint(5) unsigned NOT NULL default '0'; ALTER TABLE `guild_storage` MODIFY `card1` smallint(5) unsigned NOT NULL default '0'; ALTER TABLE `guild_storage` MODIFY `card2` smallint(5) unsigned NOT NULL default '0'; ALTER TABLE `guild_storage` MODIFY `card3` smallint(5) unsigned NOT NULL default '0'; ALTER TABLE `inventory` MODIFY `nameid` smallint(5) unsigned NOT NULL default '0'; ALTER TABLE `inventory` MODIFY `card0` smallint(5) unsigned NOT NULL default '0'; ALTER TABLE `inventory` MODIFY `card1` smallint(5) unsigned NOT NULL default '0'; ALTER TABLE `inventory` MODIFY `card2` smallint(5) unsigned NOT NULL default '0'; ALTER TABLE `inventory` MODIFY `card3` smallint(5) unsigned NOT NULL default '0'; ALTER TABLE `mail` MODIFY `nameid` smallint(5) unsigned NOT NULL default '0'; ALTER TABLE `mail` MODIFY `card0` smallint(5) unsigned NOT NULL default '0'; ALTER TABLE `mail` MODIFY `card1` smallint(5) unsigned NOT NULL default '0'; ALTER TABLE `mail` MODIFY `card2` smallint(5) unsigned NOT NULL default '0'; ALTER TABLE `mail` MODIFY `card3` smallint(5) unsigned NOT NULL default '0'; ALTER TABLE `pet` MODIFY `egg_id` smallint(5) unsigned NOT NULL default '0'; ALTER TABLE `storage` MODIFY `nameid` smallint(5) unsigned NOT NULL default '0'; ALTER TABLE `storage` MODIFY `card0` smallint(5) unsigned NOT NULL default '0'; ALTER TABLE `storage` MODIFY `card1` smallint(5) unsigned NOT NULL default '0'; ALTER TABLE `storage` MODIFY `card2` smallint(5) unsigned NOT NULL default '0'; ALTER TABLE `storage` MODIFY `card3` smallint(5) unsigned NOT NULL default '0';
While i ignore these (From line 40 to 94)
ALTER TABLE `mob_db` MODIFY `MVP1id` smallint(5) unsigned NOT NULL default '0'; ALTER TABLE `mob_db` MODIFY `MVP2id` smallint(5) unsigned NOT NULL default '0'; ALTER TABLE `mob_db` MODIFY `MVP3id` smallint(5) unsigned NOT NULL default '0'; ALTER TABLE `mob_db` MODIFY `Drop1id` smallint(5) unsigned NOT NULL default '0'; ALTER TABLE `mob_db` MODIFY `Drop2id` smallint(5) unsigned NOT NULL default '0'; ALTER TABLE `mob_db` MODIFY `Drop3id` smallint(5) unsigned NOT NULL default '0'; ALTER TABLE `mob_db` MODIFY `Drop4id` smallint(5) unsigned NOT NULL default '0'; ALTER TABLE `mob_db` MODIFY `Drop5id` smallint(5) unsigned NOT NULL default '0'; ALTER TABLE `mob_db` MODIFY `Drop6id` smallint(5) unsigned NOT NULL default '0'; ALTER TABLE `mob_db` MODIFY `Drop7id` smallint(5) unsigned NOT NULL default '0'; ALTER TABLE `mob_db` MODIFY `Drop8id` smallint(5) unsigned NOT NULL default '0'; ALTER TABLE `mob_db` MODIFY `Drop9id` smallint(5) unsigned NOT NULL default '0'; ALTER TABLE `mob_db` MODIFY `DropCardid` smallint(5) unsigned NOT NULL default '0'; ALTER TABLE `mob_db2` MODIFY `MVP1id` smallint(5) unsigned NOT NULL default '0'; ALTER TABLE `mob_db2` MODIFY `MVP2id` smallint(5) unsigned NOT NULL default '0'; ALTER TABLE `mob_db2` MODIFY `MVP3id` smallint(5) unsigned NOT NULL default '0'; ALTER TABLE `mob_db2` MODIFY `Drop1id` smallint(5) unsigned NOT NULL default '0'; ALTER TABLE `mob_db2` MODIFY `Drop2id` smallint(5) unsigned NOT NULL default '0'; ALTER TABLE `mob_db2` MODIFY `Drop3id` smallint(5) unsigned NOT NULL default '0'; ALTER TABLE `mob_db2` MODIFY `Drop4id` smallint(5) unsigned NOT NULL default '0'; ALTER TABLE `mob_db2` MODIFY `Drop5id` smallint(5) unsigned NOT NULL default '0'; ALTER TABLE `mob_db2` MODIFY `Drop6id` smallint(5) unsigned NOT NULL default '0'; ALTER TABLE `mob_db2` MODIFY `Drop7id` smallint(5) unsigned NOT NULL default '0'; ALTER TABLE `mob_db2` MODIFY `Drop8id` smallint(5) unsigned NOT NULL default '0'; ALTER TABLE `mob_db2` MODIFY `Drop9id` smallint(5) unsigned NOT NULL default '0'; ALTER TABLE `mob_db2` MODIFY `DropCardid` smallint(5) unsigned NOT NULL default '0'; ALTER TABLE `mob_db2_re` MODIFY `MVP1id` smallint(5) unsigned NOT NULL default '0'; ALTER TABLE `mob_db2_re` MODIFY `MVP2id` smallint(5) unsigned NOT NULL default '0'; ALTER TABLE `mob_db2_re` MODIFY `MVP3id` smallint(5) unsigned NOT NULL default '0'; ALTER TABLE `mob_db2_re` MODIFY `Drop1id` smallint(5) unsigned NOT NULL default '0'; ALTER TABLE `mob_db2_re` MODIFY `Drop2id` smallint(5) unsigned NOT NULL default '0'; ALTER TABLE `mob_db2_re` MODIFY `Drop3id` smallint(5) unsigned NOT NULL default '0'; ALTER TABLE `mob_db2_re` MODIFY `Drop4id` smallint(5) unsigned NOT NULL default '0'; ALTER TABLE `mob_db2_re` MODIFY `Drop5id` smallint(5) unsigned NOT NULL default '0'; ALTER TABLE `mob_db2_re` MODIFY `Drop6id` smallint(5) unsigned NOT NULL default '0'; ALTER TABLE `mob_db2_re` MODIFY `Drop7id` smallint(5) unsigned NOT NULL default '0'; ALTER TABLE `mob_db2_re` MODIFY `Drop8id` smallint(5) unsigned NOT NULL default '0'; ALTER TABLE `mob_db2_re` MODIFY `Drop9id` smallint(5) unsigned NOT NULL default '0'; ALTER TABLE `mob_db2_re` MODIFY `DropCardid` smallint(5) unsigned NOT NULL default '0'; ALTER TABLE `mob_db_re` MODIFY `MVP1id` smallint(5) unsigned NOT NULL default '0'; ALTER TABLE `mob_db_re` MODIFY `MVP2id` smallint(5) unsigned NOT NULL default '0'; ALTER TABLE `mob_db_re` MODIFY `MVP3id` smallint(5) unsigned NOT NULL default '0'; ALTER TABLE `mob_db_re` MODIFY `Drop1id` smallint(5) unsigned NOT NULL default '0'; ALTER TABLE `mob_db_re` MODIFY `Drop2id` smallint(5) unsigned NOT NULL default '0'; ALTER TABLE `mob_db_re` MODIFY `Drop3id` smallint(5) unsigned NOT NULL default '0'; ALTER TABLE `mob_db_re` MODIFY `Drop4id` smallint(5) unsigned NOT NULL default '0'; ALTER TABLE `mob_db_re` MODIFY `Drop5id` smallint(5) unsigned NOT NULL default '0'; ALTER TABLE `mob_db_re` MODIFY `Drop6id` smallint(5) unsigned NOT NULL default '0'; ALTER TABLE `mob_db_re` MODIFY `Drop7id` smallint(5) unsigned NOT NULL default '0'; ALTER TABLE `mob_db_re` MODIFY `Drop8id` smallint(5) unsigned NOT NULL default '0'; ALTER TABLE `mob_db_re` MODIFY `Drop9id` smallint(5) unsigned NOT NULL default '0'; ALTER TABLE `mob_db_re` MODIFY `DropCardid` smallint(5) unsigned NOT NULL default '0';
Please correct me if im wrong.
-
Ive read so many topics about this. Including this one http://rathena.org/board/topic/79394-setup-thor-patcher/
Anyway. I cant make it to work nor i have an issue understanding this. Can someone walk me through how to set up the new version of thor?
The Thor_Patcher 2.6.4.7 or Thor_Patcher 2.6.4.8. Please while i still have remaining days to use my VPS.
Step by step please.
-
Uhm not just yet. Because the bug is still there.
-
Made another small change in 82467e1.
@gidzdlcrz
The point of the upgrades folder is so for later on, all you need to do is go to the upgrades folder and import the SQL file that was added from the commits you haven't applied yet. It avoids you having to dump your schema every time (using live or offline data). You'd still have to apply those upgrades since some tables affected are core tables used by the server. The tables that you aren't using, such as mob_db, item_db, mob_skill_db, etc can be ignored if you get errors in your case since you are using the db/ files.
@Cydh
Thanks for testing an even older client! I'm surprised it went back that far.
I dont really get it. So sorry but how can i apply the update when i only use main and log sql's? So sorry again. Im being to noob.
-
Thank you so much Aleos. yeah. Thats why im having a hard time understanding the upgrade sql files.
So in my case. I dont need to update those upgrade_20140612.sql and upgrade_20140612_log.sql as i am using db files.
-
I suggest to download a new fresh from git. Or if you dont want. get a fresh svn 17704.
-
By default all you need is main.sql. Log would be if you want to use the logging system. The rest of the stuff is not needed unless you want everything to be ran via the SQL side rather than the db/ files.
So to apply those updates from above. What i need to truncate is only the MAIN.SQL, LOG.SQL, MOB_DB.SQL, MOB_DB_RE.SQL, MOB_DB2.SQL and MOB_DB2_RE.SQL.
Those 6. Because i tried it again only importing MAIN and LOGS. Im seeing error.
And yeah you're right. I still want to run the db/files. So only those 6 sql's right?
-
Well if there are new revision for git. I always start from zero.
Out of topic.
What are the files should i need to truncate? As i am using only 1 schema now named rathena. (The reason for this was the VPS i purchased only have 1 schema) so another schema is not necessary.Besides from MAIN and LOG what else?
-
Thanks! Correct me if im wrong. So what i did was
1. Truncate all of my SQL Files. From item_cash_db.sql to mob_skill_db2_re.sql (Located at \rAthena\sql-files)2. After truncating all of my SQL files. I go to folder called upgrades and look for SQL files named upgrade_20140612.sql and upgrade_20140612_log.sql as stated above. ( Located at \rathena\sql-files\upgrades)
3. Im using MySQL Query so File > Open Script > select those updates then Execute.
Am i making sense? I see no error after doing these steps above.
Don't forget to run sql-files/upgrades/upgrade_20140612.sql and sql-files/upgrades/upgrade_20140612_log.sql!
Uhm hi. How to do this?
just execute it on your database. sameway on how you import the main.sql and log.sql
Btw i tried this. As i am only using MAIN.SQL and LOG.SQL. The update upgrade_20140612.sql and upgrade_20140612_log.sql wont complete when i click the Execute. So what i did was the step above.
-
Yep. Already saw that. And made a comment already. I dont know how to apply those sql. :/
-
Don't forget to run sql-files/upgrades/upgrade_20140612.sql and sql-files/upgrades/upgrade_20140612_log.sql!
Uhm hi. How to do this?
-
That's correct. Please don't forget to apply both of the SQL files.
Wow! Awesome! What do you mean by apply both of the sql? In offline mode what im doing it to truncate only the MAIN.SQL and the LOG.SQL. In online. I had to ask help about making my server online. As i can see he truncated all of my sql files.
So in offline mode. Should i truncate also the other sql files? Im seeing these files.
-
- Increased limit from 32,767 to 65,535.
Does is mean that i can now create a custom item starts with id 33,000? If yes wow!! Big improvements! Forgive my ignorance.
-
Maybe the TS was reffering to a sub GM which has the id number of 4. So when that id kills a mvp it wont drop any items. To prevent corruption.
-
Ditch that already. Sobrang luma na nyan at ang daming bugs. For example you use @clone @evilcone. 1 lang hp nila. Basta marami pa. Kaya i switch to git.
-
^ Already did. As Aleos already confirmed it.
About the thor Patcher i made.
in General Support
Posted
Hello friends. I just want to ask how to change the color of the characters appearing on my Thor Patcher. Instead of black. I want it to make it white. And how to add a text saying that Patch is Complete when the patching is done? Thank you!