• Announcements

    by Published on 08-13-2017 08:08 AM   

    Weekly Update

    The SWGEmu Development Division

    We are using Jenkins & Gerrit. You can find all commits to Test Center Nova here. You can still report all bugs you find on Test Center Nova to the Mantis Bug Tracker. A helpful guide to bug reporting can be found here.
    Our current focus is the Publish 9 Checklist. Features planned to be in publish 9 can be seen in the SWGEmu Roadmaps

    Non linked Mantis reports are in the dev/QA area and can not be viewed with out dev/QA access.

    (Stable) = Commits are now on Basilisk
    (Unstable) = Commits are on TC Nova and are being tested

    TheAnswer (Lead Developer)
    • (unstable)[Fixed] Stability issue

    Miztah (Developer)
    • (unstable)[Fixed] Potential turn-in bug with Sarguillo phase 3
    • (unstable)[Fixed] Sarguillo phase 3 rescue mobs sending spatials while dead
    • (unstable)[Fixed] gmfsvillage event timer showing the wrong value. Mantis #7542
    • (unstable)[Fixed] Sarguillo phase 1 patrol camps should now despawn when you reachthe next camp. Mantis #7541
    • (unstable)[Fixed] Enclaves should no longer show as valid cloning points if theFRS is disabled

    ~ The SWGEmu Development Division
    by Published on 08-14-2017 01:18 PM   

    Basilisk extended downtime

    Posted August 9th 2017
    The SWGEmu Staff

    Basilisk extended downtime

    While doing a routine backup before the merge one of the HDD's died, unfortunately that was the second one we lost in a matter of weeks. Right now TheAnswer and the rest of development staff are discussing the options and trying to figure out how best to try to recover all Basilisks data. Of course, with two HDD's gone, there is a strong possibility that what they recover is too corrupt and unusable or they may not even manage to recover all the necessary data to restore Basilisk in its original state before merging it with Publish 9 code and we will be forced to do a full database wipe. Of course its still early to give any predictions but one thing is for sure, we are not at a point where we can definitely say that we will be able to move forward one way or the other.

    We apologize for the extended downtime that is probably going to last for days.

    No matter the the outcome, we thank you for your dedication and your continuous support. Of course we will keep you posted as things progress. As soon as we have any info, you will have it too.

    Update 6:

    Quote Originally Posted by Miztah View Post
    Alright folks, here's our current status. From what we can tell, our database is in good enough shape to proceed with another Publish 9 merge attempt. There's still a lot of potential for corruption or database issues to crop up that we haven't seen, so we're going to be taking some extra precautions in case those issues do pop up. Because of this, when the server is taken down, expect an extended downtime before it comes back up with the new publish.

    Quote Originally Posted by Miztah View Post
    Our current schedule is looking like Basilisk will be taken down approximately 12 hours from now. That timeframe may change between now and then. Once it's taken down, we'll start the process of backing up the database again. With the size of the database, this alone will take a fair amount of time, so we're not going to give an ETA on when it will be back up. Once Basilisk does come up, the server's new navmesh system will begin building meshes for all static and player cities as well as POI's, which will also take some time. Expect the server to remain locked for a while after it comes up.

    TLDR: When we take the server down, expect the update process to take a while to complete, especially with the issues we ran into over the past few days. We'll get the server up and running with Pub9 as quickly as we can.

    Update 5:

    Quote Originally Posted by TheAnswer
    Its a 48 hour test, so its ongoing. But, no bad news so far.
    UPDATE 4:

    Quote Originally Posted by Miztah View Post
    Alright folks, update time. We've managed a recovery of the database and we've got everything copied over to our new SSD's. We're letting Bas run for the weekend as a stress test on the database to ensure there is no corruption that didn't pop up initially. This means that for this weekend, Basilisk is going to remain on Publish 8. We're looking to give the Publish 9 merge another shot on Monday, assuming all goes well over the next 48 hours. We'll update regarding Pub9 closer to Monday when we know for sure.

    In the meantime, continue on Basilisk as you normally would. We'll be keeping an eye out on our side for any potential stability issues.

    Keep in mind that we're still doing integrity checks on the database, if we run into any database corruption between now and then it's very likely that any progress you make this weekend will be lost when we revert to a backup. This is not guaranteed to occur, but be aware that it is definitely a possibility.

    UPDATE 3:

    Quote Originally Posted by TheAnswer
    We finished uploading 1.1TB of data and now we're going though it.
    UPDATE 2:

    Quote Originally Posted by Miztah View Post
    To clarify a bit, Basilisk was up but still in the process of validating the integrity of most of the database objects. The server is currently running through our backup HDD's, which is causing the server's loading to take a lot longer than it normally would on SSD's. We shut down the login server because any actions triggered on Bas will delay the database check, and it's going to take long enough as it is.
    Quote Originally Posted by Miztah View Post
    The good news is, the server didn't explode using the recovered database. There's no current bad news, but as of right now, that's the only good news. We still have to verify that all of the objects in the database are actually valid and load properly, and it will take time. The possibility of a wipe still remains if we find too much corrupted data. Time will tell, but in the meantime you'll see Basilisk go online and offline multiple times, but you won't be able to access it. Those still connected will not be able to reconnect when they disconnect, and in the interest of getting this testing done as quickly as possible, they should disconnect on their own anyway.


    Quote Originally Posted by Ivojedi View Post
    About the loading status: We are attempting to load a test db instance to check for data integrity. This should give us an indication of whether we'll need to wipe or not. It's loading on the HDDs so it's slow and will take time. Thanks for the continued patience.

    ~The SWGEMu Staff
    by Published on 06-10-2015 08:20 PM   

    Join Staff - SWGEmu EC/CSR/Support training program

    June 2015
    The SWGEmu

    Greetings SWGEmu Community!

    As a volunteer project, SWGEmu is constantly looking for new community members to step up and assist and support the community. If you are interested in taking on the responsibility of an SWGEmu Staff member to further our goals, we encourage you to take the time to apply for our SWGEmu
    EC/CSR/Support training program.

    The SWGEmu EC/CSR/Support training program is designed to introduce community members to different aspects of the duties and responsibilities of the SWGEmu Staff, while giving them a chance to develop a close relationship and eventually join the SWGEmu Staff team.

    The following are the minimal requirements to be accepted into to this program:
    • Professionalism
    • Excellent work ethic
    • Positive attitude
    • Ability to work and learn in a team environment
    • Sufficient free time
    • Knowledge of the SWGEmu Project is required

    Program Details
    1. Apply to the SWGEmu EC/CSR/Support training program by submitting an application (see below).
    2. After reviewing the application, an interview may be offered to accept or decline the volunteer.
    3. Once accepted for SWGEmu EC/CSR/Support training program, the volunteer will be mentored by a member of the SWGEmu Staff for a period of 2 months.
    4. During these 2 months, the intern will assist in IRC, on forums and on Live support.
    5. After the SWGEmu EC/CSR/Support training period has ended, an evaluation will be completed by the SWGEmu Staff to determine if the SWGEmu EC/CSR/Support trainee has met all duties and expectations expected of them.
    6. The trainee may then remain as a support assistant or apply for an available position in the SWGEmu Staff.
    7. If accepted, an apprenticeship period of 4-8 weeks will begin and the apprenticeship will work closely with the staff member of the department they applied for.
    8. At the end of the apprenticeship, another evaluation will be completed to determine if the intern would be a good fit for the chosen SWGEmu Staff department.
    9. If accepted, the apprentice will be offered the opportunity to join the SWGEmu Staff as a full-time member.
    10. The new SWGEmu Staff member will perform their department's duties as well as continue assisting with Support.
    Upon completion of the internship period, the following positions may be applied to for apprenticeship:
    • Support Staff (Community Support Representative)
    • Event Coordinator
    • Community Relations (Forum Moderator)
    We are very excited to be offering this program to our community. It is our hope that it will bring forward community members that want to help SWGEmu succeed and provide our Community with the best experience possible.

    Submitting Your Application

    Please complete the application below and email it to [email protected] with 'SWGEmu Internship Application' as the title and the application attached. If you are selected to participate, we will contact you by email informing you of such and provide information about the next step in the process.

    What is your forum account name?

    What is your in-game character name?

    What is your IRC nickname?

    What is your age?

    What is your profession in real life? If you are a student, what are you studying?

    What time zone do you live in? What times/days of the week will you usually be available to spend time assisting in Live Support?

    Do you know any current or former staff members? If so, how?

    How long have you been following this project?

    Why do you want to become a member of the SWGEmu EC/CSR/Support training program?

    Please write a short paragraph detailing what Pre-CU Star Wars Galaxies means to you.

    If you are accepted into the SWGEmu EC/CSR/Support training program and are looking at applying for a SWGEmu Staff position, what position would you apply for and why?

    ~The SWGEmu Staff
    by Published on 06-09-2011 03:54 PM   

    SWGEmu Recruitment

    Updated: April 12, 2013
    Development Division

    We are looking for passionate programmers who can dedicate some of their free time to volunteer for this project.

    Required Skills

    - Intermediate knowledge of C++ and/or Java
    - Minimum experience with the Unix/Linux environment
    - Familiar with scripting languages such as LUA

    Recommended Skills

    - Object oriented programming and design patterns
    - Understanding of transactional systems and client/server architecture
    - Concurrent programming (threads, mutexes)
    - Experience with SQL
    - Reverse engineering skills
    - Game modding experience

    How can I contribute?

    Contributing is easy if you have set up the environment and git you just commit reviews to http://gerrit.swgemu.com as simple patches. After we approve some of your patches and we see that you're comfortable with the framework you get git access so you can commit directly.
    If you have questions about the implementations you can directly ask TheAnswer on IRC through personal messages or in the #opendev channel.

    ~ The SWGEmu Development Division
    by Published on 09-08-2014 01:31 PM   

    Please read all SWGEmu Rules And Policies

    September 2014
    SWGEmu staff


    The only exception to SWGEmu Rules and Policies is the Sarlacc Pit 2.5 section, which has its own set of Rules and Policies.