Star Wars Galaxies Patch Notes

looking forward to it!

I am working on research and documenting (flowcharting) the functionality of various systems in the Artisan progression, started with surveying and sampling, and am starting to move into some more complicated areas (merchant vendors to be specific).

The purpose of this is to define and document exactly how the function various functions of the profession work, and to research and document what is supposed to happen in certain cases (like what happens when you try to start a survey while already sampling, or can you craft while surveying?) not to mention define what error messages or prompts should be displayed on certain events (including things like sounds, and animations and which string files from the client should be displayed and/or if its a message that is simply displayed in the chat window or if it is a System Message).

Its surprising to find out just how many small. moving parts there are, even with a function that seems really simple, like /survey …the magic of SWG, everything ties into everything else in some way or form

Well this is my first attempt at a dev blog so please be kind lol…

Having finally gotten my feet wet with the core so to speak… I have started working on the implementation of the new server configuration table structure in the core.

Now by no means am I a fabulous C++ Coder, that being said I have found the initial changes to the configuration system to be fairly simple and straight forward. There are some areas which still confuse me ( At the moment the zone server configurations has me a bit stumped to be sure) but I have successfully changed over most of the code to use the new config tables.

Currently I have the latest develop code loading off the new config tables the server compiles fine, and even runs fine, one problem i have run into is that you can login and get all the way to the char creation server selection once you do that however you cant connect to the galaxy any longer to create your character…(this one has me totally stumped, perhaps snow will have some insight).

Another problem i ran into is the config_server table has totally changed which utterly breaks how the zones are loaded from the db so thats something else ill have to ask snow about…

Well thats all for now stay tuned for part 2 as work progresses…

KBrooker

A little update on what Ive been working on…

Well first of all one of my projects is getting creatures into the database this being their attributes and so forth, this is progressing nicely if a bit ahead of where the core is currently, the idea behind this is so that when all is said and done and our spawn system is in place the creatures will already be in the database ready to go.

The next thing I am working on is Item Attribute and Schematic Attribute entry into the database as well, this job specifically requires us to make some design decisions on the current and future structure of the attributes but once we have gotten a good design implemented I should be making short work of entering a good bit of the data for the ingame schematics and items.

While I am doing this, I am also hard at work trying to learn the core source code itself and C++ As a while it is a very steep learning curve but I am making progress, hopefully soon i will be able to do more then just contribute some content to the db and actually start working on the core with the rest of the team.

And Finally… I have been hard at work on a server gui application, I must say it is coming along quite nicely I will post screenshots soon this tool will allow configuration and a gui interface for running the server from within the gui itself. Anyway thats my progress update

This week i will mostly be looking at fixing the buff bugs which have crept in and look at trying to design the replacement systems for HAM and Buffs based on Apathy’s new event stuff.

kbrooker has informed me that he will work on entering item attributes.

The last few weeks I’ve been working on a piece of technology that lets us communicate between differing parts of the application easier, the EventDispatcher. I’ve just today finished the initial implementation and have used the burstrun command as a "guinea pig" for how it works. I’m happy to report that everything appears to be working as well or better than expected!

This next week I’m going to be responsible for breaking down the current implementation for item attributes in the code so that by next meeting we can all have some sort of reference for how they work and an idea of how (if necessary) they can be improved.

In addition to item attributes investigation I will be focused on further test case usages of the event dispatcher and completing the api and tutorial documentation for it, this should be available later in the week.

For the long term my goals for the 0.3.0 milestone are implementing access fees for structures and continuing to contribute to the bug squashing efforts. In addition I will also be turning focus to how database interactions work from the code side of things, this is currently a very cumbersome system and making it easier to use will significantly improve the ease of implementing new features.

This next week I will be finishing up Sampling/Surveying and fixing random crafting bugs. I will also be taking a look at item attributes with apathy. Once the event system is solid, I will replace the existing events for sampling/surveying.