Zone Information Script Re-write

[bjcasey]

Short Forms:

Zone Information Script = ZI
Quest Bot = QB

Purpose:

Helps Quest Bot know what type of zone it is in. QB uses it when it completes a QB file and needs to change zones. ZI is also used for personal statistics and keeps track of how many times the last boss of a zone has been killed by a particular character.

Current Usage:

I enter information about a zone (zone name, zone type, number of connected zones and their type, where to find those zone connections, zone door number, minimum lockout, maximum lockout, and final boss name) into an included file. This file is then encrypted inside of the extension.

Future Usage:

Same as above, but the file isn't encrypted. I will add the "default" file to the patcher and it will be updated as I add zones. In addition to the default file, a one time patch "custom" file will be added to the patcher. Users will be able to add this information themselves using the following command: BJ ZI Setup

Help Needed:

Thinking about the TLE servers (although this would apply to all servers), what other information should be included about a zone? Should another entry be added to track hard lockout zone versus soft lockout (persistent) zones?

I am currently working on updates to this script and would really like feedback on how people would use this script.

 

[fireopal]

Some zones that are not persistent and when you are locked they have the message box that pops up are you sure you want to leave? Yes/No I imagine this could be included automatically if zone isn't persistent.

If you just make one lockout timer per zone and persistent ones just use the short lock out and not persistent use the full lockout.

Maybe the option to zone into something that is not a good normal door. Like an item name.

Is there a way to include a way to choose an agnostic zone in through the ui?

 

[bjcasey]

Some zones that are not persistent and when you are locked they have the message box that pops up are you sure you want to leave? Yes/No I imagine this could be included automatically if zone isn't persistent.

If you just make one lockout timer per zone and persistent ones just use the short lock out and not persistent use the full lockout.

Maybe the option to zone into something that is not a good normal door. Like an item name.

Is there a way to include a way to choose an agnostic zone in through the ui?

1) So you want to be able to flag an instance as persistent? TRUE/FALSE
2) Zone Actor Name is already a parameter. It will double click the actor name.
3) Agnostic zones can already be zoned into by going to the LAD zone in actor in Qeynos and Freeport.

 

[fireopal]

1) Yes and have QB handle the zone out message / reset automatically
2) perfect
3) oh i didnt think about using that. good idea

P.S. i know we talked about this before but being able to choose which door number for zone in because some zones change depending on level and flagging

 

[bjcasey]

1) Yes and have QB handle the zone out message / reset automatically
2) perfect
3) oh i didnt think about using that. good idea

P.S. i know we talked about this before but being able to choose which door number for zone in because some zones change depending on level and flagging

