Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

Multiplayer - RP Server - Repair permissions

Abierto
#172 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
35/100
Tipo de issue
Error
Claridad
Necesita aclaración
Estado de actividad
Tranquilo
Stack tecnológico
lua
Área
game-dev

Línea de trabajo

Start by reproducing the multiplayer scenarios described: a contractor attempting larger repairs at another farm’s repair shop and their own, plus a vehicle brought to the main dealership. Then trace how repair permissions, repair-size limits, and vehicle availability differ across those locations. Done means the intended Fleet Services workflow is supported, or the limitation is clearly identified.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

enhancement

Not really an issue, more of a suggestion? Looking for an assist with ADS. I don't know if its meant to be used this way or if maybe I'm doing this wrong. We have a multiplayer server. Each "farm" has a business. Whether its logging, mining, farming or what we tried to start (Fleet Services). I use a mobile service vehicle and get made a contractor to the other farms. I can tap into their machines and diagnose but for repairs, some say its too large for mobile repair. No problem, figured Id use the repair facility on their farm or even bring it to my own (farm) Repair shop. It won't let me make larger repairs on anything at the repair shop neither the farm im contracted with (thats me doing it not the farm owner) nor if I brought it to my (farm) REpair shop. I even tried the main dealership and the vehicle doesn't even show up.

The goal was to have a "Fleet Services" division so farmers, loggers etc can continue on and maintenance is handled by the Fleet Services (farm).

Lenguaje dominante
Lua
Estrellas
282
Forks
17
Métricas de merge de PR
Sin PR fusionados en 30 d

Preparar el entorno

Este proyecto no incluye contenedor de desarrollo, Dockerfile ni guía de contribución, así que la configuración corre por tu cuenta: empieza por su README y consulta nuestra guía para la primera contribución para los pasos generales.

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de id577/FS25_AdvancedDamageSystem

Todos los issues de id577/FS25_AdvancedDamageSystem

Issues similares

Más issues de Lua

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.