SC Lecter
07-05-2008, 10:32 PM
PROP BUILDER POPUP TOOL
Bria's player followed-up on the status of a cross-game prop building tool, @BUILD, which allows players to propose item ideas, then once the item is approved, provides a template to the player who suggested it so that they can build the item. It will make things a lot easier on both staff and players alike, and cuts down on request-wait time since players would be essentially building requests themselves. Both the idea and the item have to be approved before it gets introduced to the game.
The tool is ready to use for simple props.
STATUS:
As of July 3, 2008 Lecter will follow-up with Azrael on how to get @BUILD to tie into the actual code for this command. Once that's working rest assured he'll post how this tool works.
The @build command is now in place and ready to use (big thanks to Azrael). In the tool's current stage, you will be able to create an object and provide its descriptions along with its mass, density, container capacity. The tool is not yet finished so feel free to submit feedback to the LC staff who will forward it on to Azrael.
One thing to note is that not everyone will have access to this command. To get access, just file an assist stating why you should have it (e.g. "I am good at coming up with prop ideas" or "I am good at writing descriptions") or file a storypoint request saying you want such and such prop and you want to provide the descriptions. We likely won't be strict on who we allow access unless we start to notice abuse. Trial accounts (unless I am overruled by Willow) will not be given access. [warning]It is expected that if you request access to this tool that you have every intention to use it responsibly. Failure to do so will result in your access being revoked without warning and possible further repercussions depending on the severity of the abuse.[/end warning] An example of irresponsible use is proposing "joke" props such, as a booger or Chuck Norris. Basically, anything that will waste the staff's time or intentionally harm the tool and/or game.
There are three stages to this process:
1. Propose idea. State what the prop is and a general description of what it is and why it should be allowed in the game world. You can also note whether you want to provide descriptions or if you want someone else to (anyone will be able to build the prop if approved).
2. Get staff approval. Staff will review the proposal and will accept or reject it. They will also determine who writes the descriptions (the player who submitted it or "anyone").
3. Build prop. If the player is allowed to build their own prop, it will be up to them (and only them) to provide the descriptions. If the prop can be built by anyone, then anyone can claim it and then only that person will be able to build it (unless they give up their claim on it).
Another thing to note is that it's not possible by using the @build command to tell when a prop is finished. So if you finish up a prop, make sure to file an @assist so we can give the prop a final review and release it.
Bria's player followed-up on the status of a cross-game prop building tool, @BUILD, which allows players to propose item ideas, then once the item is approved, provides a template to the player who suggested it so that they can build the item. It will make things a lot easier on both staff and players alike, and cuts down on request-wait time since players would be essentially building requests themselves. Both the idea and the item have to be approved before it gets introduced to the game.
The tool is ready to use for simple props.
STATUS:
As of July 3, 2008 Lecter will follow-up with Azrael on how to get @BUILD to tie into the actual code for this command. Once that's working rest assured he'll post how this tool works.
The @build command is now in place and ready to use (big thanks to Azrael). In the tool's current stage, you will be able to create an object and provide its descriptions along with its mass, density, container capacity. The tool is not yet finished so feel free to submit feedback to the LC staff who will forward it on to Azrael.
One thing to note is that not everyone will have access to this command. To get access, just file an assist stating why you should have it (e.g. "I am good at coming up with prop ideas" or "I am good at writing descriptions") or file a storypoint request saying you want such and such prop and you want to provide the descriptions. We likely won't be strict on who we allow access unless we start to notice abuse. Trial accounts (unless I am overruled by Willow) will not be given access. [warning]It is expected that if you request access to this tool that you have every intention to use it responsibly. Failure to do so will result in your access being revoked without warning and possible further repercussions depending on the severity of the abuse.[/end warning] An example of irresponsible use is proposing "joke" props such, as a booger or Chuck Norris. Basically, anything that will waste the staff's time or intentionally harm the tool and/or game.
There are three stages to this process:
1. Propose idea. State what the prop is and a general description of what it is and why it should be allowed in the game world. You can also note whether you want to provide descriptions or if you want someone else to (anyone will be able to build the prop if approved).
2. Get staff approval. Staff will review the proposal and will accept or reject it. They will also determine who writes the descriptions (the player who submitted it or "anyone").
3. Build prop. If the player is allowed to build their own prop, it will be up to them (and only them) to provide the descriptions. If the prop can be built by anyone, then anyone can claim it and then only that person will be able to build it (unless they give up their claim on it).
Another thing to note is that it's not possible by using the @build command to tell when a prop is finished. So if you finish up a prop, make sure to file an @assist so we can give the prop a final review and release it.