Development Team - Policies & Procedures
  • Development Team
    • Development Team Info
      • Team Leadership
      • Project Scopes
      • Task Processing
      • Git Procedures
      • Server Versioning
    • Non-Disclosure Agreement
    • Beta Team Info
    • Apply For Dev Team
    • Changelog
  • Special Updates
    • 3.5.0 Update
  • Developer Wiki
    • Local Dev Server
Powered by GitBook
On this page
  • Purpose & Responsibilities
  • Activity
  • Server Access
  • How and What to look for when testing resources
  • Dev Server Basic Commands
  1. Development Team

Beta Team Info

Purpose & Responsibilities

Beta team's purpose and primary responsibility is testing new versions of the FiveM server and confirming any bugs/issues reported by members. In order to progress items forward, beta team members when testing new resources will work directly with the project developer(s) to test and deploy their resources/edits and will report any bugs reported by members to that project's developer.

Activity

To be considered an active member of beta team, members must regularly complete the following tasks:

  • Monitor #community-support for member-generated bug and issue reports, verify those reports in either Main or Dev server and report findings to the dev team is those channels. Developers will review as time allows and based on severity

  • Monitor #task-list filtered by "Beta Testing" tag to test all open tickets

  • If you are active, you will know. If you haven't participated in any tickets for over a month you will be set to inactive, if more than 60 days you will be removed from the beta team. Activity will be measured doing a discord search for the last time you posted a meaningful message in a task thread.

    • If you will be busy with life obligations, make a post in #beta-team channel.

Server Access

Beta team members will have access to the Development Server for testing. Please only provide feedback for items that are tasked for testing/feedback. Providing feedback for items still in active development is a waste of your time and will be mostly ignored. This server is whitelisted so only Dev team, Dev Liaisons, Beta team and selected other individuals have access. Please conduct yourself like an adult would, we don't mind a little tomfoolery, but getting excessive will get you removed.

With beta team having access to our development server, any changes in server that are not posted in #beta-tasks is to be considered NDA until told otherwise.

While in the Dev server, please be in the Teamspeak channel OR in a beta discord voice channel in dev discord.

How and What to look for when testing resources

The below is a general guideline of how to test something effectively.

  • Vehicles and Vehicle Packs

    • Make sure vehicle liveries have no spelling mistakes, no voids or weird color bars. If assessing a vehicle pack, make sure the liveries are fairly consistent across different vehicles, that no element is drastically placed different.

    • Handling lines should not have any MAJOR issues. If it easily flips when turning or if the vehicle doesn't start or move at all then report that in the task thread.

  • Scripts & Features

    • Read carefully the details of the thread and make sure to test each feature specifically checking for any console errors (F8), or if functions don't work at all report that to the developer in the task thread.

  • Maps and MLO's

    • Walk the entire MLO, inside and outside to check for major collision issues, visual glitches or any other issues.

    • Check object and wall textures for any weird color bars, wrong or inconsistent logos, flags, etc

    • Check textures for inappropriate images, be sure to provide a screenshot and location for each. instance to the developer in the thread.

Tips:

When testing resources, take into consideration the perspective of our membership, how they will do something, what their experience will be and what information they will need to use the script effectively

Feel free to group up to simulate actual roleplay scenes, test how how practical or how useful something is. Try to simulate an actual patrol, with patrol rules and policies.

Our end goal increase the member experience in our servers, how something is used in-game with real scenarios.

Images and Videos are the best. If you have a bug to report, take a screenshot or a quick video that shows what the issues is. Videos go a long way for us to diagnose potential issues.

Dev Server Basic Commands

Beta testers have access to use the /admin menu to do many functions on the dev server, change job/rank ( or /setjob ID JOBNAME RANK# ), revive, give clothing menu, give items ( or /giveitem ID ITEMNAME AMT), teleport (/tp coords or /tpm teleport to marker), /vector3 or /vector4 to copy coords to clipboard. and More.

Last updated 1 month ago