Foreign worlds botting

[Nava2]

Uhm, I don't think Simba has troubles with Caps.. I thought that was a SCAR issue? I could be wrong though.

[i luffs yeww]

It may have been SCAR. I don't remember. I just know that for awhile it was advised to avoid caps.

[KingKong]

well get uptext works with caps though sometimes it has troubles telling the difference between I and 1 and things like that.

[i luffs yeww]

Well I may just skip over capitals and "foreign" characters.

[Flight]

@KingKong: I can't really think of too many places where a number would be included in the UpText or any text, aside from withdraw/deposit.

@i luffs yeww: I noticed some of those 'special' characters in foreign words were usually in the middle of the word itself, so if I'm predicting correctly, skipping over special characters would, in most cases, limit you to trying to find around half of the word you're searching for, would this not be inaccurate?

[i luffs yeww]

By skipping over them I mean having a wildcard. If it gets most of it, and your language is set right, it's probably right.

It would be just as accurate really.

[KingKong]

@KingKong: I can't really think of too many places where a number would be included in the UpText or any text, aside from withdraw/deposit.

@i luffs yeww: I noticed some of those 'special' characters in foreign words were usually in the middle of the word itself, so if I'm predicting correctly, skipping over special characters would, in most cases, limit you to trying to find around half of the word you're searching for, would this not be inaccurate?

The number isn't included in the uptext, sometimes when the uptext is too long(eg: superheat iron ore) or some random error it thinks the i/I is 1 and gives random stuff like '^' for spaces.

[i luffs yeww]

The number isn't included in the uptext, sometimes when the uptext is too long(eg: superheat iron ore) or some random error it thinks the i/I is 1 and gives random stuff like '^' for spaces.

Reminds me why I don't like how text finding is done currently.. Not like the OCR needs to be better (I understand it's difficult), but other stuff.

[Zyt3x]

Zytex, for awhile capitals were told to stay away from. So people stuck with that. I don't see why you'd want to slow it down, even if by an amount that wouldn't be noticeable, so I don't see why you're against this..

And why does it matter if people use 'obster' instead of 'Lobster'? Why does that make them lazy? :x

Still.. I don't see why you're against this.. :/ It won't affect anyone who doesn't use it..

Woah, I didn't see this post until now...

I'd rather like it to be a good function but 0.5ms slower, than having a dysfunctional function that is 0.5ms faster.

Because using "lobster" is the correct way to do it, and there is no other reason why they shouldn't

I'm not against the idea at all. Just the way you're doing it

[i luffs yeww]

I don't understand why you're against this at all.. :/ And by this I mean my idea.

Just as a few examples as to why I want it to translate the German word of "lobster" when Translate("obster") is passed.. (From Emaziz's application)

if not ClickText('aw','UpChars',MSX1,MSY1,MSX2,MSY2,true) then

TYPE_LURE: option := 'ure';
TYPE_BAIT: option := 'ait';
TYPE_NET : option :=  'et';

Those wouldn't work if this was added how you want to do it.. And those are all of the text finding things I can find from a quick glance. So his script wouldn't work if we did it your way, but would work if we did it my way..

And if it matches a whole word it will obviously use that first.. It would check them in order of % matched.

[Zyt3x]

And what do yo think Translate('et'); would make 'et' into before translating?
I found 70 results on this page http://www.tip.it/runescape/?rs2item, and that's only for A.
How would the script know which one to pick? That sounds like a awfully (unnecessarily) long and complicated function for me, with a lot of useless code.

Using what I want (to rely on the scripter to enter correct information) such errors would not happen. Translate('Net'); would translate 'Net', and 'Net' only.

[i luffs yeww]

But then most people would have to rely on the scripters to add this, when that's silly imo. And would be tedious for them.

I don't see how it would be complicated? :x

[Zyt3x]

But then most people would have to rely on the scripters to add this, when that's silly imo. And would be tedious for them.

I don't see how it would be complicated? :x

No, they'd just have to rely on the scripter knowing what he's doing (and not entering 'ow' intead of 'bow')

[footballjds]

No, they'd just have to rely on the scripter knowing what he's doing (and not entering 'ow' intead of 'bow')

and i think if this takes off and ends up working scripters here can do their part to use an include like this!

[Echo_]

I'm starting to think the entire word should be required in order to translate, just because there are so many translation possibilities for commonly used suffixes and word endings.

[Zyt3x]

I'm starting to think the entire word should be required in order to translate, just because there are so many translation possibilities for commonly used suffixes and word endings.

Exactly. There's so many possibilities for false results

[Ogre]

There could be an option to look for partial matches, and you can check the most similar word with something like

function SimilarStrings(s1, s2: string): Extended; 
begin                                              
  if (Pos(s1, s2) > 0) then
    Result := (Length(s1) * 100.0)/Length(s2);
end;

and see what the highest result of this function is with different s2's
and do an SRL_Warn or something if a partial match had to be looked for, if there wasn't a perfect match (of course it would only do this if the option to check for partial matches was set)

and make sure there's a minimum similarity percentage for a partial match to be selected

[Zyt3x]

MMouse(50, 50, 4, 4);
if(IsUpText('aw lobster'))then //See, Zyt3x? People don't use full words 100% of the time. ;D
//begin
//  GetMousePos(x, y);
//  Mouse(x, y, 0, 0);
//end;
  Mouse(50, 50, 4, 4, True); //Take this out if you remove the comments, obvi.

*sigh* I know they don't but they should do, but

And what do yo think Translate('et'); would make 'et' into before translating?
I found 70 results on this page http://www.tip.it/runescape/?rs2item, and that's only for A.
How would the script know which one to pick? That sounds like a awfully (unnecessarily) long and complicated function for me, with a lot of useless code.

Using what I want (to rely on the scripter to enter correct information) such errors would not happen. Translate('Net'); would translate 'Net', and 'Net' only.

[footballjds]

I think if this include builds a bridge between english and other languages scripters can get off there lazy ass and atleast put in the correct words

[i luffs yeww]

I'm starting to agree now.

[Echo_]

Btw, we won't be able to do much until we refactor SMART for multi-language support. I made a script to run in a Portuguese world on the webclient, but apparently the game "flashes" and causes Simba to deselect the client (according to Coh3n.).

[i luffs yeww]

Btw, we won't be able to do much until we refactor SMART for multi-language support. I made a script to run in a Portuguese world on the webclient, but apparently the game "flashes" and causes Simba to deselect the client (according to Coh3n.).

If it's done right it should be just fine. In SMART, at least.

[Echo_]

It's too bad that this project died so early considering what we could gain from it.

I was bored, so I made a simple base for the include that reads translation data from .ini files. I already added full support for item name translation, now objects and NPCs are what's left.

[i luffs yeww]

Wouldn't something like

function Translate(name, lang, category: string): string;
begin
  Result := ReadINI(lang, name, IncludePath + 'lib/' + category + '.ini');
end;

work just fine for Translator.simba?

[Echo_]

Wouldn't something like

function Translate(name, lang, category: string): string;
begin
  Result := ReadINI(lang, name, IncludePath + 'lib/' + category + '.ini');
end;

work just fine for Translator.simba?

lmao yeah. Sorry, I was tired

function Translate(name, lang, category: string): string;
begin
  Result := ReadINI(Capitalize(lang), name, IncludePath + 'flrl\lib\' + Capitalize(category) + '.ini');
end;