FlowsionMS Source - OdinMS Fork -

Status
Not open for further replies.
Re: [RELEASE]FlowsionMS Source - OdinMS Fork -

i had this since revision 80 or something and now its up to rev 139
 
Re: [RELEASE]FlowsionMS Source - OdinMS Fork -

The OdinTeh fork has been renamed and merged with the FlowsionMS Source. Lily has merged with OdinTeh and now FlowsionMS as well. We will be working hard to continue the work that Serpendium and Matze did with OdinMS and making sure our work is open source like it is supposed to be. Look forward to tons of updates and revisions just the same as OdinMS! :)

Temporary SVN & TRAC

SVN:



TRAC:


Website:


What to Expect:
- .60 Support
- . XML Support
- Bug fixes to d/c errors
- Skill fixes
- Zakum PQ
- PQ's
- 4th Job Quests
- Pianus / Papulatus / Zakum Fixes

and wayy more. There will be a huge update on Friday posted!

Sorry for this noob question,
What can I use better, SVN or TRAC?
 
Re: [RELEASE]FlowsionMS Source - OdinMS Fork -

Umm to everyone saying nice release, this isn't so much a release than a news update. considering that they are merging with odinteh, everyone using odinteh will be changing to it anyway. Nice to know that Odinteh is progressing.
 
Re: [RELEASE]FlowsionMS Source - OdinMS Fork -

I'm glad you're helping out Flowsion, but I highly think you should of kept it closed source, even if it meant I couldn't use it lols. But I'm out of this so meh.

Anyways, I think you should of left if closed source because people are just going to get it and make very high rate servers and make you lose your players. But since it's already done why not do this.

HARD CODE the EXP/MESO/DROP RATES into the source so they can't be changed. That way you can set the rates for every other server that uses it so that the owner of that server can't have the high 500x+ rates. Hard code it to like 80x or lower that way all the servers are low rates and your server will still be the premier one since you know how to run a successful low rate server. Just an idea.
 
Status
Not open for further replies.
Back