Hercules using GIT now, not SVN anymore i believewhen i asked you i didnt know the difference of svn. but now i downloaded the latest hercules and now setting it up.. but the guide i saw was too confusing for me because it was my first time making private server
oh i didnt know the difference of it . but i already obtained the updated hercules . no wonder the setting up was very different in svn.. thank you sir !!!! i cant wait to try your costumesHercules using GIT now, not SVN anymore i believewhen i asked you i didnt know the difference of svn. but now i downloaded the latest hercules and now setting it up.. but the guide i saw was too confusing for me because it was my first time making private server
http://herc.ws/board/topic/152-obtaining-hercules/
Hi zack, is it possible to get this in pre-renewal?np
haha the costumes is not mine
it just a db lol
It is possible if you take them from the renewal item_db. Since they don't have any effects they should be able to be implemented for pre-renewal too (double check them to be sure though).Hi zack, is it possible to get this in pre-renewal?np
haha the costumes is not mine
it just a db lol
Lol. it sounds easy but it is merged with the item_db at random lines it would be better if it was separated at least and grouped.It is possible if you take them from the renewal item_db. Since they don't have any effects they should be able to be implemented for pre-renewal too (double check them to be sure though).Hi zack, is it possible to get this in pre-renewal?np
haha the costumes is not mine
it just a db lol
Currently working on the addition of renewal items to pre-renewal db, it's a horror but someone has to do it.
It is more logical that it's done by order of item ID, which is done now. However a chronological order of implementation wouldn't be bad for purposes like this. However, if you want it, you'll have to just sit those 3-4 hours comparing the two databases and merge changes. I'll be doing the migration for the whole renewal database to pre-renewal and not just the costume items. Just the costume items probably is relatively easy to do, I think it's within the item ID range of like 19k-23k or something? Which is done quite fast.Lol. it sounds easy but it is merged with the item_db at random lines it would be better if it was separated at least and grouped.It is possible if you take them from the renewal item_db. Since they don't have any effects they should be able to be implemented for pre-renewal too (double check them to be sure though).Hi zack, is it possible to get this in pre-renewal?np
haha the costumes is not mine
it just a db lol
Currently working on the addition of renewal items to pre-renewal db, it's a horror but someone has to do it.
That would be great, and yes I agree with you it is supposed to be on that order.It is more logical that it's done by order of item ID, which is done now. However a chronological order of implementation wouldn't be bad for purposes like this. However, if you want it, you'll have to just sit those 3-4 hours comparing the two databases and merge changes. I'll be doing the migration for the whole renewal database to pre-renewal and not just the costume items. Just the costume items probably is relatively easy to do, I think it's within the item ID range of like 19k-23k or something? Which is done quite fast.Lol. it sounds easy but it is merged with the item_db at random lines it would be better if it was separated at least and grouped.It is possible if you take them from the renewal item_db. Since they don't have any effects they should be able to be implemented for pre-renewal too (double check them to be sure though).Hi zack, is it possible to get this in pre-renewal?np
haha the costumes is not mine
it just a db lol
Currently working on the addition of renewal items to pre-renewal db, it's a horror but someone has to do it.
We use essential cookies to make this site work, and optional cookies to enhance your experience.