Recent Posts

Pages: 1 2 3 4 5 [6] 7 8 9 10
51
I feel like with the new update, we should be bumping this again and gets some new ads going. I've been noticing quite a few more new players joining recently and I want to see more :^D I feel bad for the new players that join to find a dead server with nobody on.
52
add me plz :3333
54
Can I take CM seat !!
55
Add me please!
56
I'd like to be on the list
57
Sortition List for the 11th Senate of VillageCraft
Status: Closed to New Names
Senate Session: #11 - Starts Wednesday, 3rd April 2024 at Noon

This list will be used to randomly select Senators for the 11th Senate of VillageCraft.
Full Info: The Senate of VillageCraft
Sortition in action: Daily Sortition Selection Lists


-------
- Reply below stating you want to add your name. -
Sortition List for the 11th Senate of VillageCraft:
Luis
Dallas
FroggyBee
Ako
58
Parliament | Suggestions / Re: Discussion on Issues With /fly
« Last post by FroggyBee on 5 February 2024, 02:13:12 PM »
I think that allowing players /fly whenever they want with a "permit" or allowing them to have fly whenever they're in a village can be misused easily. Although players may be punished for using this during PvP there are also other issues as Myst mentioned such as exploring areas with fly - this would be hard to keep track of.

What I initially proposed is not much different than what we have now, but I wanted to create more "guidelines" as to when players & staff should be using fly.
Ex: Not using fly for farms, using fly for builds in the air, etc.

I'm spitballin:

If we go thru with this, I more or less think that someone granted fly should need to specifically agree to some standardized wording that says they will not build any industrialized autofarm/spawner device, not engage in pvp, and understand that their fly ability is intended as a building tool in their agreed upon region for their build.

The Staff member(s) granting this should then be required to log it; "Gave Daypath /fly for village build in Skystar-McMansion region".

I also wonder if we should be offering this tool to Villages of a certain tier or not? That way it could already be established, there's proof of concept, and thus the Staff member goes "yeah, I see what you got goin here, this build would def be helped with a lil /fly"

I think that having some guidelines is a great idea, as well as requiring staff to log it each time. But that is also a system based on trust and every staff member (even the more inactive ones) would have to acknowledge and apply any time they are asked. I can see favoritism happening in these instances as well.

I think that having those guidelines in place would make a great gateway to regulating /fly if it was able to be auto logged. It feel like (to me) the biggest issue is how hard it is to keep track of it's use.

I'm not sure if it's possible, but would we be able to have log block show whether or not something was built with/without fly or whatever gamemode the player is in? Or at least something in that ballpark, like automatically logging the time frame each player uses it. Again, don't know how all of that works so I'm also just spitballing.
59
Parliament | Suggestions / Re: Discussion on Issues With /fly
« Last post by Akomine on 2 February 2024, 09:41:45 PM »
Tldr: my recommendation is more or less in line with what Ako said, but region based instead of player based.

not both at once?
60
Parliament | Suggestions / Re: Discussion on Issues With /fly
« Last post by TheLegend12369 on 1 February 2024, 12:15:33 PM »
I just saw this thread and wanted to give my opinion as one of the people that wrote the permissions list for legacy staff and as a member of legacy staff.

The intention of legacy staff, from my point of view, was to encourage staff members to leave staff if they were no longer active. In my experience, there were many staff members that were either no longer passionate about helping develop or improve the server or were too busy with life to continue to be an effective staff member. These staff members were sticking around on staff because they had grown accustomed to building with fly and creative. I wanted to give an avenue for staff members to leave that were only staying on for those quality of life things. The intention was to create more room on staff for people that were passionate and able to serve the players.

I understand the frustration seeing staff build with creative and fly. That was part of the reason why I tried to get the creative world (which I apparently did not set up in a way that is conducive to building or aesthetics) up and running. I wanted to let people build and play around there in an area where it was harder to abuse these permissions.

I personally gave out fly pretty liberally to almost anyone who asked when I was staff, to the point that I was scolded many times. I understand the benefits of fly and it certainly does make building easier. While I would love for players to more frequently have access to fly, there are a few reasons this is hard to accomplish in an effective way.

1. Players, unlike staff, are not accustomed to enforcing server rules and are more likely to abuse fly. This is a bit of an assumption on my part, but previous staff members that are in legacy staff have been staff and have been tasked with enforcing rules. Yes, we can still have cases of abuse within staff, but in general it's much less likely that staff or ex-staff exploit or abuse permissions.

2. I feel that it would be hard to monitor. When I give out fly to someone, I know who I'm giving it out to and how long I've given it out for. It's something that has to be done manually, by a staff member, and thus it creates accountability for that staff member. If a player abuses their fly that a staffer gave them, staff can hold that player and the staff member accountable and ensure that fly is only given to trustworthy players that will be less likely to abuse it. If players just had access, there is nothing stopping them from abusing it in PVP, the end, or any other host of problems that it could create.

3. I am unsure whether it would be clear in the logs, should we need to review them, if a player was abusing fly. To my knowledge, the only log that is created when using fly is the initial command to turn it on. There are many ways that players could do shady things with fly that would be hard to track, and staff might have a hard time ensuring players aren't abusing fly.

I think a good solution, should we choose to change how fly is given out, would be to create an application of sorts to receive fly in a given region for a given amount of time. Personally, this seems easy enough to track and enforce; just make a Google form like we do with moderation logs where staff need to track who has been given a fly region and for how long they are receiving it. Make them review a set of rules that staff could write and agree to them, and if they break any of the rules, punish them accordingly.

I personally have no issue extending fly to players more frequently. I also love the idea of standardizing rules, as it eliminates a lot of this sentiment that staff are playing favorites or are being unfair with who they give perms to.

I am against giving creative to players in most cases. It is very easy to abuse, both as staff and as a player. It concerns me that staff are selling ex-staff and current staff villages that were clearly built with creative, because as pointed out in the above discussion, many expensive blocks can be used when building in creative that would otherwise be more difficult to obtain. I'm not sure what the solution is here, but I think it's quite a bad idea to give unsupervised players creative. If the masses want to change the way creative is used by staff, I'd love to hear suggestions and solutions to the perceived unfairness.

Tldr: my recommendation is more or less in line with what Ako said, but region based instead of player based.
Pages: 1 2 3 4 5 [6] 7 8 9 10