Skip to content

No labels!

There aren’t any labels for this repository quite yet.

30 labels

Sort
Sort
Alphabetically
Reverse alphabetically
Most issues
Fewest issues
area: build
area: build
the sampctl build and ensure process, dependencies, etc.
1
area: code
area: code
relates to the code, suggestions for libraries or bugs caused by logical errors
6
area: gameplay
area: gameplay
relates to a gameplay mechanic specifically, user-facing, design, etc.
6
area: meta
area: meta
issues regarding issues themselves and GitHub in general
area: repo
area: repo
repository layout, dot files, documentation, github files, etc.
1
misc: good first issue
misc: good first issue
good for a new contributor
misc: help wanted
misc: help wanted
help wanted from another contributor
pr: needs discussion
pr: needs discussion
requires discussion before further action
pr: needs docs
pr: needs docs
requires documentation either via Readme file or code comments
pr: needs review
pr: needs review
requires another contributor to review
pr: needs tests
pr: needs tests
requires in-game testing or unit testing to verify completeness
pr: work in progress
pr: work in progress
pull request should not be merged
severity: A
severity: A
a run time error that crashes the server or causes memory corruption
severity: B
severity: B
significantly impairs its basic functionality or prevents feature access/use
severity: C
severity: C
purely visual or gameplay related annoyance, does not impair functionality
status: cannot reproduce
status: cannot reproduce
the bug cannot be repeated by developers, possibly user error
status: confirmed
status: confirmed
the bug has been confirmed
status: deferred
status: deferred
put off until a later time or depends on something else being solved first
status: discuss
status: discuss
requires discussion before further action
status: duplicate
status: duplicate
duplicate of another issue
status: in-progress
status: in-progress
actively being worked on by a member of the team or a contributor
1
status: invalid
status: invalid
doesn't warrant an issue at all
type: bug
type: bug
unexpected behaviour caused by mistake in code
type: discussion
type: discussion
a discussion regarding the project in general that warrants its own issue
5
type: optimisation
type: optimisation
an improvement that relates to performance of the code at runtime
type: proposal
type: proposal
a formal proposal for a new feature or change to a feature that includes implementation details
6
type: question
type: question
a question regarding the area the issue is about
type: regression
type: regression
bug caused by upstream changes
type: suggestion
type: suggestion
a high-level suggestion for an idea, little to no implementation details or roadmap
type: todo
type: todo
general task for a basic feature or minor fix set by a project lead that needs to be completed
2