I've svnsync'd both the old obsolete sourceforge and the new googlecode svn repositories on a visualsvn server located on my server at home. This will leave a redundant copy in case something happens to access we can still make checkouts of the source as it was and place diffs into the forum until there is a chance to update the main svn repos. Once their updated resync will be ran and can maintain that redundant fuzzy feeling I like to have when working on any project.

If anyone has a complaint about this or concern please don't be bashful.

EmulateS
~Tom~

FYI, EQ2Emu Devs work off a private SVN, which no longer gets automatically synchronized to SourceForge (I do not have the account info) nor the new GoogleCode SVN. Until there is more development interest from the community, our efforts will remain private until we reach a point of stability where code can be released to GoogleCode SVN.

Tom, if you are making code changes, you can join the Dev team and get access to this private SVN - but please only do so if you plan to actually commit changes The sources are barely different at this time, between Dev and Public, due to the fact we have no active development going on right now.

Thanks for the backup though.

John,
I understand about the private svn it makes sense too. I'd like to get on board, but I don't see any dev's to get on board with lol. If someone is still doing the coding and I'm incorrect please point me in the direction of gaining access. I would like to get started on issues I've found just by logging into the emu as it stands. Such as omg those f'ing harvest auto attacks and spells that have visuals but no effect or spells that effect with no visual. Just a couple of things, I'm aware there are many other issues, just thought I'd hit a couple over the head I can't stand.

Emulates,
The harvesting/attack bugs are content issues I believe. I know the sprint one was and I looked at foresting in the db and it is set to 'unfriendly' so it should start autoattack but I have yet to test them.

I can code but have yet to really do anything. Took me a while to believe the bug tracker was up to date. I'm not sure who else can code (beside you ).

I really liked the doxygen documents you made and hope to use them to start with some coding, but just haven't gotten there. So far the few (read: very few) bugs I have 'found' seemed to be content issues. I am starting to think that the code is really solid and most issues might be content related. Of course there are still lots of missing features but that is a horse of another color.



Syl

Sylaei wrote: The harvesting/attack bugs are content issues I believe. I know the sprint one was and I looked at foresting in the db and it is set to 'unfriendly' so it should start autoattack but I have yet to test them.

I assumed it was a content issue based off prior Bug Tracker logging, but wasn't positive. Thank you for clearing this up for me.

Sylaei wrote: I am starting to think that the code is really solid and most issues might be content related. Of course there are still lots of missing features but that is a horse of another color.

Your right I noticed quite a few non-implemented features that need to be worked on diligently.
I'll start with those.

Would be nice to see some coding movement again
I'm here to help out in anyway I can, I am still learning the C++ language, so keep that in mind, but if there is a data struct or opcode question I am the man for that

I am still collecting and gathering spell information and have been working on some lua scripts also.

That is fantastic Zcoretri. Thanks for the help and insight. Same goes for yourself, if you have questions about C++ or coding in general please don't hesitate to ask. There's no reason not to learn from each other.