Allowing the entry field to be changed about keira3 HOT 3 OPEN

it's a bit hard to do, so for now we did not implement it
this feature request has been alreadu reported here #25 so I am closing this issue

thanks anyway for the report

from keira3.

it's a bit hard to do, so for now we did not implement it this feature request has been alreadu reported here #25 so I am closing this issue

thanks anyway for the report

Can you explain a little why this would be hard to do?
All that is needed is the ID to be editable. SQL will take care of the rest.

The ID not being editable forces the user to have to copy the already made code by hand, edit the ID by hand, and run it in an HeidiSQL by hand. This seems weird as Keira3 was made to not have to do that.

from keira3.

Reopening this and editing the title. Allowing the entry to be changed is a separate feature request than a full entity copy.

But be aware that allowing the entry to be changed may easily lead to an inconsistent state of the editor.

However, if you know what you are doing, I don't see a problem allowing it.

The reason is the same for

Can you explain a little why this would be hard to do?

The reason that the full copy is hard to do is because you have to sync all dependant tables.

For example, if you chance creature_template.entry you need to also sync all other tables that point to that value, e.g. creature_template_addon and so on. If you know what you are doing and you manually do it, I don't see any problems in allowing you to do it. Otherwise, you might just mess up things.

I'm not considering allowing this feature behind some kind of "I know what I'm doing" toggle, but this needs a second look.

from keira3.