5zig-reborn / 5zig-reborn/The-5zig-Mod
[Mod Compat] Custom Main Menu
- Lenguaje dominante
- Java
- Estrellas
- 111
- Forks
- 12
- Métricas de merge de PR
- Sin PR fusionados en 30 d
Descripción
**Describe the bug**
The last server button is removed by CMM (The Custom Main Menu Mod) (expected behavior) but is not listed in the debug.log file as being removed (unexpected behavior) and attempting to add it back in using a wrapped button (proper procedure) results in the button disappearing entirely (unexpected behavior).
**To Reproduce**
Steps to reproduce the behavior:
1. Install 5zig and CMM for 1.12.2 on a forge 1.12.2 Minecraft installation
2. Open the config folder and find 'mainmenu.json' in the 'CustomMainMenu' folder
3. Attempt to insert a wrapped button by using the button ID (typically found in the debug.log) and adding a button (for example, here's my code:
` "lastserver":
{
"text": "Last Server",
"posX": 2,
"posY": 48,
"width": 116,
"height": 20,
"wrappedButton": 98
},`
)
4. See error
**Expected behavior**
If everything was functioning properly, CMM would remove the last server button, log it in the debug.log, and a user of CMM could add it back in using the wrappedbutton function to restore its functionality.
**Desktop (please complete the following information):**
- OS: Windows 10
- Version: 10.0.18363 Build 18363
Guía de contribución
No hay ninguna guía de contribución indexada para este repositorio
Línea de trabajo
The issue involves the Custom Main Menu (CMM) mod interaction with the 5zig mod's last server button. Start by examining the debug.log generation in the codebase to see why the button removal isn't logged. Look for the wrapped button functionality in the CMM integration points. Testing requires a Minecraft 1.12.2 Forge setup with both mods installed. Check the mainmenu.json configuration and the button ID handling. Done when the button removal is logged and the wrapped button restores functionality without disappearing.
Escrito por el modelo de indexación a partir del texto del issue.
Evaluación
- Stack tecnológico
- java
- Área
- game-dev
- Tipo de issue
- Error
- Dificultad
- 4/5
- Tiempo estimado
- 3-5 días
- Estado de actividad
- Estancado
- Claridad
- Bastante claro
- Aptitud para principiantes
- 35/100