Archive for February, 2010
Powerking’s Development Blog – Entry I
by admin on Feb.28, 2010, under SWGANH - Development
Hello everyone! I thought I’d take the opportunity to introduce myself to the community as well as keep everyone informed of my work in the SWG:ANH core.
==INTRODUCTION==
I am Powerking, and I’ve been working with SWG modding, emulation, and reverse engineering for about 5 years now (long time, inorite?). I have worked with several teams throughout this span of time (with contributions varying greatly). I started with the SwgEmuMods group, which was a group that intended to create mods for the swg client. While there I started a small project (that quickly grew out of my hands), called cuemu. I’m not going to take credit for anything that the cuemu did, because it was mostly put together by others (apathy). From there I wandered to the SwgPreCU team and eventually bounced to the OSSWG (Persistent Worlds) team. After taking a short break from the SWG scene I returned to come do work for SWG:ANH.
Upon my arrival I received a copy of the source code, some instructions, a few logins and was told to have at. I quickly established what I wanted to be my first area of work: Scout. I’ve only been working with the core for about a week and a half, but I’m already starting to feel that I’ve got a good grasp of it’s structure. I’ve fixed several bugs (some minor, some enormous), finished camp implementation (Pictures Incoming!), and have completely added in foraging!
Next Stop: TROW TRAP! (with a brief trip to Medical Forage first because it’s so much like Forage)
Despite what some have said: Fun times and great things are happening here at Swg:ANH!
Twitter RSS
by admin on Feb.28, 2010, under Star Wars
You can now follow us on Twitter!
http://twitter.com/swgpatchnotes
Re: Lloydyboy’s Development Blog I
by admin on Feb.28, 2010, under SWGANH - Development
Ah. For a Masters we (USA) write a thesis and for a PhD we write a dissertation. So when you said dissertation, I jumped to an erroneous conclusion. Congrats, just the same! A Masters is not a piece of cake!
Re: Lloydyboy’s Development Blog I
by admin on Feb.28, 2010, under SWGANH - Development
Ah. In the UK we use the terms the other way around.
Changeset [1885]: [fixed] compiling
by admin on Feb.28, 2010, under SWGEmu Timeline
[fixed] compiling
Changeset [1884]: [updated] idlc compilation
by admin on Feb.28, 2010, under SWGEmu Timeline
[updated] idlc compilation
Object Restructures, and a Deadlock?
by admin on Feb.28, 2010, under SWGEmu Developer Chats
As you know, our Test Center will "crash" operation from time to time, lately more more often than not. Why, you ask?
If you’ve been keeping up on current affairs, you know that the focus of development shifted some time ago from content "branches" to the fundamental codebase.
Throughout the past few years this project has seen many Developers come and go, each with their own unique contributions to the code. However, the sheer number of contributions placed a severe burden on a few Core Devs that assumed the responsibility of Integrating all this new code into the "Tree" successfully. This is not without challenges. Things such as deadlocks, crashes, memory-leaks, etc are a constant threat.
When these issues arise, a condition known as a "Deadlock" can occur. In our case, a Deadlock means that several aspects of the code are awaiting one another to compete, causing the server to grind to a halt. Please take some time to understand what a Deadlock is.
At a certain point, the decision was made (and wisely) to take stock of what had been accomplished, reviewing current code and ensuring that the "Tree" was sufficiently workable. It was determined that modifications were necessary, not only to clean up the current code, but to ensure that future contributions would be EASILY adapted to the complete Tree, without reconfiguration and coding of the entire codebase each addition.
As a result, the OR was born. SWGEmu has been many months into this, and significant progress has been made. However this post isn’t to note progress, it’s intention is to inform about the OR and what a "Deadlock" actually is. The community needs a place to be able to point new members to, so they can become informed. Hopefully this post is a start. I encourage all who read this to FURTHER review the Announcements, Community News posts, and the Bi-Weekly Updates. All available information is represented there.
At this point the emphasis on the current revision was marginalized in light of the need to lean out what was going to be workable moving forward. However, you guys are playing, and a few of our guys have made valiant attempts (read: TA, Kyle etc etc, Kellina, Learning, all QA) to make what’s up, work. As a result you’ve seen a lot of jedi work. Of course, because that was the patch, for you, as a gift.
HOWEVER! Please do not assume that Jedi is the Emu’s focus, it is not. This was done for you folks, as a gift, while the slow process of the OR is worked through.
Please be patient while our 100% volunteer staff continues to chip away at the OR. As you can see, we’re still here. This is simply not a time for momentous leaps and bounds. However that time will come, and we’ll need to you help us test the new code and prepare for the final push.
Thank you, as always, for your ongoing support of Pre-Cu and SWGEmu!
* Please remember, you can check server status in the Java client at SWGEmu IRC or your favorite IRC client. Please see #test and #status for that latest status updates.
SWGEmu
Object Restructures, and a Deadlock?
by admin on Feb.28, 2010, under SWGEmu TC Patches
As you know, our Test Center will "crash" operation from time to time, lately more more often than not. Why, you ask?
If you’ve been keeping up on current affairs, you know that the focus of development shifted some time ago from content "branches" to the fundamental codebase.
Throughout the past few years this project has seen many Developers come and go, each with their own unique contributions to the code. However, the sheer number of contributions placed a severe burden on a few Core Devs that assumed the responsibility of Integrating all this new code into the "Tree" successfully. This is not without challenges. Things such as deadlocks, crashes, memory-leaks, etc are a constant threat.
When these issues arise, a condition known as a "Deadlock" can occur. In our case, a Deadlock means that several aspects of the code are awaiting one another to compete, causing the server to grind to a halt. Please take some time to understand what a Deadlock is.
At a certain point, the decision was made (and wisely) to take stock of what had been accomplished, reviewing current code and ensuring that the "Tree" was sufficiently workable. It was determined that modifications were necessary, not only to clean up the current code, but to ensure that future contributions would be EASILY adapted to the complete Tree, without reconfiguration and coding of the entire codebase each addition.
As a result, the OR was born. SWGEmu has been many months into this, and significant progress has been made. However this post isn’t to note progress, it’s intention is to inform about the OR and what a "Deadlock" actually is. The community needs a place to be able to point new members to, so they can become informed. Hopefully this post is a start. I encourage all who read this to FURTHER review the Announcements, Community News posts, and the Bi-Weekly Updates. All available information is represented there.
At this point the emphasis on the current revision was marginalized in light of the need to lean out what was going to be workable moving forward. However, you guys are playing, and a few of our guys have made valiant attempts (read: TA, Kyle etc etc, Kellina, Learning, all QA) to make what’s up, work. As a result you’ve seen a lot of jedi work. Of course, because that was the patch, for you, as a gift.
HOWEVER! Please do not assume that Jedi is the Emu’s focus, it is not. This was done for you folks, as a gift, while the slow process of the OR is worked through.
Please be patient while our 100% volunteer staff continues to chip away at the OR. As you can see, we’re still here. This is simply not a time for momentous leaps and bounds. However that time will come, and we’ll need to you help us test the new code and prepare for the final push.
Thank you, as always, for your ongoing support of Pre-Cu and SWGEmu!
* Please remember, you can check server status in the Java client at SWGEmu IRC or your favorite IRC client. Please see #test and #status for that latest status updates.
SWGEmu
