Metis 2.80

[GhostShip]

It really is Xmas Folks 

In germany we get our Christmas presents on 24th December so here is a little Christmas present:

I released Metis 2.80 Alpha 1 for public testing.

http://mxcontrol.sourceforge.net/index.php?act=dscript&CODE=showdetails&f_id=201

Metis 2.80 Alpha 1 Installer.
Metis 2.80
*********************************
- Added new conditions:
"logical non exclusive or" (||)
"logical and"                 (&&)
"is digit"                      (digit)

See the helpfile and the example scripts for more details

- Fixed a lot of documentation errors in thehelpfile (especially in the section"Operators" and updated the section"Variables" to include all variables

- Fixed %BOTRAWNAME% and %BOTNAME% bug(Carefull, might break existing scripts)
 
- Added Variable Spy dialog which displays all uservariables currently in memory and their corresponding values. Added this to help you debug scripts

- Added Parser-error dialog which displaysall parsing errors in a script (if any)

- Added new operator "readweb" which can read files via the http protocol (for example you can now read http://mxcontrol.sf.net/index.php)

See documentation and the example in operators.xml

An Update has been hoped for for some time now and here it is,  Merry Xmas to Bender, Sabine and Ella 

[KM]

he forgot to add "Default config actually has some caches in it" to the changelog - quite an important update if you ask me

[GhostShip]

I,m sure that will please many users who suffered from minor confusion on how to enter those.

[GhostShip]

Yet another update folks 


Download here.

http://mxcontrol.sourceforge.net/index.php?act=dscript&CODE=showdetails&f_id=208

Source code here ( broken at time of posting : (  )

http://mxcontrol.sourceforge.net/index.php?act=dscript&CODE=showdetails&f_id=209

Metis 2.80 Beta 1
*************************
- Fixed condition "is digit"

- You may now use %RANDOMNUM[$uservar$]%

- Added Systeminformation variables (Read the variable topic in the helpfile)

- Added additional userinfo variables (Read the variable topic in the helpfile)

- Fixed variables spy via middle mouse-button

- Added previously undocumented element <TriviaStartMessage .../> to defaultMXC.xml and Helpfile

- You can now use variables within variables (%USERVAR[$somevar$]% or %USERVAR[%LINE%]%,
    %USERVAR[%USERVAR[n]%]% is NOT allowed) Be carefull with this as this might lock or crash the bot if used incorrectly.

- Fixed several bugs related to entities in Metis. Expect always the entity form in memory (ie: &amp instead of &) <out type="file"> now handles entitiescorrect (replaces them with the corres-ponding characters). When reading from file and web the special characters arenow correctly replaced with their xml-entity.
NOTE: This might break some scripts thatdont expect XML entities in memory.

- Fixed a bug in the tinyxml parser that removed the & in front of entities used by Metis

- Fixed newline bug in <operator type="readfile">and <operator type="readweb"> when mode is set to"c"

- <out type="file"> and <operator type="readfile">do now remove illegal characters from the filename

- Added "Reload MXC.xml" button to error dialog

- You may now finally have more then 1 <OnRename> command

Cheers again and happy New Year Bender 

[Max™]

well i like it, it enters the room and auto /mxc run's faster and smoother than the 2.7 overall, it responds faster, i give it 10 out of 10 as the best metis so far.

[Victim]

Yes, its good but there are alot of people finding bugs in the new version being as it has been tested deeply. But some people have got back to alpha being as that has 1 more feature that works which beta 1 doesent. Some poeple have stuck with there 2.7 test 6 and some have stuck with 2.60. Maybe people are waiting for a solid release instead of just alphas and betas. But im gunna move on to alpha.

[GhostShip]

I suspect this is due to the developer taking over a years break from the program, some ideas seem to have been left out and other items added, hopefully this will resolve itself sometime in the future with a few more releases under his belt.

[Max™]

yep there is known bugs oin the 2.8beta, the 2.8alpha is the best one as i havent found a bug yet, its on my general bot that has 2 games in it and no problems

[James420]

I don't know about anyone else, but I got alpha one not long ago and tested it out. And it seems that I can't enter an offline room with RoboMX 2.08/Metis 2.80 apha 1. It gets some stupid error and never enters. I'm using WCS and running the room with it set to offline. Makes things a little hard to test. But I'll go home and try the beta to see if I still get the same problem. Hope it's a bug that can be fixed soon.

[Max™]

there is a problem with entering the room you host on wcs and fxs when using routers, try the loop-back method, thats how a lot of people pop metis into rooms. i also get a message when trying to enter an off-line room sometimes.

[James420]

I don't get the error sometimes. I get the error every time with the new RoboMX/Metis. I've always used the loopback address when entering an offline chatroom. I'm not new to WinMX...plus, since I don't have net. I don't have a router hooked up. So it isn't that either. I've tried everything to get it into the chatroom with no avail. Loopback in hash and IP form both give me the same error. So I'm pretty sure it is a new bug that has developed.

[Max™]

try a little test, go back to the older version, then run both, try to get in room with one then the other and see if the older one goes in without an error, then you will know its the robo/metis and not your set-up.

[James420]

Already done that, like I said...I'm no noob. I've tried everything to think of and still can't seem to figure it out. I'm going to dig through the source over the next few days and see if I can figure out where this bug would be coming from.

[]-[êll.Ôñ.ËÀR'][']-[.]

try clearing the room history on the join  simple but it worked for me 

[mimmo]

  :twisted: :roll: :| :mrgreen:

try clearing the room history on the join  simple but it worked for me 

[rob]

i`m having a problem getting onopmesssage to work with fxserv using alpha1
it don`t read my /opmsg triggers
   so far only thing that don`t work for me

[Max™]

Hi Rob
set this up as a test, the bot must be admin and it has 2 outputs 1 normal 1 admin, you should see both

Code: [Select]

<OnOpMessage type="script">
<in>test</in>
<out>test complete</out> //goes to errm
<out>/opmsg test completed</out> //is an admin message
</OnOpMessage>