Post by MrKill on Oct 21, 2015 15:18:49 GMT -6
Okay, guys.
As per the other thread, 'Let's improve this website together', we've come up with a vote that needs to be decided on by the community.
The vote is the return of the main mission.
The main mission, historically, used to be the only mission people could participate in that wasn't either a side-mission or sandbox story. Since we've changed over to a free-to-make system regarding our missions. However... the 'continuity' of the main mission has been lost and it appears like no one feels the timeline is advancing without the linear progression provided by the main mission. Now, keep in mind, that the time-line can move with user generated missions; they just have to be staff sponsored.
Here is what you're voting for.
A vote for yes indicates you want main missions, which are created by the staff and guardian team, to return. These main missions will resume the role they had before they were removed prior to the most recent major website changes. A linear progressing time-line will return, however, this means that we will have to keep a better eye on the dates of user generated content because of fluid restrictions.
By fluid restrictions, we mean where your character is and when that is, and take canonical information into account. So an example would be this:
- User A creates a user-mission dated on March 1st, 2550; it takes place in the SOL System as a social thread.
- User B joins User A's mission.
- User A launches his mission with User B [and others].
- Staff release a main mission taking place on March 3rd, 2550; this mission is set in the outer colonies, multiple light years away from User A and B's characters.
- User A and B cannot participate in the Main Mission with the characters they used for the social thread. Why? They couldn't realistically be there in time because of the UNSCs relatively 'slow' speeds in FTL travel.
A vote for no means you wish to keep the current system we have now. You can read up on this system here: www.yappashalorpg.com/thread/11626/mission-creation-guide
As per the other thread, 'Let's improve this website together', we've come up with a vote that needs to be decided on by the community.
The vote is the return of the main mission.
The main mission, historically, used to be the only mission people could participate in that wasn't either a side-mission or sandbox story. Since we've changed over to a free-to-make system regarding our missions. However... the 'continuity' of the main mission has been lost and it appears like no one feels the timeline is advancing without the linear progression provided by the main mission. Now, keep in mind, that the time-line can move with user generated missions; they just have to be staff sponsored.
Here is what you're voting for.
A vote for yes indicates you want main missions, which are created by the staff and guardian team, to return. These main missions will resume the role they had before they were removed prior to the most recent major website changes. A linear progressing time-line will return, however, this means that we will have to keep a better eye on the dates of user generated content because of fluid restrictions.
By fluid restrictions, we mean where your character is and when that is, and take canonical information into account. So an example would be this:
- User A creates a user-mission dated on March 1st, 2550; it takes place in the SOL System as a social thread.
- User B joins User A's mission.
- User A launches his mission with User B [and others].
- Staff release a main mission taking place on March 3rd, 2550; this mission is set in the outer colonies, multiple light years away from User A and B's characters.
- User A and B cannot participate in the Main Mission with the characters they used for the social thread. Why? They couldn't realistically be there in time because of the UNSCs relatively 'slow' speeds in FTL travel.
A vote for no means you wish to keep the current system we have now. You can read up on this system here: www.yappashalorpg.com/thread/11626/mission-creation-guide
