shop_LockOnly breaks default behaviour

[EternalHarvest]

That's an important default where you won't open (with shopAuto_open only, opening shops in general wasn't restricted) shop in a wrong place.
(Adding shop_LockOnly 1 in distributed config won't resolve that.)

Also poorly named option for many reasons.

http://openkore.svn.sourceforge.net/vie ... threv=8118

Why such option is need at all? What's the situation where you want to open your shop automatically (not with console command etc), and at the same time to keep lockMap configured to another map? Does it work at all, wouldn't navigating to lockMap have priority over shopAuto_open anyway?

[Kaspy]

[EN]
I regret for having created it and do not know why I did it... I think it was not very well head.

It also has other functions config.txt that would not be very good being there, as removeActorWithDistance.

[PT-BR]
Eu me arrependo por ter criado isso e não sei porque fiz isso... Acho que não estava muito bem da cabeça.

Também tem outras funções do config.txt que não seria muito bom estarem lá, como o removeActorWithDistance.

[EternalHarvest]

I regret for having created it and do not know why I did it... I think it was not very well head.

If you think that it's not needed, we can just revert these changes.

It also has other functions config.txt that would not be very good being there, as removeActorWithDistance.

This one doesn't break existing behaviour by default, doesn't do anything by default, disabled in distribution and wiki explains what it was intended for. There are a lot of options like that which just do nothing by default.

Currently, it may be less useful for new servers (as many other options are) and/or overshadowed by clientSight (but not totally useless if you're trying to reduce CPU and memory usage by all means). If anything, it should be investigated further / added to bug reports / explained in wiki.

It could have been a plugin instead, but you can say that for many other features as well.

[catcity]

I actually have a half finished plugin where this config option might be applicable.

The concept of the plugin is that in between vending the merchant would carry out other automated tasks that would require him to move out of the lockmap. At times it might be necessary for the merchant, while not at his lockmap, to wait for some other event and in that downtime I don't want him opening up a shop wherever he is.

This could be handled within the plugin though. Not as a generic config option.

[Kaspy]

Removed
http://openkore.svn.sourceforge.net/vie ... ision=8304

[alicia45]

I actually have a half finished plugin where this config option might be applicable.

The concept of the plugin is that in between vending the merchant would carry out other automated tasks that would require him to move out of the lockmap. At times it might be necessary for the merchant, while not at his lockmap, to wait for some other event and in that downtime I don't want him opening up a shop wherever he is.

This could be handled within the plugin though. Not as a generic config option.

Same issue was with me, I have handled this within the Plugin though, but no result.. Please help me.

[Kaspy]

I actually have a half finished plugin where this config option might be applicable.

The concept of the plugin is that in between vending the merchant would carry out other automated tasks that would require him to move out of the lockmap. At times it might be necessary for the merchant, while not at his lockmap, to wait for some other event and in that downtime I don't want him opening up a shop wherever he is.

This could be handled within the plugin though. Not as a generic config option.

Same issue was with me, I have handled this within the Plugin though, but no result.. Please help me.

I did not ... The function shop_LockOnly has been removed. This updated with OpenKore?