Based on this discussion in the forum, I took a look at the shop manager and changed the way how things are setup in terms of the user history. So from now on, the “Users” section of the shop manager only shows the general stats about all active users. If you want to see detailed shopping history of a specific user, this will be now on the user page instead. There is now also pagination, so you can browse through 100% of the sales history.
Take a look!
The Lot manager now shows you why lots are not in the list of available lots to chose from. There are 4 possible reasons:
The system simply shows how many lots were hidden for each of those 4 reasons (if applicable). I hope this clarifies the form contents a bit better.
I have discovered with the help of the lag mapping tool that there is an area in the nether that caused extreme levels of l
ag:
Yellow here means that a chunk as loaded at least once when lag occurred, Red means the chunks were loaded when the worst lag occurred and blue means the chunk was live ALWAYS when lag was occurred. So the yellow areas one can ignore, but the red and blue ones means that this area has been the single biggest source of lag for the whole server, and it’s huge. Every square in this is 16 blocks. It spanned 2×2 regions or more precisely 400×400 blocks. When looking closer at the location, I found the following:
What you can see here is a MASSIVE area of lava flow. Someone (I know at least one person who is involved) has made a huge dig of a nether fortress while building a blaze spawner. While the blaze spawner was not an issue, the lava flow created a huge amount of lag. The server basically immediately went from 20 tps to 10 tps lag (minimum TPS, not 1-minute average) the moment I showed up there – despite the fact that I was alone on the server. Since the lava flow area was so huge and distributed over such a wide area, I could not even fix it. I had to reset the wider area of 4 region files, i.e. 1024×1024 blocks.
I won’t start naming names or banning people here, but this should be a reminder NOT to create unnecessary lava flows.
It seems that the respawn/suicide command suddenly started to crash the server, so I had to disable it until I have time to fix it this weekend.
FYI, I am currently working on improvements on the back-end. The goal is to separate the Donator status from the user level. The first result will be that people won’t be called “SettlerDonator” anymore, but “Settler” and “Donator” separately. Currently, the system works with only one set of levels and this requires people to have 2 different, independent levels at the same time, and eventually more. The ultimate goal is that we can have a set of different levels that can be used to give in-game user rights for specific commands or access to specific things without interfering with other functions. For example, we will be able to give access to lots by group membership or hand out specific disguises by achievements.
This change is quite involved however since the system is working with the current levels in MANY parts of the code and all of those need to be changed. While I have the code reasonably compartmentalized for other things (like deposit etc), the userlevels are spread all over the system. I made some way forward by finding all the functions that change, check or manage userlevels and consolidate them in one file, but now I have to make sure they all can deal with several levels being found for one user and to interpret them dynamically instead of relying on hard-coded terms.
So in effect you won’t see a lot of new improvements in the coming few days but some instances where things break for a bit when I screw up the code :D.
Also, disguises are switched off for now until I have time to figure out some strange issues with the plugin we are currently using. Please stand by for updates there.
This is a daily update on the status of the work done behind the scenes.
Our webserver is completely open source, hosted on GitHub. You can help improve the server by fixing issues here.
….as the title says.
I just managed to re-add the list of the user forum posts back to the profile pages.
The links are not 100% accurate since the forum is breaking longer threads into pages, and reading the forum posts from the database I am not able to find out which page to go to. But it points to the right thread at least.
We have now a new section in the user profiles that shows the promotion history of a user. Since we keep the records of Citizen promotion only since January 2016, this is not very complete, but I still find the whole thing informative. For example, here’s Sepengo’s page:
Thanks everyone who contributed to the discussion about the user votes. I have now made the following changes:
Future plans:
I wanted to point out to everyone that we are having a discussion in the forum about user voting. Please take a look and voice your opinion!
Please see the latest upgrades from the voting system:
Congratz and thanks to all voters!
I made a small update to the discord chat. Previously messages sent to the global channel with the /g <text> command while someone was mainly in a different channel would not show up on Discord. This is fixed now.
This is a daily update on the status of the work done behind the scenes.
Our webserver is completely open source, hosted on GitHub. You can help improve the server by fixing issues here.
This is a daily update on the status of the work done behind the scenes.
Our webserver is completely open source, hosted on GitHub. You can help improve the server by fixing issues here.
In order to give lots back, there is the general question about the mechanics of what can be given back and what that actually means.
Giving back a lot finally means that it should have a quality that justifies the lot to be preserved and never be reset. It’s therefore the same requirement as a winner in a building contest. I plan to enable some sort of a judging process as for the user promotion voting process. So we need to make a list of judgement criteria that allows people to vote on a build by answering the same questions for any possible submission. Possible ratings are:
I would think that a minimum score in each category would be required. On top of that, a sum of all scores should be required as well, and that one should be higher than the combined minimum score of all together. Then we would ask for people to vote on it. But who?
Once a lot has been given back, the question comes what will be the reward for that. Again, different choices:
What is a good price increment for kingdom lots?
This boils down to the question how many lots one can reasonably have as a project and how many people should be required from a certain size on to participate in the purchase of lots. If one ever only – by reasonable standards – to have one “private” lot and another 2×2 larger project lot, we have 5 lots that should be somewhat affordable for example. For larger projects one should either be really rich or have others support them in buying and building. The current 250k Uncs for 5 lots is a bit on the high side for that.
We can argue that larger builds need 3×3 as a size as well, so 10 lots would be the right number in that range. Specially when one needs to occupy land that is not along the lot borders such as a larger island, this becomes helpful. Beyond that 3×3 sice, I think that builds would become either unmanageable or ambitious beyond a reasonable level – as a single project to be done in a 1-man show.
Then there is the question how much one should pay for 10 lots – in the latter case.
[Update:]
Something completely different than just price limits:
One option that just came to my mind is to make a limit how many lots one can have by checking how many they gave back so far. This would mean that you cannot get 2 lots if you have not given one back so far. So with each lot that you give back, you can increase the limit of lots that you can own in the kingdom. Example:
Everyone is allowed to have x+1 (main) lots in kingdom. You start with 1+1=2. Once you give one back, you are back at 1, you can get 2 new ones (2+1=3). Give those 2 back, and you get 3 new ones (3+1=4) and so on. This way we avoid people starting mega-projects in 2×2 spaces that they can never finish because they cannot even finish a 1 lot build. We might still make incremental pricing, but the fact that someone has finished a lot of builds allows them to increase their size with the assurance that they actually do something with it.
[/Update]
Please comment below with your opinions on this matter.
We have a new achievement type, measuring how many emails you have sent using the internal system. Your current level can be seen as usual on your user page.
So I have been investigating on what is keeping the Villager chunks alive and got some replies there. It seems that there are some very old bugs in Spigot that they tried to fix to make it more work like the Vanilla server, which in turn caused the Villagers to become persistent despite no users being near. This has caused issues also for other servers.
The end result is that I tried to change a spigot setting that might fix the issue, but I need to observe this going forward. For this, I need to get more info from my lag-tracking plugin. There is an issue with it however. If you know basic Java, please stop by on GitHub and help me solve the issue. The issue has been resolved!
Please see the latest upgrades from the voting system:
Congratz and thanks to all voters!