SRL Archive - S.M.A.R.T.

Is it possible to play in the German Language worlds using smart?

SMART should bring up German worlds with little to no editing, BUT most scripts are made for the English language and wont work in those worlds. (Unless 100% Reflection)

Yeah I kinda forgot about the language barrier…it would be nice tho because those worlds are usually extremely empty

How empty?
Empty as in, nobody there at all?

From: Naike
How empty?
Empty as in, nobody there at all?

They generally don't go over 1k players

From: Dgby714
They generally don't go over 1k players

and also people don't go there just to train, they go there to everything. so i find that on english worlds, training spots (i.e. flesh crawlers, VEM) are the most crowded, but when i do those things legit i go on german servers - it's also a good way to get a tiny bit of German EXP!

In my personal experience, German words for botting aren't as good; the language barrier being the main problem. If you manage to convert SRL to work for Deutsch, then SMART should be able to load the world (though I am unsure).

tl;dr, it's not worth the effort to maintain both English-SRL and German-SRL. It's a novel idea that others have suggested, but it will probably never get off the ground.

From: Dgby714
They generally don't go over 1k players

lol at night it never goes over 50 players

From: doublex8
lol at night it never goes over 50 players

This. I've never seen it over about 150 in PvP worlds, actually.

And I don't think this would be too hard to do. If I have time I'll work on this.

Keep me updated if you decide to

I will work on this at some point. Just not sure when I'll get around to it.

From: Harry
it's not worth the effort to maintain both English-SRL and German-SRL. It's a novel idea that others have suggested, but it will probably never get off the ground.

Obviously no one would maintain 2 different includes for a language change, it could easily be done with no code duplication. (make a german.simba with all of the german strings defined and an english.simba with all english strings defined, then the include would just refer to variable names, this is how basically all programs handle localization)

From: moparisthebest
Obviously no one would maintain 2 different includes for a language change, it could easily be done with no code duplication. (make a german.simba with all of the german strings defined and an english.simba with all english strings defined, then the include would just refer to variable names, this is how basically all programs handle localization)

There is more to it than that… All the functions and procedures that use color counting to recognize text for example would have to be modified. (Like LoginPlayer)

From: Zyt3x
There is more to it than that… All the functions and procedures that use color counting to recognize text for example would have to be modified. (Like LoginPlayer)

We could still do what Mopar said =/ Just include the const used if those functions in the languagename.simba files. (IDK if all the functions like those use const but theu can easily be changed…)

From: Dgby714
We could still do what Mopar said =/ Just include the const used if those functions in the languagename.simba files. (IDK if all the functions like those use const but theu can easily be changed…)

True, but it will be a hell-a-lot of work to do >.<

From: moparisthebest
Obviously no one would maintain 2 different includes for a language change, it could easily be done with no code duplication. (make a german.simba with all of the german strings defined and an english.simba with all english strings defined, then the include would just refer to variable names, this is how basically all programs handle localization)

Jagex likes to change small things randomly; having more than one localization to need to maintain would make both more unstable and split the developing team.

From: Harry
Jagex likes to change small things randomly; having more than one localization to need to maintain would make both more unstable and split the developing team.

If you did it like I said it definitely wouldn't make it more unstable, and having all language-specific things in one, easy to access place would probably make it even easier to update when jagex updates. It would mean you would have to have a 'german team' to update that file, but that's all the extra work we are talking about.

From: Zyt3x
True, but it will be a hell-a-lot of work to do >.<

not really, if the english version of runescape gets updated with something that would vary by language, odds are that it changed in the german version too.

There really wouldn't be any changes to language.. >_> In all of it's history, it's usually small things every few months-years and it's usually stuff like "axe" to "hatchet."

From: TomTuff
not really, if the english version of runescape gets updated with something that would vary by language, odds are that it changed in the german version too.

Why is that a good thing?