Localizations (stupid)

For it works this way when there would be another even simpler way ?

Now:

const data = new SlashCommandBuilder()
    .setName('dog')
    .setNameLocalizations({
        pl: 'pies',
        de: 'hund',
    })
    .setDescription('Get a cute picture of a dog!')
    .setDescriptionLocalizations({
        pl: 'Słodkie zdjęcie pieska!',
        de: 'Poste ein niedliches Hundebild!',
    })

const data = new SlashCommandBuilder()
    .setName('dog')
    .setNameLocalizations({
        pl: 'pies',
        de: 'hund',
    })
    .setDescription('Get a cute picture of a dog!')
    .setDescriptionLocalizations({
        pl: 'Słodkie zdjęcie pieska!',
        de: 'Poste ein niedliches Hundebild!',
    })

const data = new SlashCommandBuilder()
    .setName('dog')
    .setNameLocalizations({
        pl: 'pies',
        de: 'hund',
    })
    .setDescription('Get a cute picture of a dog!')
    .setDescriptionLocalizations({
        pl: 'Słodkie zdjęcie pieska!',
        de: 'Poste ein niedliches Hundebild!',
    })

const data = new SlashCommandBuilder()
    .setName('dog')
    .setNameLocalizations({
        pl: 'pies',
        de: 'hund',
    })
    .setDescription('Get a cute picture of a dog!')
    .setDescriptionLocalizations({
        pl: 'Słodkie zdjęcie pieska!',
        de: 'Poste ein niedliches Hundebild!',
    })

After:

const data = new SlashCommandBuilder()
    .setNameLocalizations({
        pl: 'pies', default: true,
        de: 'hund',
        en: 'dog',

    })
    .setDescriptionLocalizations({
        pl: 'Słodkie zdjęcie pieska!', default: true,
        de: 'Poste ein niedliches Hundebild!',
        de: 'Get a cute picture of a dog!',
    })

const data = new SlashCommandBuilder()
    .setNameLocalizations({
        pl: 'pies', default: true,
        de: 'hund',
        en: 'dog',

    })
    .setDescriptionLocalizations({
        pl: 'Słodkie zdjęcie pieska!', default: true,
        de: 'Poste ein niedliches Hundebild!',
        de: 'Get a cute picture of a dog!',
    })

const data = new SlashCommandBuilder()
    .setNameLocalizations({
        pl: 'pies', default: true,
        de: 'hund',
        en: 'dog',

    })
    .setDescriptionLocalizations({
        pl: 'Słodkie zdjęcie pieska!', default: true,
        de: 'Poste ein niedliches Hundebild!',
        de: 'Get a cute picture of a dog!',
    })

const data = new SlashCommandBuilder()
    .setNameLocalizations({
        pl: 'pies', default: true,
        de: 'hund',
        en: 'dog',

    })
    .setDescriptionLocalizations({
        pl: 'Słodkie zdjęcie pieska!', default: true,
        de: 'Poste ein niedliches Hundebild!',
        de: 'Get a cute picture of a dog!',
    })

LLucasB25 For it works this way when there would be another even simpler way ? Now: ```js...

Parogo_72•12/6/22, 9:36 PM

I dont get your issue

Parogo_72•12/6/22, 9:37 PM

.setName is the default

PParogo_72 I dont get your issue

LucasB25OP•12/6/22, 9:38 PM

https://discordjs.guide/slash-commands/advanced-creation.html#localizations I’m talking about if

Original message was deleted

LucasB25OP•12/6/22, 9:39 PM

the first and the original that is currently in place, the second would be the most logical way to do

Parogo_72•12/6/22, 9:39 PM

No, the second one doesnt make sense

Parogo_72•12/6/22, 9:39 PM

As we said, what will be the fallback value?

Parogo_72•12/6/22, 9:39 PM

What if their localization is eses? What will be the name of the command

LucasB25OP•12/6/22, 9:41 PM

English, since this is the default. just force the use of the default

en

en

LucasB25OP•12/6/22, 9:43 PM

Then at this point the default lang of the bot must be used

Parogo_72•12/6/22, 9:44 PM

And which is that

Parogo_72•12/6/22, 9:44 PM

Enforcing people to use localization doesnt seem good either way, not everyone needs it

LucasB25OP•12/6/22, 9:46 PM

Either the creator’s original lang or the default lang in the directory app

LucasB25OP•12/6/22, 9:46 PM

after I never said to force the localization

LLucasB25 For it works this way when there would be another even simpler way ? Now: ```js...

