I am starting to work with the flash client coder to get a new version ready to go. I doubt many of you use flash as it is a bit more of an entry level client, but I would like some help with this. Jump on the client for a bit, run around, play with the features, etc.

If you are aware of any bugs or if you have any feature suggestions PLEASE post them here or email me directly at jeremy@ironrealms.com.

Thanks for your help!

First problem the inabilty to easily add Keybindings.

Second thing is that we can not copy paste from the window. Makes logging impossible unless someone decides to manually type out thier logs.. not fun

I think it would be very nice if it could catch the Client.Compose ATCP message and pop open the editor window accordingly. A compass would also be nice, but I don't think there's any room

I agree, keybindings are a problem. However, you can copy from the screen, you just have to double-click on it to pull up a selectable version. Then just click on the "normal" part of the screen to go back. However, this is a pain. I only use it for getting trigger messages, or looking back in the history. You can also go to logging under settings. I don't feel like the buffer is long enough however.

Some weirdness, when you open the editor and click cancel, I get some random spam messages like "I don't understand" and at the end I shake my head. So it appears the editor is feeding lines into the game.

Specifically, *quit and no. It's not smart enough to know whether or not you're actually in the composer.

lol

that makes sense. I figured it was something silly like that.
Actually, I was having a fun time just using the built in achaean editor to do my writing.

A variable tab in the settings thing would be nice as well. And maybe a button that opens the manual too.. I hear there is one But I can never seem to find it. And before anyone posts a link to the youtube viseos on it.. they are not all that helpful. very limited in showing what it can or can not do

I'd find it really useful if there was a pop out editor like there was/is on Nexus.

Hit the Editor button on the left side when you've stepped into the composer. It doesn't automatically come up, but it does exist.

The button for the help is in the settings tab, it's labeled "Help". Those videos are really the only help files it has (at least that I've been able to find). Try looking up a java-script tutorial (which is not the same as java). Look at a regexp tutorial, too.

Other than that testing things out works well. Variables have to be declared every time they are used. Variables can't store data between sessions (unless I'm missing something). It would be nice if they could (or at least stay declared).

I'd also like to see the bug fixed where if you move too quickly between maps it fails to load one until you leave the map and come back. Gets rather annoying when popping through places like NoT.

There is an option that will allow you to export the buffer into a html log, it's in the settings bit, so you don't have to manually type ou the logs

You can also double click on the buffer to get a copyable screen. Double click again underneath that screen, on the buffer, to make it go away.

Since it was only mentioned in passing, really...

Proper documentation (in-game and a webpage linked to the client itself) would help a lot.

And stored variables, please.

Flash seems to have a tendency to miss a lot of triggers if they happen quickly. Such as when you walk into a totem.
or is this a problem with my triggers?

Add keybindings, stored variables, and UNLIMITED TRIGGERS.

The current achaea flash client has only 100 trigger slots i think.

.. You wouldn't be able to make a combat system with just 100 triggers, that alone makes it nearly completely unusable for combat

It might be able to be used if it was pretty fast though so you could manual

I don't know where you got this number...but I just made a whole bunch of empty triggers and got to like 500. then I got bored with clicking. So I don't think there is a limit. Other than your computers memory. My proto-system has like uh...200ish triggers, and mostly works (but that has nothing to do with a limit on the number of triggers, more like a limit on the time I've spent on it).

The current maximum is 500 each of aliases and triggers.

No matter the case, it needs UNLIMITED memory for thousand's of triggers and aliases and everything!

A late post, but my suggestion is pretty much this: Make a list of Nexus's features, and then if they aren't in the Flash client, add them. (for example, I don't believe the Flash client lets you sort triggers in the way Nexus does, allowing you to turn classes of them on or off, as well as making it easier to find the triggers you're looking for)

I need some help. Due to circumstances (nexus my favorie no longer wants to work for me even with my java updated) I have started using flash. Now, I've figured out how to move all my antitheft and such. Except for my armour, I have tried every variable I can think of to wait unil I regain balance to wear the armour. It just doesn't work. So I had to do somehing that annoys the - out of me. I se it up so that whenever I regain balance from anything I wear my armour. So I see you are already wearing this item quite alot. Is there anyone who migh know a time wait variable for flash that I don't?

Well, you could just set up an alias "set" that sets the value of armour to 1. Then everytime you log on you just do SET and it will know you are wearing your armour. You could also have a trigger catch the "blah blah armour" line in II WEAR. And just have that fire from something right when you log in. Like, the "System announce" line or something. That trigger will send ii wear and and if you are wearing your armour it will set the value to 1. Then when you regain balance do:

if (armour == 1)
{
Send("Wear armournum")
}

That was the problem right?


EDIT: That doesn't seem to be working. I must no understand the matching engine in flash.

This is the easy solution, it would be possible to make a work around that would do everything automatically, but because variables aren't stored between sessions, it's a pain. So everytime you log in you have to do setarmour so it knows if you have armour or not.

Trigger One
Pattern:
^.+ whateveryourarmouriscalledhere //matches to the ii wear menu

send:
armour = 1
disableTrigger('armourtest') //so it doesn't keep firing

name:
armourtest

Alias One:
pattern:
^setarmour$

send:
enableTrigger('armourtest')
send('ii wear')


make sure regexp, script, and enabled are check for the above.

and switch to mush.

Make an alias to set all startup variables, update it whenever something changes?

Yeah, that's basically what I did when I was using the flash client. But since I don't know how he has everything set up I didn't want to confuse him. Although he must have something like that, because otherwise nothing would work every time you logged on. Actually the whole reason for the strange trigger thing was a holdover from he trying to think of a way to make it totally automatic, you could do it, just on qq enable the prompt matching trigger to redo your startup variables. Then after two times you would have to have it self-disable. (two times because you get a prompt line after qq)

Trevize: I couldn't get any of the system messages/startup messages (ie, "welcome to achaea" and and adminmessage) to match, why was that?

@Damen: Just add the armour variable to whatever method you use to declare your variables for balance and equilibrium and afflictions.

Sorry, I don't know FMUD at all.