Being that it was a recommendation, and not a rule, the author can write a note to the reviewer explaining that they decline to Universalize the expressions, and take their chances that customers won’t have issues.
Just as long as the project isn’t currently generating errors with the English version of Ae, we’ll accept it for sale.
Running Expression Universalizer isn’t necessarily a requirement for approval, but we HIGHLY recommend it. Expressions sometimes don’t translate properly through the different language versions of Ae (English, German, Japanese, etc.), which can generate errors and cause the project to be unusable.
As the review note says:
“it is recommended that your project’s expressions be universalized using the “ExpressionUniversalizer” script”.
Therefore, this isn’t an “unwritten rule”, but a highly-recommended suggestion. The reviewer was only trying to help you.
If customers experience problems with your scripts, we’ll have to disable your item until you can resolve the issue, which may stifle sales at the very beginning of your project release… that’s not something you want to experience.
If you’re going to use expressions in your projects, as the author, it’s only in your best interest to Universalize them for your customers. It cuts down on possible errors and future support questions that you’ll have to field.
If we approved only 2-5 projects per day, your projects would be sitting in the queue for months!
The best thing every author can do is work on “searchability” of their items and concentrate on better promoting their overall portfolios. Writing good item descriptions and using descriptive tags helps customers who actually search for items instead of browsing through a few easily accessible pages.
Relying on exposure from the front page or New Items page is never a good long-term solution.