@ -439,8 +439,8 @@ msgid "This requires three steps."
msgstr "これには3つのステップが必要です。"
#: ../../faq.rst:442
msgid "Attach a message to the :class:`~discord.ui.View` using either the return type of :meth:`~abc.Messageable.send` or retrieving it via :meth:`Interaction.original_response`."
msgid "Attach a message to the :class:`~discord.ui.View` using either the return type of :meth:`~abc.Messageable.send` or retrieving it via :attr:`InteractionCallbackResponse.resource`."
msgstr ""
#: ../../faq.rst:443
msgid "Inside :meth:`~ui.View.on_timeout`, loop over all items inside the view and mark them disabled."
@ -455,30 +455,30 @@ msgid "Putting it all together, we can do this in a text command:"
msgstr "すべてをまとめると、テキストコマンドではこのように行うことができます。"
#: ../../faq.rst:470
msgid "Application commands do not return a message when you respond with :meth:`InteractionResponse.send_message`, therefore in order to reliably do this we should retrieve the message using :meth:`Interaction.original_response`."
msgid "Application commands, when you respond with :meth:`InteractionResponse.send_message`, return an instance of :class:`InteractionCallbackResponse` which contains the message you sent. This is the message you should attach to the view."
msgstr ""
#: ../../faq.rst:472
msgid "Putting it all together, using the previous view definition:"
msgstr "以前のビューの定義を使用して、すべてをまとめます。"
#: ../../faq.rst:487
#: ../../faq.rst:490
msgid "Application Commands"
msgstr "アプリケーションコマンド"
#: ../../faq.rst:489
#: ../../faq.rst:492
msgid "Questions regarding Discord's new application commands, commonly known as \"slash commands\" or \"context menu commands\"."
msgid "Did you invite your bot with the correct permissions? Bots need to be invited with the ``applications.commands`` scope in addition to the ``bot`` scope. For example, invite the bot with the following URL: ``https://discord.com/oauth2/authorize?client_id=<client id>&scope=applications.commands+bot``. Alternatively, if you use :func:`utils.oauth_url`, you can call the function as such: ``oauth_url(<other options>, scopes=(\"bot\", \"applications.commands\"))``."
msgid "Whether you use :attr:`Message.poll` to check the message polls."
msgstr ""
#: ../../intents.rst:118
msgid "Whether you use the commands extension with a non-mentioning prefix."
msgstr "コマンド拡張機能をメンションなしプレフィックスで使用するかどうか。"
#: ../../intents.rst:122
#: ../../intents.rst:123
msgid "Member Cache"
msgstr "メンバーキャッシュ"
#: ../../intents.rst:124
#: ../../intents.rst:125
msgid "Along with intents, Discord now further restricts the ability to cache members and expects bot authors to cache as little as is necessary. However, to properly maintain a cache the :attr:`Intents.members` intent is required in order to track the members who left and properly evict them."
msgid "To aid with member cache where we don't need members to be cached, the library now has a :class:`MemberCacheFlags` flag to control the member cache. The documentation page for the class goes over the specific policies that are possible."
msgid "Other events that take a :class:`Member` will require the use of the member cache. If absolute accuracy over the member cache is desirable, then it is advisable to have the :attr:`Intents.members` intent enabled."
msgid "If the cache is disabled or you disable chunking guilds at startup, we might still need a way to load members. The library offers a few ways to do this:"
msgid "Some common issues relating to the mandatory intent change."
msgstr "強制的なインテントの変更に関連するいくつかの一般的な問題。"
#: ../../intents.rst:165
#: ../../intents.rst:166
msgid "Where'd my members go?"
msgstr "私のメンバーはどこに行ったのか？"
#: ../../intents.rst:167
#: ../../intents.rst:168
msgid "Due to an :ref:`API change <intents_member_cache>` Discord is now forcing developers who want member caching to explicitly opt-in to it. This is a Discord mandated change and there is no way to bypass it. In order to get members back you have to explicitly enable the :ref:`members privileged intent <privileged_intents>` and change the :attr:`Intents.members` attribute to true."
msgid "Why does ``on_ready`` take so long to fire?"
msgstr "``on_ready`` が発火するまでに時間がかかるのはなぜか？"
#: ../../intents.rst:187
#: ../../intents.rst:188
msgid "As part of the API change regarding intents, Discord also changed how members are loaded in the beginning. Originally the library could request 75 guilds at once and only request members from guilds that have the :attr:`Guild.large` attribute set to ``True``. With the new intent changes, Discord mandates that we can only send 1 guild per request. This causes a 75x slowdown which is further compounded by the fact that *all* guilds, not just large guilds are being requested."
msgid "The first solution is to request the privileged presences intent along with the privileged members intent and enable both of them. This allows the initial member list to contain online members just like the old gateway. Note that we're still limited to 1 guild per request but the number of guilds we request is significantly reduced."
msgid "The second solution is to disable member chunking by setting ``chunk_guilds_at_startup`` to ``False`` when constructing a client. Then, when chunking for a guild is necessary you can use the various techniques to :ref:`retrieve members <retrieving_members>`."
msgid "Under the original system this would result in 2 requests to fetch the member list (75 guilds, 20 guilds) roughly taking 60 seconds. With :attr:`Intents.members` but not :attr:`Intents.presences` this requires 840 requests, with a rate limit of 120 requests per 60 seconds means that due to waiting for the rate limit it totals to around 7 minutes of waiting for the rate limit to fetch all the members. With both :attr:`Intents.members` and :attr:`Intents.presences` we mostly get the old behaviour so we're only required to request for the 95 guilds that are large, this is slightly less than our rate limit so it's close to the original timing to fetch the member list."
msgid "If you want the logging configuration the library provides to affect all loggers rather than just the ``discord`` logger, you can pass ``root_logger=True`` inside :meth:`Client.run`:"
msgid "If you want to setup logging using the library provided configuration without using :meth:`Client.run`, you can use :func:`discord.utils.setup_logging`:"
github-actions[bot]
4 days ago
GitHub