Desu

You already have the english versions of those files. ns_strings_zh.xml == IRB_0_en.xml ns_strings_zh_storyline.xml == IRB_1_en.xml ns_strings_zh_platinum.xml = CPU_0_en.xml strings_zh_dump.xml == BPE_en.xml strings_zh_dump.xml == BPR_en.xml

We can only include translations of the data/strings/strings_en.xml file. We cannot include dumped strings in the official PokeMMO client. This is done from our translation project located at translate.pokemmo.eu. We only accept fluent contributors, who do not rely on machine translation services.

That string is in IRB_0_en.xml. Please just search the files for what you need.

The first 5, are each rom's language files. You will need to translate these to entirely translate all parts of the game. You will need to edit them and change the language code at the top of the file. You should also use the normal strings_en.xml from the data folder as the base. Not the dumped strings_en.xml.

Tomorrow™

Make a ban appeal on https://support.pokemmo.eu and wait for it to be answered. There is nothing you can do to speed up this process.

Match manipulation is against the rules and is enforced equally to all players. It's a busy time of the year for all of us, and sometimes mistakes happen in report processing. We will do our best to fully investigate this report and handle it soon. Donations to the game do not give special treatment on rule enforcement.

I'm proud of you

There should be nothing modified with the random status effect rate. One factor is that it matters a lot more here than on vanilla difficulty so you notice it more.

Bug Fixes Fixed an issue with moves showing as hitting multiple times. Possible fix for sounds playing during other sounds when music is disabled. Fixed an issue related to reconnecting during team preview.

This is not feasible due to the cost of machine translation services.

Dude basically the whole game is PvE

It should be fixed sometime later today.

Ah darn, I finally got time to look into this and it was missing the +25% leeway for the initial yellow warning. It was showing yellow if it's just $1 above the valuation. This should be fixed with the latest client update.

Changelog: 23/09/2021 Bug Fixes Seasonal vanity items will now use the correct blue icons again. Fixed darkness overlay in GBA regions. Fixed incorrect badge signup requirements for randoms. Added 3x GBA Zoom Level option to android. Fixed incorrect GTL coloration level. (Items were showing as yellow before they were supposed to)

No, GTL only.

The prices are 100% based on completed sale prices (not unsold listing prices). There has been no manual effort in dictating the valuation. If people are willing to pay a higher price, the level at which the yellow/red prices start to show warnings will increase. The colors only indicate that the price is higher than what the item typically actually trades for. If you feel like a price is worth paying when it's yellow or even red, there's nothing stopping you. We may have to do some adjustment to lower-priced items to give them a higher acceptable range before showing yellow, but these colors follow the price, not dictate it.

The price dictates the colors. If the price of an item raises, so will the level at which the colors apply.

This issue happens with a lot more items than the RP voucher. And we're actively taking steps to prevent it both already on live and in next update. This thread's not helping anything, so going to end it here.

Ah, I see what we did wrong. Should be fixed for next update and includes more detailed context. Example with 1 brace:

Alright, this thread's been answered. Going to leave it outside of trash so people can find it if they need it, but locking it.

There's nothing to add or document, it's the standard gen3/4 catch rate, which is almost identical to gen5's as well. The few changes we made to ball rates are already documented.