Stop misusing config.txt's block format

[hakore]

Better ask isieo...

[isieo]

ok i think we are all getting confused,

what i mean is we keep this feature untill the last day of the current stable, when we release the new stable version, it will not have the {} teleport blocks in the code base, this way we can put up a huge notice here in the release page saying that the {} is not supported anymore and we reverted it back to the _. what we should do now is to replace the {} in the svn's config.txt with _ so that new svn user uses _.

any better ideas?

[hakore]

Oh, I mistook what you said earlier as "knock off the code AFTER the next release".

Anyways, I already took care of README.txt and config.txt in SVN.

I guess this satisfies Cozzie's query? Although, I believe Cozzie proposes that the code be knocked off "right now".

[Cozzie]

Yes hakore, since we are going to release 2.0.6 soon. Why not just tie up lose ends and revert the changes now fully and if preferably introduce the new style of using square brackets for non repeatable configs. This way we kill two birds with one stone by having only to migrate once when 2.0.6 stable is released.

I dont mind either way imo.

[Mushroom]

Ressing the topic, I hope it's not a problem lol

Is the square brackets configs going to be released in the future?

[survivorsavior]

Can we have multiple teleport blocks?

like;

Code: Select all

teleportAuto_useSkill 1
teleportAuto_equip_leftAccessory
teleportAuto_equip_rightAccessory
teleportAuto_idle 1
teleportAuto_portal 1
teleportAuto_search 1
teleportAuto_onlyWhenSafe 1
teleportAuto_allPlayers 1

use skill teleport for non risky situations.

Code: Select all

teleportAuto_useSkill 0
teleportAuto_hp 20
teleportAuto_minAggressivesInLock 4
teleportAuto_maxDmgInLock 3233
teleportAuto_deadly 1
teleportAuto_attackedWhenSitting 1

use fly wing on risky situation,
aggro > 3 AND hp less 20% = tele

Code: Select all

teleportAuto_useSkill 0
teleportAuto_hp 90
teleportAuto_minAggressivesInLock 6

customized on different HP and aggros and perhaps other possible variables,
aggro > 5 AND hp less 90% = tele

Code: Select all

teleportAuto_useChatCommand @jump
teleportAuto_allPlayers 1
teleportAuto_atkCount 0
teleportAuto_atkMiss 10
teleportAuto_unstuck 1
teleportAuto_lostTarget 0
teleportAuto_dropTarget 0
teleportAuto_dropTargetKS 0

[Mushroom]

I think you can change this using doCommand or macros.

[survivorsavior]

Does docommand supports;

teleportAuto_deadly
teleportAuto_portal
teleportAuto_allPlayers
teleportAuto_atkCount
teleportAuto_atkMiss
teleportAuto_attackedWhenSitting
teleportAuto_lostHomunculus

and other probable future exclusive features to teleport block?
theres still many possible workaround to enhance teleportblock. Like auto use fly wing if tele triggered, but skill delay on action.

[Scarya]

http://wiki.openkore.com/index.php?title=DoCommand
http://wiki.openkore.com/index.php?titl ... Conditions

Read it!

[Mortimal]

But u can always add conditions to source code... On tima I addes condition afterSkill to self conditions...