LucasB25OP•12/6/22, 9:47 PM

but just suprimmer this line

Parogo_72•12/6/22, 9:47 PM

This just seems completely unnecessary and not djs related even. How is djs even supposed to get the author localization

LucasB25OP•12/6/22, 9:49 PM

If I’m not mistaken localization and based on the user’s language

Parogo_72•12/6/22, 9:49 PM

And in any case, that would only make everything more confusing

LLucasB25 Either the creator’s original lang or the default lang in the directory app

Parogo_72•12/6/22, 9:49 PM

You just said this

Parogo_72•12/6/22, 9:49 PM

You cant get that information when deploying commands

Parogo_72•12/6/22, 9:50 PM

And as explained above, changing that will only make everything more confusing for the developer

Parogo_72•12/6/22, 9:51 PM

Will only lead to issues regarding names appearing "wrongly"

Original message was deleted

LucasB25OP•12/6/22, 9:52 PM

I think the answer and all in all, the default lang would simply be the lang put on the front line of

Parogo_72•12/6/22, 9:53 PM

Thats not how objects work

Parogo_72•12/6/22, 9:53 PM

Objects arent arrays

LucasB25OP•12/6/22, 9:57 PM

or simply add to the same object

    .setDescriptionLocalizations({
        pl: 'Słodkie zdjęcie pieska!', default: true,
        de: 'Poste ein niedliches Hundebild!',
    })

    .setDescriptionLocalizations({
        pl: 'Słodkie zdjęcie pieska!', default: true,
        de: 'Poste ein niedliches Hundebild!',
    })

Parogo_72•12/6/22, 9:57 PM

At this point just use setDescription

Parogo_72•12/6/22, 9:57 PM

Seriously, I dont get your point

LLucasB25 or simply add to the same object ```js .setDescriptionLocalizations({ ...

LucasB25OP•12/6/22, 9:57 PM

like what you can do with fields

LLucasB25 like what you can do with fields

Parogo_72•12/6/22, 9:58 PM

But those are not field

Parogo_72•12/6/22, 9:58 PM

And thats not how objects work

Parogo_72•12/6/22, 9:58 PM

For the second time

Parogo_72•12/6/22, 9:58 PM

Just adding a default property doesnt mean that it will reference the pl property

PParogo_72 But those are not field

LucasB25OP•12/6/22, 9:58 PM

I know, it was just to compare visual example

Parogo_72•12/6/22, 10:01 PM

Im surprised that you think that that is easier to understand than the current way meguFace

LucasB25OP•12/6/22, 10:03 PM

It is not the story of simplicity of understanding but of adding line for nothing

LucasB25OP•12/6/22, 10:03 PM

Especially since for the moment it doesn’t work with embeds

Parogo_72•12/6/22, 10:03 PM

What have embeds to do with this

LucasB25OP•12/6/22, 10:04 PM

I'm talking about Localizations

LLucasB25 Especially since for the moment it doesn’t work with embeds

Parogo_72•12/6/22, 10:04 PM

What have embeds to do with this

LucasB25OP•12/6/22, 10:05 PM

I’m talking about the fact that we can’t use the Localizations system with embeds

Parogo_72•12/6/22, 10:06 PM

And how is that our issue?

Parogo_72•12/6/22, 10:06 PM

We cant implement something that the api doesnt support

Parogo_72•12/6/22, 10:07 PM

Also, if you want to change builder's method, ask discord to change how they want the command data to be sent

Parogo_72•12/6/22, 10:08 PM

Because

name

name

and

description

description

are required as different properties from localization

LucasB25OP•12/6/22, 10:08 PM

not so easy to tell them about this kind of request

Parogo_72•12/6/22, 10:09 PM

@discord.js/builders is just a simplier way to create those objects

Parogo_72•12/6/22, 10:09 PM

There is no reason to just invent things because we save lines of code

Parogo_72•12/6/22, 10:10 PM

Because that actually makes it messier and less readable

Parogo_72•12/6/22, 10:10 PM

And harder to mantain if something ever changes

Localizations (stupid)

Similar Threads

Similar Threads

Similar Threads