Add Action (scripting within the walker)

[psychaos]

I really dont think the way scripts currently work within xenobot is very practical, and if im honest i find it a bit confusing. Also, if something isnt working and the script needs editing you have to locate the file and edit it in notepad. and i can see the script folder getting pretty messy as more features are added to the bot and we have several scripts saved.

I feel that it worked alot smoother in neobot, whereby you could just add an action waypoint, and write/edit the script within neobot.

I propose an "Add Action" option in the walker, which opens a text box where u can add the script right into the walker. And then a doubleclick to open the box again if it needs to be changed for any reason. No save files needed, and much easier to adjust things.

or is this not possible with xenobots design?

[Spectrus]

It may be possible. My belief, however, is that any dialogue menu that he can make inside the Tibia client would provide a poor scripting interface. Perhaps the option to "Add Script" and when added, asks you to input a path to the script. I also agree that it should be possible to edit waypoints while logged in.

[psychaos]

id take a poor scripting interface for ease of use any day.

besides, i fail to see what would be so bad about it anyway, the only thing it might lack is coloured text. the scripts would still be written in the same way surely?

[Heardy]

As far as I know there's a limit of characters you can enter into any textbox before the clients starts to lag like hell.
Not sure tho.

[psychaos]

well failing that, spectrus' suggestion is still an improvement.

[Syntax]

this isn't neobot. A different structure does not make it worse. I prefer having it read scripts from the folder. I like to have syntax coloring and honestly making an entire IDE inside the client is not something Nick should waste his time on.
If you take a look at my alternative walker I do use labels as function names so you can call functions straight from the walker. That's the closest you will get.

[Heardy]

Nevermind...

[psychaos]

please explain to me how pulling each script from a file is better? what if you need something simple like a checkposition, you have to create an individual file for 2 or 3 lines of text. take into account how many files one depositing script might use, then times that by the number of different scripts we will eventually make. how will we be able to keep anything organized within the script folder.

[Raphael]

this isn't neobot. A different structure does not make it worse. I prefer having it read scripts from the folder. I like to have syntax coloring and honestly making an entire IDE inside the client is not something Nick should waste his time on.
If you take a look at my alternative walker I do use labels as function names so you can call functions straight from the walker. That's the closest you will get.

Let's be honest, it's not the end of the world, but it's indeed worse. Separating it only makes it harder to manage and maintain. While, of course, it's probably impractical to develop something like this under the current structure, you can't take it as an excuse, but rather as a design flaw.

[Spectrus]

Syntax's system works like this. You add a label that says 'Self.Say("exura")'. That command is executed. No need for a file.