So the way that I have this working is, I create a zone info default file. I choose the door option number that makes sense for MY characters (I"m selfish like that). However, you can use the same script I use, except in your case it will create a custom zone info file. In your file you could change the door option number for YOUR characters. Zone Information checks for the existence of a custom file before loading the default. If a custom file is found is skips loading the default and loads the custom file.

 

[fireopal]

perfect i would rather there be a default as its less work for me and have the option to overwrite the specific zone info file as long as its only for that specific zone. when you update the default zone as you add new zones i dont want to have to update the custom one

 

[bjcasey]

perfect i would rather there be a default as its less work for me and have the option to overwrite the specific zone info file as long as its only for that specific zone. when you update the default zone as you add new zones i dont want to have to update the custom one

Right. I will patch out a default file for each zone, but while you wait for it or if you want to change something you can use the custom file. If at some point you want to use the default instead, delete or rename your custom file for that zone.

 

[bjcasey]

Update:

I was able to filter out numbers from instances. This should allow it to recognize that Maldura is the same zone as Maldura 2.

The Developer Mode checkbox in the top right won't be visible/usable by people other than me. It was just an easy way for me to allow myself to write to a default file instead of a custom file. All other users will write their own information to the custom file for a zone. This allows me to keep a default file up to date on the patcher, without it messing up someone's custom file. Custom files are never downloaded from the patcher and must be maintained by the user if they can't wait for me to add a default file.

Example of an Overland zone:

Overland zones keep track of how they connect to other zones. It does this by knowing the following information:

Parameter 1: Zone Name
Parameter 2: Zone Door Number (Can be 0 if there isn't a door option)
Parameter 3: Zone Door Location (echo ${Me.ToActor.Loc} when right next to the zone door location)
Parameter 4: Zone Door Actor Name (echo ${Me.CursorActor} with your cursor over the zone door actor)

(NOTE: I just noticed that I should have had a zone connection to the overland zone, Thalumbra.)

Example of an Instance zone:

Instance zones (solo, heroic and raid) keep track of the specific zone attributes, such as:

Boss Info
- P1: BossName (Used to track the number of times a particular boss has been killed, provided that when the mob dies it uses the chat text "killed MOBNAME")
- P2: Boss Order

Minimum Lockout (In seconds)
- P1: Duration

Maximum Lockout (In seconds)
- P1: Duration

Zone Exit Location

Zone Exit Actor Type

Zone Exit Actor Name

Zone Is Persistent
- P1: TRUE/FALSE

Quest Bot Default Quest Name (Sets the 1-Click-&-Go quest name to use for the instance)

Based on the information above, am I missing something important? Does this look like it might be easy enough to use? Zone Connections and Zone Attributes are entered using a wizard that prompts you to enter the information and a console that provides you with examples of what you might want. I'll upload a picture of the wizard once I finish updating the console text.

 

[blammo]

Awesome, looking forward to the changes, thank you!

(Hopefully the Algorithm script gets released too...)

 

[bjcasey]

Awesome, looking forward to the changes, thank you!

(Hopefully the Algorithm script gets released too...)

Algorithm isn't likely to get a script because the last named can't have the portals read by ISXEQ2.

 

[blammo]

Algorithm isn't likely to get a script because the last named can't have the portals read by ISXEQ2.

Not sure why not.. it's not uncommon for scripts ( in the past ) to require user intervention.. Would be nice to have the rest of the zone done, and only have drive the last fight.

 

[bjcasey]

Not sure why not.. it's not uncommon for scripts ( in the past ) to require user intervention.. Would be nice to have the rest of the zone done, and only have drive the last fight.

I'll consider it. Lately, people have been wanting full zone automation that can be looped and if I can't loop the zone because of needing the user to complete a fight, it makes things more annoying.

 

[Loppy]

Not sure why not.. it's not uncommon for scripts ( in the past ) to require user intervention.. Would be nice to have the rest of the zone done, and only have drive the last fight.

Personally I don't see the benefit of adding new scripts for ToT zones that are largely trivial now.

The focus should be on Zek Keep as its such a PITA with firstly the new names and secondly getting around the place with the ladders and what not.

Just my penneth worth!

 

[blammo]

Two thoughts:

1. Not everyone is willing to pay for gold status & GU100 content. It's false assumption that all Ogre/BJ subscribers are only doing GU100.. in fact, given the cost increase of running 6xGold accounts....
2. Especially with the advent of Ethereals, we're having to re-run zones all through ToT... and the two from today, for example, don't have bj quest entries.. wish they did.

 

[bjcasey]

Two thoughts:

1. Not everyone is willing to pay for gold status & GU100 content. It's false assumption that all Ogre/BJ subscribers are only doing GU100.. in fact, given the cost increase of running 6xGold accounts....
2. Especially with the advent of Ethereals, we're having to re-run zones all through ToT... and the two from today, for example, don't have bj quest entries.. wish they did.

I'm really working as fast as I can on the Quest Bot, Loot Manager and Zone Information scripts re-writes. I have "people" working on converting the existing QB scripts over to the new system and "other people" working on new zones. There is still not an ETA for release, but we are working as fast as we can and I feel that it will be worth the wait.

 

[blammo]

...

3. Not everybody cares about loops. Some of us just want to be able to run the daily/weekly/etc, collect the coins, and be done.

Thank you sir, much appreciated. Looking forward to quest updates.

 

[eddie43302]

if your botting and not gold your doing it wrong... you can make millions of plat per week. hell even per every other day.. no need not to be a gold member..