your-land/bugtracker
your-land
/
bugtracker
44
20
Code Issues 2.4k Projects 2 Wiki

150 node limit around protected area - change suggestion #4331

New Issue
Open
opened 2023-04-28 18:33:30 +00:00 by sixer · 15 comments
sixer commented 2023-04-28 18:33:30 +00:00
Copy Link

Currently, there is 150 node limit around protected area (300 for cities) where you are not supposed to build without invitation/permission. While this can be handy if you plan to expand your house/base to have more room, this has several flaws/drawbacks:

  • It is not enforced technically (although I admit I have not tried to push the limits here, like making my protected areas right next to someone else and walling him off completely), but only by staff decision (I've just heard rumors that people's builds were removed completely for violating this rule, so I am not actually sure how exactly this works in reality)
  • If you reserve some spot for you in the wild, this feature may actually prevent you from expanding - if new people settle nearby (likely just barely behind the 150 nodes range, as people would tend to pick first suitable spot closest to city/airport/shipyard/whatever) and you extend your base with a new area, that new area would be violating their space.
  • If people become inactive, the area protection still stays and it is impossible to ask for permissions (you can actually ask, but you'll never get any response)

There is no way to voluntarily lower that limit for your areas:

  • For some kind of builds, i.e. if you build a road, bridge, hellevator or similar structure meant primarily for transport, you may rather want to not limit people settling nearby and you may wish to allow people settling with their areas possibly even directly touching the road area.

Some suggestions to limit the impact of this issue:

  • Allow reducing this proximity protection for your area, so people could build nearby without having to ask for explicit permit
  • Require some activity or explicit effort to set up this reservation, so people will think if they need it or not: setting it could require either extra command, where you have to explicitly say how many nodes you wish to reserve (150 max), or possibly could even cost you (costing 1 masterarea limit ?)
    You could be even able to specify non-even area extension (like reserve 150 nodes to north, but only 50 nodes to south, as the landscape is unsuitable for your extension plans in that direction) or possibly some limited reservation (50 nodes?) could be done for free (without costing you or having to use extra commands)
  • Reduce/remove this protection for inactive accounts (for example reduce to 80 nodes after 45 days of not logging and 10 nodes after 90 days of not logging), somewhat similar mechanism where you can lose your plot in a city after month of absence.
    Although here the core protection of your build still remains, you just lose reservation for a space to expand.
Currently, there is 150 node limit around protected area (300 for cities) where you are not supposed to build without invitation/permission. While this can be handy if you plan to expand your house/base to have more room, this has several flaws/drawbacks: * It is not enforced technically (although I admit I have not tried to push the limits here, like making my protected areas right next to someone else and walling him off completely), but only by staff decision (I've just heard rumors that people's builds were removed completely for violating this rule, so I am not actually sure how exactly this works in reality) * If you reserve some spot for you in the wild, this feature may actually prevent you from expanding - if new people settle nearby (likely just barely behind the 150 nodes range, as people would tend to pick first suitable spot closest to city/airport/shipyard/whatever) and you extend your base with a new area, that new area would be violating their space. * If people become inactive, the area protection still stays and it is impossible to ask for permissions (you can actually ask, but you'll never get any response) There is no way to voluntarily lower that limit for your areas: * For some kind of builds, i.e. if you build a road, bridge, hellevator or similar structure meant primarily for transport, you may rather want to not limit people settling nearby and you may wish to allow people settling with their areas possibly even directly touching the road area. Some suggestions to limit the impact of this issue: * Allow reducing this proximity protection for your area, so people could build nearby without having to ask for explicit permit * Require some activity or explicit effort to set up this reservation, so people will think if they need it or not: setting it could require either extra command, where you have to explicitly say how many nodes you wish to reserve (150 max), or possibly could even cost you (costing 1 masterarea limit ?) You could be even able to specify non-even area extension (like reserve 150 nodes to north, but only 50 nodes to south, as the landscape is unsuitable for your extension plans in that direction) or possibly some limited reservation (50 nodes?) could be done for free (without costing you or having to use extra commands) * Reduce/remove this protection for inactive accounts (for example reduce to 80 nodes after 45 days of not logging and 10 nodes after 90 days of not logging), somewhat similar mechanism where you can lose your plot in a city after month of absence. Although here the core protection of your build still remains, you just lose reservation for a space to expand.
👍 2
AliasAlreadyTaken added the
1. kind/enhancement
 label 2023-04-28 19:06:24 +00:00
Boot commented 2023-04-28 20:48:58 +00:00
Member
Copy Link

Please remember: this server has a surface of 65k x 65k.

Please remember: this server has a surface of 65k x 65k.
👎 1
sixer commented 2023-04-28 22:53:27 +00:00
Author
Copy Link

True, but no (or very limited) teleportation, so there is motivation to have settlement near other infrastructure (shops, cities, mines, ...)

Especially for newbies who typically does not have crystal boots or enough food for longer sprinting and walk fairly slowly ....

True, but no (or very limited) teleportation, so there is motivation to have settlement near other infrastructure (shops, cities, mines, ...) Especially for newbies who typically does not have crystal boots or enough food for longer sprinting and walk fairly slowly ....
👍 3
Ravise commented 2023-04-29 09:57:38 +00:00
Copy Link
  • This is a survival server. Some level of initial difficulty is expected.
  • Food is obtainable via public farms at Haven and other cities.
  • There are 12 destinations on the airship network (I'm discounting Haven and GeG) and 18 destinations on sailship (discounted for Haven and Atlantis) = total 30 viable destinations. And at least some (I checked 2 sailship cities and a single airship destination) are free on their outskirts. Yes, it takes a bit of searching to settle close, but you can always settle further away
  • Once settled, you have /home and /spawn, which is all the personal teleportation you need for easy access to and from cities.
  • For newbies, there's an option to get a plot in cities (Citites! Not only Haven).
  • Catapult destination is changed time to time
* This is a survival server. Some level of initial difficulty is expected. * Food is obtainable via public farms at Haven and other cities. * There are 12 destinations on the airship network (I'm discounting Haven and GeG) and 18 destinations on sailship (discounted for Haven and Atlantis) = total 30 viable destinations. And at least some (I checked 2 sailship cities and a single airship destination) are free on their outskirts. Yes, it takes a bit of searching to settle close, but you can always settle further away * Once settled, you have /home and /spawn, which is all the personal teleportation you need for easy access to and from cities. * For newbies, there's an option to get a plot in cities (Citites! Not only Haven). * Catapult destination is changed time to time
sixer commented 2023-04-29 11:30:34 +00:00
Author
Copy Link

Yes, when I arrived for first time and decided to take a plot in wilderness, from time I found a suitable plot (but that was too close to somebody) to time I found another suitable conforming to this limit, it took few extra hours, deaths and kilometers walked. This adds a "bureaucratic" difficulty, not survival difficulty.

What is catapult and how it works?
Maybe that thing should be more visible for newbies ...

Yes, when I arrived for first time and decided to take a plot in wilderness, from time I found a suitable plot (but that was too close to somebody) to time I found another suitable conforming to this limit, it took few extra hours, deaths and kilometers walked. This adds a "bureaucratic" difficulty, not survival difficulty. What is catapult and how it works? Maybe that thing should be more visible for newbies ...
AliasAlreadyTaken commented 2023-04-29 21:22:00 +00:00
Owner
Copy Link

Some of the issues will be addressed with a near future update to the areas:

  • Creating areas too close to another or to cities will not work anymore. It will fail with an error message.

  • Area owners will be able to disable the distance rule for their area. Default will be "no other areas allowed within 150 blocks". To create a new area, ALL conditions must be met. If there are seven areas too close to the new one, all seven of those areas need to have the distance checking disabled, if only six disabled it and one has it enabled, the new area cannot be created.

  • This also solves the issue when people are gone for longer: You cannot build near them.

  • "Distance reduction over time" and "lowering distance rules to a chosen value" sound interesting, we'll consider those.

Some of the issues will be addressed with a near future update to the areas: - Creating areas too close to another or to cities will not work anymore. It will fail with an error message. - Area owners will be able to disable the distance rule for their area. Default will be "no other areas allowed within 150 blocks". To create a new area, ALL conditions must be met. If there are seven areas too close to the new one, all seven of those areas need to have the distance checking disabled, if only six disabled it and one has it enabled, the new area cannot be created. - This also solves the issue when people are gone for longer: You cannot build near them. - "Distance reduction over time" and "lowering distance rules to a chosen value" sound interesting, we'll consider those.
👍 5
sixer commented 2023-05-08 14:12:37 +00:00
Author
Copy Link
  • Creating areas too close to another or to cities will not work anymore. It will fail with an error message.

City areas grow sometimes. How that would be handled? By this growing, some near areas may suddenly be within the 300 limit, where previously they were ok.

In worst case, if owner accidentally un-protects its colliding area, he will not be able to re-protect it again.

Once solution would be to lower the border on such extension.

If there was area 300 away from a city and after extending the borders that area is suddenly 250 away from a city, the protective borders around that city must be lowered to 250 in the process.

> - Creating areas too close to another or to cities will not work anymore. It will fail with an error message. City areas grow sometimes. How that would be handled? By this growing, some near areas may suddenly be within the 300 limit, where previously they were ok. In worst case, if owner accidentally un-protects its colliding area, he will not be able to re-protect it again. Once solution would be to lower the border on such extension. If there was area 300 away from a city and after extending the borders that area is suddenly 250 away from a city, the protective borders around that city must be lowered to 250 in the process.
Boot commented 2023-05-08 15:30:33 +00:00
Member
Copy Link
  1. If you are planning something big, you should keep your distance right from the start.
  2. Once you have found a place, you are not forced to place your master areas very close to each other, but you can place them with said distance, so that you have already reserved a very large piece of land with this technique.
  3. If you want to build even bigger, you should team up with others anyway. Together, huge areas can be secured.
  4. Otherwise, once again, it helps to talk to the neighbors in good time.
1. If you are planning something big, you should keep your distance right from the start. 2. Once you have found a place, you are not forced to place your master areas very close to each other, but you can place them with said distance, so that you have already reserved a very large piece of land with this technique. 3. If you want to build even bigger, you should team up with others anyway. Together, huge areas can be secured. 4. Otherwise, once again, it helps to talk to the neighbors in good time.
AliasAlreadyTaken added the
4. step/discussion
2. prio/controversial
 labels 2023-05-09 01:01:52 +00:00
daydream commented 2023-08-19 13:40:26 +00:00
Member
Copy Link

For a player with some experience not to be aware of the goblin catapult is disheartening... we do mention is a LOT and it clearly isn't enough still. Plus it's notoriously hard for newbies to use, I spend a LOT of time watching newbies failure to launch for extended periods of time because the dialogue box is 'cute' instead of functional.

Another instance of things not being geared for easy understanding, especially when newbies are involved. The lack of remembering just how difficult and challenging this server is to learn for newbies really BUGS ME. I remembering being sure I could NEVER learn my way around Haven or get from spawn to the goblin catapult because it was just too complex, the corners and route is not direct, it's all this way and that way - and just visually there's a LOT to deal with and learn.

The best planners of kindergarten activities are those who remember what being there felt like, not those who remember what college feels like - if you see what I mean.

For a player with some experience not to be aware of the goblin catapult is disheartening... we do mention is a LOT and it clearly isn't enough still. Plus it's notoriously hard for newbies to use, I spend a LOT of time watching newbies failure to launch for extended periods of time because the dialogue box is 'cute' instead of functional. Another instance of things not being geared for easy understanding, especially when newbies are involved. The lack of remembering just how difficult and challenging this server is to learn for newbies really BUGS ME. I remembering being sure I could NEVER learn my way around Haven or get from spawn to the goblin catapult because it was just too complex, the corners and route is not direct, it's all this way and that way - and just visually there's a LOT to deal with and learn. The best planners of kindergarten activities are those who remember what being there felt like, not those who remember what college feels like - if you see what I mean.
Boot commented 2023-08-19 14:14:08 +00:00
Member
Copy Link

Ok, but why don't you make a separate issue out of it: "Keep things simple"?

Ok, but why don't you make a separate issue out of it: "Keep things simple"?
Sokomine commented 2023-08-19 19:49:36 +00:00
Member
Copy Link

daydream wrote:

we do mention is a LOT and it clearly isn't enough still.

Yes, but that's life. It sometimes takes ages to learn about something everyone else took for granted for a long time. Has happened to me multiple times, both ways around.

daydream wrote:

spend a LOT of time watching newbies failure to launch for extended periods of time because the dialogue box is 'cute' instead of functional.

That may be another problem. The right amount of...warning...regarding dangerous situations is hard to get. For one player, the same words that for another one may mean a casual warning to give the thing some atmosphere may be meant as a clear hint that the player will be brutally slaughtered and loose all. And vice versa. In the long run, with quests, it helps to know how the one who wrote the warning tends to think, but that's nothing new players can know. It'll be a big issue with quests.

daydream wrote:

to the goblin catapult because it was just too complex, the corners and route is not direct, it's all this way and that way - and just visually there's a LOT to deal with and learn.

Oh yes. It's far from easy at the beginning. It really is no wonder that players ask how they can get out of town. Most of us tend to forget that new players don't wear crystal boots - so it takes them ages to get anywhere. Even if they knew where they'd be going.

AliasAlreadyTaken wrote:

Area owners will be able to disable the distance rule for their area. Default will be "no other areas allowed within 150 blocks". To create a new area, ALL conditions must be met. If there are seven areas too close to the new one, all seven of those areas need to have the distance checking disabled, if only six disabled it and one has it enabled, the new area cannot be created.

It's great if the distance rule can be disabled!

The trouble I see here is if someone creates - allowed by all neighbours due to their settings - a new area "too close" and then changes the settings for his area so that the neighbours cannot expand anymore and even loose their protections if they delete them by accident.

AliasAlreadyTaken wrote:

"Distance reduction over time" and "lowering distance rules to a chosen value" sound interesting, we'll consider those.

I don't know. How long the player who built something nice has been gone doesn't really matter in my point of view (sure, if absent nothing nice new can be built, so that's a pity). And those "old" places may rarely be of intrest to new players. Unless they have a particular plan for that particular landscape.

In my experience, players are like magnets to other players. Most want to be togehter with other players, want to build close together, to help each other, to see what's beeing built there over time, to have company.

I've mixed feelings about the distance rule as such. Sure, it did annoy me on other servers if new neighbours built badly, and I usually search for a nice neighbourhood. But then, you can never know in advance how things will devellop.

A lot of builders on the server care about keeping the landscape nice and making the server beautiful. Ugly bases and devastations of the landscape are not welcomed there.

The lack of sufficiently fast travel methods conflicts with the distance rule as well.

Perhaps we can have diffrent...areas...with diffrent conditions? Not small protected areas but something larger scale. The environment around a city might be especilly protected - but not absolutely protected. The city may define manual exceptions (i.e. players can settle alongside that road over there). Things that don't fit in could still be asked to be remove (with a warning to the player that in this area special build rules apply!) - while other (again, large-scale) areas may be more open and allow players to settle where and as close as they want and build as they want (or, again with a few rules that can be checked everywhere in the area).

daydream wrote: > we do mention is a LOT and it clearly isn't enough still. Yes, but that's life. It sometimes takes ages to learn about something everyone else took for granted for a long time. Has happened to me multiple times, both ways around. daydream wrote: > spend a LOT of time watching newbies failure to launch for extended periods of time because the dialogue box is 'cute' instead of functional. That may be another problem. The right amount of...warning...regarding dangerous situations is hard to get. For one player, the same words that for another one may mean a casual warning to give the thing some atmosphere may be meant as a clear hint that the player will be brutally slaughtered and loose all. And vice versa. In the long run, with quests, it helps to know how the one who wrote the warning tends to think, but that's nothing new players can know. It'll be a big issue with quests. daydream wrote: > to the goblin catapult because it was just too complex, the corners and route is not direct, it's all this way and that way - and just visually there's a LOT to deal with and learn. Oh yes. It's far from easy at the beginning. It really is no wonder that players ask how they can get out of town. Most of us tend to forget that new players don't wear crystal boots - so it takes them ages to get anywhere. Even if they knew where they'd be going. AliasAlreadyTaken wrote: > Area owners will be able to disable the distance rule for their area. Default will be "no other areas allowed within 150 blocks". To create a new area, ALL conditions must be met. If there are seven areas too close to the new one, all seven of those areas need to have the distance checking disabled, if only six disabled it and one has it enabled, the new area cannot be created. It's great if the distance rule can be disabled! The trouble I see here is if someone creates - allowed by all neighbours due to their settings - a new area "too close" and *then* changes the settings for his area so that the neighbours cannot expand anymore and even loose their protections if they delete them by accident. AliasAlreadyTaken wrote: > "Distance reduction over time" and "lowering distance rules to a chosen value" sound interesting, we'll consider those. I don't know. How long the player who built something nice has been gone doesn't really matter in my point of view (sure, if absent nothing nice new can be built, so that's a pity). And those "old" places may rarely be of intrest to new players. Unless they have a particular plan for that particular landscape. In my experience, players are like magnets to other players. Most want to be togehter with other players, want to build close together, to help each other, to see what's beeing built there over time, to have company. I've mixed feelings about the distance rule as such. Sure, it did annoy me on other servers if new neighbours built badly, and I usually search for a nice neighbourhood. But then, you can never know in advance how things will devellop. A lot of builders on the server care about keeping the landscape nice and making the server beautiful. Ugly bases and devastations of the landscape are not welcomed there. The lack of sufficiently fast travel methods conflicts with the distance rule as well. Perhaps we can have diffrent...areas...with diffrent conditions? Not small protected areas but something larger scale. The environment around a city might be especilly protected - but not absolutely protected. The city may define manual exceptions (i.e. players can settle alongside that road over there). Things that don't fit in could still be asked to be remove (with a warning to the player that in this area special build rules apply!) - while other (again, large-scale) areas may be more open and allow players to settle where and as close as they want and build as they want (or, again with a few rules that can be checked everywhere in the area).
mrdeveloper commented 2023-08-20 00:09:38 +00:00
Copy Link

Please remember: this server has a surface of 65k x 65k.

That's fine for most bases, but not shops.

If you build in an unoccupied area, you will get little to no customers.

And if 150m rule is enforced, there simply won't be enough area with lots of visitors for everyone to build a shop in.

> Please remember: this server has a surface of 65k x 65k. That's fine for most bases, but not shops. If you build in an unoccupied area, you will get little to no customers. And if 150m rule is enforced, there simply won't be enough area with lots of visitors for everyone to build a shop in.
Sokomine commented 2023-08-20 02:57:29 +00:00
Member
Copy Link

mrdeveloper wrote:

That's fine for most bases, but not shops.

Shops are probably a diffrent issue. Either you have one in Haven, or...not many visitors. It gets a bit better with daydreams' shopping area, but that's already further out. Aveniture changes too much for shops. And Haven...suffers from those many shops.

The NPC may help as soon as everyone can get one. They can offer trades as well and need less room.

mrdeveloper wrote: > That's fine for most bases, but not shops. Shops are probably a diffrent issue. Either you have one in Haven, or...not many visitors. It gets a bit better with daydreams' shopping area, but that's already further out. Aveniture changes too much for shops. And Haven...suffers from those many shops. The NPC may help as soon as everyone can get one. They can offer trades as well and need less room.
Boot commented 2023-08-21 15:46:40 +00:00
Member
Copy Link

It really is no wonder that players ask how they can get out of town. Most of us tend to forget that new players don't wear crystal boots - so it takes them ages to get anywhere. Even if they knew where they'd be going.

Ok, the very first orientation is certainly not easy. It would be nice if there was a very simple wind rose at the spawn point, with the display north, east, south and west and maybe in the first aid book by daydream the hint that on the server (as in real life) the sun rises in the east, etc.

Crystal boots, however, are now thrown at the feet of newbies as soon as they appear in the public farm, presumably to recruit them for a party as soon as possible. I observed it myself several times while I was still in the process of recommending crafting wooden armour to the newcomers.

I don't think much of it, because it also relieves the newbies of the great first moments of achieving something and thus tends to reduce the bond to the server, but that's just my personal opinion.

> It really is no wonder that players ask how they can get out of town. Most of us tend to forget that new players don't wear crystal boots - so it takes them ages to get anywhere. Even if they knew where they'd be going. Ok, the very first orientation is certainly not easy. It would be nice if there was a very simple wind rose at the spawn point, with the display north, east, south and west and maybe in the first aid book by daydream the hint that on the server (as in real life) the sun rises in the east, etc. Crystal boots, however, are now thrown at the feet of newbies as soon as they appear in the public farm, presumably to recruit them for a party as soon as possible. I observed it myself several times while I was still in the process of recommending crafting wooden armour to the newcomers. I don't think much of it, because it also relieves the newbies of the great first moments of achieving something and thus tends to reduce the bond to the server, but that's just my personal opinion.
Boot commented 2023-08-21 15:51:26 +00:00
Member
Copy Link

That's fine for most bases, but not shops.

You think your shop will have more visitors if it is placed near other players areas and they don't like to have this shop near them?

I, on the other hand, think that shops either have to be such a very good offer that word gets around among the players about their value, as was the case with shanish's shop in the early days.

Or the shops form attractive clusters and this is only possible in consultation with several players among themselves. The best way to do this is in an easily accessible city and talk to the mayors accordingly.

> That's fine for most bases, but not shops. You think your shop will have more visitors if it is placed near other players areas and they don't like to have this shop near them? I, on the other hand, think that shops either have to be such a very good offer that word gets around among the players about their value, as was the case with shanish's shop in the early days. Or the shops form attractive clusters and this is only possible in consultation with several players among themselves. The best way to do this is in an easily accessible city and talk to the mayors accordingly.
DragonWrangler commented 2023-11-24 12:36:46 +00:00
Copy Link

Creating areas too close to another or to cities will not work.

And how would that work for roads, because some mayors make roads and protect them until the reach the edge of the city area.

One alternative would be to give mayors the city area and give a sub area to City.

>Creating areas too close to another or to cities will not work. And how would that work for roads, because some mayors make roads and protect them until the reach the edge of the city area. One alternative would be to give mayors the city area and give a sub area to City.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
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, 3d modelling, and in-game building.

  
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, or our attempts to rectify conflicting mechanics have created a new bug

  
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/license

A licensing problem is involved

  
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. might be installed on prod, but needs final testing

  
4. step/ready to QA test

the code is supposedly 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

not planned currently, but maybe some day

  
5. result/wontfix

the reported issue won't be changed, whether it's intentional or not.

  
ugh/petz

yet another petz bugz.

  
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/license
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
Clear milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
No Assignees
8 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#4331
No description provided.
Delete Branch "%!s(<nil>)"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?