Links
Tags
Creators
Details
Licensed MIT
Published 2 months ago
Updated last week
All versions
Config screen (
1.1.4+26.3
Release
AutoResponder 1.1.4+26.3last week 12
Compatibility
Minecraft: Java Edition
26.3
Platform
Fabric
Supported environments
Client-side
Required content
Any compatible version
Any compatible version
Changes
1.1.4
Documentation
- README and changelog in two languages: English is the base version (
README.md,CHANGELOG.md), French lives inREADME.fr.mdandCHANGELOG.fr.md. Each file links to the other language at the top. - README: fixed the Config section (it still mentioned "the YACL screen", removed in 1.1.1), updated the
jar example, documented the
‹ ›arrows and the translated labels of the config screen. - No mod code change.
1.1.3
Languages
- All the mod's text now follows the language chosen in Minecraft: config screen (tabs, labels,
buttons, notice styles and overlay positions), the "answer found" / "no known answer" notices, the
feedback of the
/arcommands (on,off,reload,add) and the "toggle" key message. Before, these texts were hard-coded (in French). - Languages provided: English (en_us, default), French (fr_fr), Spanish (es_es), German (de_de). Any other Minecraft language falls back to English.
- Adding a language = copy
assets/autoresponder/lang/en_us.jsonto<code>.jsonand translate it. - Proper names ("AutoResponder", "Chat Games »") and the content of
autoresponder_questions.jsonare not translated (they depend on the server).
1.1.2
- Dropped 1.20.1 and 1.21.1 (user request): removed from the build (
settings.gradle.kts,stonecutter.properties.toml). Supported versions: 26.1.2, 26.2, 26.3. No mod code change. - A plain
gradlew buildtherefore only targets these three versions.
1.1.1
New Minecraft versions
- Added Minecraft 26.3 (Fabric API 0.161.0+26.3, Fabric Loader 0.19.5, ModMenu 21.0.0).
- Multi-version build through Stonecutter: one jar per version (
autoresponder-1.1.1+<mc>.jar). Versions that build and load: 26.1.2, 26.2, 26.3. - 1.20.1 and 1.21.1 were declared in the build but not supported (dropped in 1.1.2).
26.3 compatibility
- 26.3 moved from GLFW to SDL: the "toggle" key no longer uses
GLFW.*orInputConstants.Type.KEYSYM(removed).KeyMapping3-argument constructor +InputConstants.UNKNOWN, valid from 26.1 to 26.3. - Config screen: no hard-coded mouse button code, vanilla EditBox (already compatible with the new SDL
TextInputManager). - Verified: clean build for 26.1.2 / 26.2 / 26.3, and the 26.3 client starts with the mod loaded (resources reloaded, GUI atlas created without sprite errors).
Config screen (/ar)
- Complete redesign, without YACL: dark palette, rounded corners through 9-slice textures
(
textures/gui/sprites/rounded_rect.png,pill.png) tinted on the fly, animated hover. - Fixed: the "Chat Games" tab's frames were drawn over the "General" tab.
- Fixed: field text (cooldown, template) stuck to the top/left — an unbordered
EditBoxdoes not center its text; offset compensated. - Fixed: the on/off switch texture showed as a "missing texture" (9-slice border = exactly half the image, rejected by the atlas).
- Fixed:
‹ ›chevrons of the choice fields — they are now on both edges, left click = previous value, right click = next (before: always "next"). - The panel adapts to the resolution / GUI scale.
- "AutoResponder" title centered above the panel, bold with a shadow.
Detection / notices
- "Chat Games" detection is robust to spaces and line breaks around the prefix.
- Ignores round-result messages ("X answered Y in 2.1s!").
- Configurable notice style: chat / overlay (adjustable position) / toast / none.
Commands
/aropens the config screen;/ar on|off,/ar reload,/ar add <trigger> | <response> | [min] [max].- A single data file:
autoresponder_questions.json.
Projects on Modrinth are automatically available through a Maven repository for use with JVM build tools such as Gradle. To learn more about the Modrinth Maven API, click here.
Note: When available, you should use the creator's maven repo instead as it will have transitive dependency information that the Modrinth Maven API does not. You may also end up with duplicate dependencies if you use a mix of Modrinth and non-Modrinth Maven repositories for your dependencies, because the group identifier will be different when served through the Modrinth Maven API.
Maven coordinates:
Version ID:
build.gradle:
repositories {
exclusiveContent {
forRepository {
maven {
name = "Modrinth"
url = "https://api.modrinth.com/maven"
}
}
// forRepositories(fg.repository) // Uncomment when using ForgeGradle
filter {
includeGroup "maven.modrinth"
}
}
}
// Standard Gradle dependency
dependencies {
implementation "maven.modrinth:y5tIJ2IY:58uBXGB1"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:y5tIJ2IY:58uBXGB1"
}

