Jump to content

Recommended Posts

 

 

np

 

haha the costumes is not mine

it just a db lol

 

Hi zack, is it possible to get this in pre-renewal? 

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).

Currently working on the addition of renewal items to pre-renewal db, it's a horror but someone has to do it.

 

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.

Share this post


Link to post
Share on other sites

 

 

 

np

 

haha the costumes is not mine

it just a db lol

 

Hi zack, is it possible to get this in pre-renewal? 

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).

Currently working on the addition of renewal items to pre-renewal db, it's a horror but someone has to do it.

 

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 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.

Share this post


Link to post
Share on other sites

 

 

 

 

np

 

haha the costumes is not mine

it just a db lol

 

Hi zack, is it possible to get this in pre-renewal? 

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).

Currently working on the addition of renewal items to pre-renewal db, it's a horror but someone has to do it.

 

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 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.

 

That would be great, and yes I agree with you it is supposed to be on that order.

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...

×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.