1. Setup your pack
- A pack is a group of 5 commands.
- Load up the HD Admin Trello Commands Board.
- Select and drag a card from Packs-To-Do to Packs-In-Process, OR create a new card. Join the card if using an existing one.
- Setup your 5 commands as a checklist.
2. Create the commands
- Before beginning a command…
- Understand the importance of Fun Commands.
- Get to know the HD Admin Documentation.
- Once ready, begin creating commands in your development place (found in discord under #
places). - Ping @Modeler if you need a model built during the creation of your pack.
3. Publishing your pack
- Once complete, tick off all the commands within your card and transfer to ‘Completed Packs’.
- Test your commands and fix any surface-layer bugs.
- Ping @Testers in #
feedback to verify your pack, making sure to include a link of your Trello card. - Correct any recommendations and bugs from the testers.
- Once Tester approved, your pack will be code-reviewed by a Lead member. If necessary, amend any issues from your code review.
- Once Lead approved, you’ll be paid accordingly for your pack and your commands added to the MainModule. We will be keeping packs on standby until December for when the new commands framework is implemented.
From time-to-time, Scripters will be in need of a model for their command. As a Modeler, you’ll be assisting Scripters with the creation of these models, responding to commissions in a promptly manor so that Scripters can continue their command.
About
- Once a Scripter completes their pack, they will ping you with a link to their Trello card.
- Locate their development place under #places
- Review and test all commands within that pack.
1. Reviewing
- For fun commands, is the command as fun as it can be? Do the commands contain suitable descriptions and aliases?
- If not, ping the developer of the pack to make any necessary amendments.
- Read the Fun & Utility Commands guide for more info.
2. Testing & Debugging
- Test test test! Does the command…
- Function as intended, even under unusual circumstances (e.g. multiple players, executed after another command, when you reset/die, etc?
- Work for both R6 and R15?
- Is it compatible on all devices?
- Gather a list of bugs for the whole command pack, then once thoroughly tested, ping the developer to make any fixes if needed.
- Repeat the process if bug fixes were required.
- Once bug-free, ping @Lead in #feedback with the developer’s Trello card to send the pack off for code-review.
Responsibilities
- Core maintenance and improvement
- Providing support and answering questions for team members
- Code review for command packs
- Creating your own command packs during quiet weeks
Code Review
Once Testers have completed their review, they will ping you with a developer’s Trello card pack.
- Locate their development place under #places
- Review the code for the commands within that command pack:
- Things to consider and watch out for…
- Inefficient/harmful/malicious code
- Server-side vulnerabilities
- If assets have been used, do they contain any scripts, and if so, are they meant to be there?
- Is code written within the scope of the command?
- Is the developer using core functions and practises mentioned in the documentation?
- Have they organised their code clearly?
- Fix any minor mistakes, otherwise ask the developer to amend the pack in #feedback. For abusive code, please inform me.
- Once approved, drag the card to ‘Approved Packs’
Transferring approved commands to the MainModule
- Coming soon
Coming soon