Labels
Depends on balancing 1. kind/breaking
something that alters or disables an existing game mechanic 1. kind/bug
Something is not working 1. kind/construction
A build needs fixing 1. kind/documentation
Needs proper documentation 1. kind/enhancement
New feature 1. kind/griefing
players despoiling builds or nature 1. kind/invalid
Not a valid report, e.g. created by mistake with no content. 1. kind/meme
issue is mostly a joke 1. kind/node limit
something which works for or against the node limit 1. kind/other
Something not within the other kinds 1. kind/protocol
something concerning how staff should react to player requests, or how players should treat each other 2. prio/controversial
not likely to happen w/out a lot of discussion 2. prio/critical
Very important 2. prio/elevated
something players are eager to have fixed 2. prio/good first issue
the resolution to this is could be done by a new minetest contributor, who doesn't yet understand the mod ecosystem 2. prio/interesting
one of us has real interest in getting this implemented or fixed. however, more research might be needed. 2. prio/low
Not so important 3. source/art
art needs to be created or found for this to exist. includes sound and 3d modelling. 3. source/client
Issue is with the minetest client, or with player client configuration or the technical details of their setup 3. source/engine
Issue is due to a bug or feature of the minetest engine 3. source/ingame
Problem and solution exist in-game, e.g. builds or player moderation 3. source/integration
Two or more nonbuggy mechanics conflict 3. source/lag
A problem which is caused or made worse by lag, due to server processing issues, client processing issues, or network issues 3. source/mod upstream
Problem is upstream (not engine/client) 3. source/unknown 3. source/website
Affects the website 4. step/approved
Alias has approved this feature, someone should implement it 4. step/at work
Being worked on 4. step/blocked
we plan to do this, but other work has to be finished first 4. step/discussion
issue is under discussion, a solution has not been dictated or agreed upon 4. step/help wanted
Need some help 4. step/needs confirmation 4. step/partially fixed
this is mitigated or partially solved, but more work needs to be done 4. step/question
More information is needed 4. step/ready to deploy
has been QA tested by another person. has no outstanding issues. may be installed but unverified on prod 4. step/ready to QA test
the code is fixed, but needs to be tested. 4. step/want approval
Someone can quickly implement this if Alias approves the change/feature 5. result/cannot reproduce 5. result/duplicate
This issue or pull request already exists 5. result/fixed
problem is fixed 5. result/maybe
Needs more research 5. result/wontfix
This won't be fixed ugh/petz ugh/QA main
That's something we can only wait and see whether it hapens again: On the main server ugh/QA NOK
Fix didn't yield the expected results ugh/QA OK
tested
Apply labels
Clear labels
1. kind/balancing
Depends on balancing 1. kind/breaking
something that alters or disables an existing game mechanic 1. kind/bug
Something is not working 1. kind/construction
A build needs fixing 1. kind/documentation
Needs proper documentation 1. kind/enhancement
New feature 1. kind/griefing
players despoiling builds or nature 1. kind/invalid
Not a valid report, e.g. created by mistake with no content. 1. kind/meme
issue is mostly a joke 1. kind/node limit
something which works for or against the node limit 1. kind/other
Something not within the other kinds 1. kind/protocol
something concerning how staff should react to player requests, or how players should treat each other 2. prio/controversial
not likely to happen w/out a lot of discussion 2. prio/critical
Very important 2. prio/elevated
something players are eager to have fixed 2. prio/good first issue
the resolution to this is could be done by a new minetest contributor, who doesn't yet understand the mod ecosystem 2. prio/interesting
one of us has real interest in getting this implemented or fixed. however, more research might be needed. 2. prio/low
Not so important 3. source/art
art needs to be created or found for this to exist. includes sound and 3d modelling. 3. source/client
Issue is with the minetest client, or with player client configuration or the technical details of their setup 3. source/engine
Issue is due to a bug or feature of the minetest engine 3. source/ingame
Problem and solution exist in-game, e.g. builds or player moderation 3. source/integration
Two or more nonbuggy mechanics conflict 3. source/lag
A problem which is caused or made worse by lag, due to server processing issues, client processing issues, or network issues 3. source/mod upstream
Problem is upstream (not engine/client) 3. source/unknown 3. source/website
Affects the website 4. step/approved
Alias has approved this feature, someone should implement it 4. step/at work
Being worked on 4. step/blocked
we plan to do this, but other work has to be finished first 4. step/discussion
issue is under discussion, a solution has not been dictated or agreed upon 4. step/help wanted
Need some help 4. step/needs confirmation 4. step/partially fixed
this is mitigated or partially solved, but more work needs to be done 4. step/question
More information is needed 4. step/ready to deploy
has been QA tested by another person. has no outstanding issues. may be installed but unverified on prod 4. step/ready to QA test
the code is fixed, but needs to be tested. 4. step/want approval
Someone can quickly implement this if Alias approves the change/feature 5. result/cannot reproduce 5. result/duplicate
This issue or pull request already exists 5. result/fixed
problem is fixed 5. result/maybe
Needs more research 5. result/wontfix
This won't be fixed ugh/petz ugh/QA main
That's something we can only wait and see whether it hapens again: On the main server ugh/QA NOK
Fix didn't yield the expected results ugh/QA OK
tested
No Label
1. kind/balancing
1. kind/breaking
1. kind/bug
1. kind/construction
1. kind/documentation
1. kind/enhancement
1. kind/griefing
1. kind/invalid
1. kind/meme
1. kind/node limit
1. kind/other
1. kind/protocol
2. prio/controversial
2. prio/critical
2. prio/elevated
2. prio/good first issue
2. prio/interesting
2. prio/low
3. source/art
3. source/client
3. source/engine
3. source/ingame
3. source/integration
3. source/lag
3. source/mod upstream
3. source/unknown
3. source/website
4. step/approved
4. step/at work
4. step/blocked
4. step/discussion
4. step/help wanted
4. step/needs confirmation
4. step/partially fixed
4. step/question
4. step/ready to deploy
4. step/ready to QA test
4. step/want approval
5. result/cannot reproduce
5. result/duplicate
5. result/fixed
5. result/maybe
5. result/wontfix
ugh/petz
ugh/QA main
ugh/QA NOK
ugh/QA OK
Milestone
Set milestone
Clear milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Assign users
Clear assignees
No Assignees
3 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.
No due date set.
Dependencies
No dependencies set.
Reference: your-land/bugtracker#1873
Reference in new issue
There is no content yet.
Delete Branch '%!s(<nil>)'
Deleting a branch is permanent. It CANNOT be undone. Continue?
No
Yes
HTML
Trailing / for unpaired tags are a XHTML thing and are not used in HTML5
If you want to specify the width specify the height as well. Using the width and height attributes of the image tag is primarily for reserving space on the page. I would argue that specifying a height would be more important for that than specifying the width.
Also trailing / for unpaired tags are a XHTML thing and are not used in HTML5
What is this used for? If it's not used (by for instance a script) it should not be here.
For links that lead off the current page you can better set a target attribute to open in a new tab|window
Please also put this between
<p>
tagsOkay, 3 major thing here:
<nav>
tags as they are in the wrong place as wel as redundant<section>
and<nav>
tags because they are in the wrong order<p>
tags around the list items. If you want to use<p>
tags in a list place them in between the<li>
tags, not around themFooters are not manditory for websites. If not used they should not be defined. The same goes for the unused
<ul>
tagCSS
Try to keep the CSS files clean by removing unused styles.
Please don't assign such styles to tags, but rather use classes or ids. You can and are using more than one
<nav>
tag in your page and setting such style as such can have unexpected and horrible-looking results.JAVASCRIPT
The entire main.js file seems dedicated to some sort of confetti system. However the element "confetti-box" is no longer an existing element on the page. Either restore the confetti-box element or unlink the javacript file.
Hey Elvano, thanks for the ideas. I'm going to look at it and we'll see how to implement your ideas. Feel free to send me more information in irc.
i suppose this is the wrong decade to root for XHTML :) i always preferred it.