Mumbles

I wrote a similar topic on rAthena boards in regards to setting up a second server channel on the same machine. After deciding that running two servers on the same machine was going to be an issue, I decided to use a separate computer for the second channel. My second server is configured so that it shares only the login server with the main computer; the char and map servers are hosted on the machine itself. The second channel appears as an option after logging in (before char select), but I'm having a problem getting past that point; the client returns "Failed to connect", even though the second server is up and running. On a side note, I use harmony with my client; could this be conflicting with using a second channel? And if at all possible, I'd like to stick to the concept of using the client as a medium for both channels.

Glad you guys liked it! c:

Thanks Judas; I was able to compile successfully after doing that.

How would I go about fixing it? .-. If it's useful information to anyone, I'm running CentOS5 lol. Edit: Also, this is basically whatever I cloned from Github.

This actually seems like a better solution than other posted ones. Add the columb to your login database that reads level in addition to the group_id. @Jman: So you're saying that if I add group_id as a column, let's say, after level, in my eAthena's login database, Hercules and eAthena would be able to read from it without conflicting? From what it looks like on my end, I think it'd work; I just wanna confirm this before I make changes to a live server's database. There can be extra columns in a database without conflicting with each other. The Hercules/rAthena source code is looking for a group_id field. If there is none, it will error. If there is a 'level' field in addition Hercules simply won't read it (it won't even know its there nor will it care). Thanks for the confirmation. Now to just get it running...lol.

Not really sure what's going on in there, but I got this error while compiling in Linux. make[1]: Leaving directory `/root/Desktop/Hercules/src/char'make[1]: Entering directory `/root/Desktop/Hercules/src/map' MKDIR obj_sql CC map.c CC chrif.c CC clif.c CC pc.c CC status.c CC npc.c CC npc_chat.c CC chat.c CC path.c CC itemdb.c CC mob.c CC script.c CC storage.c CC skill.cskill.c:1: error: stray â357â in programskill.c:1: error: stray â273â in programskill.c:1: error: stray â277â in programmake[1]: *** [obj_sql/skill.o] Error 1make[1]: Leaving directory `/root/Desktop/Hercules/src/map'make: *** [map_sql] Error 2

This actually seems like a better solution than other posted ones. Add the columb to your login database that reads level in addition to the group_id. @Jman: So you're saying that if I add group_id as a column, let's say, after level, in my eAthena's login database, Hercules and eAthena would be able to read from it without conflicting? From what it looks like on my end, I think it'd work; I just wanna confirm this before I make changes to a live server's database.

Thanks for looking into it; this is just what I needed.

actually nothing if you uses the upgrade sqls...Hercules just add new tables so that your database can support new features..only attribute that will be changed is level to group_id.. ...but wouldn't changing the field name break the other server's queries? I don't feel like I got much out of this response, though I may just be misreading it; from what I understand, you're claiming that upgrading my SQL table's fields will magically make Hercules work? If anything, I feel like that would break both servers. As with JoWei's response, I think it would work out fine if I were able to edit the source so that it reads from level instead of group_id in the database; essentially, it would function normally - it would just be reading from a differently named column. If someone could direct me as to where I'd make this change, it'd help me move things along. I don't wanna break this before I even get it running. .-. And, with all cautions heeded, I still would like to make a second channel available, if at all possible. Thanks for your input so far guys.

As I stated in my previous topic, I would like to use Hercules as a second channel with my existing server's login database. The problem with this is that it uses level instead of group_id. What conflicts will I face with Hercules reading from my other login database? Is there a workaround to get the different emulators sharing login? Constructive replies are appreciated. Thanks in advance. c:

Idk, the current one looks pretty bland to me. I made a sort of banner/logo to replace it with; feel free to use it if you like it. Logo: Logo w/o slogan:

Hercules supports both (You can switch between them with a single edit on /src/config/renewal.h) This made me so happy T__T Looks like I'll be using Hercules, then.

I'm considering using Hercules for my next project, but it would be complimentary to my existing server; I plan on using a second channel hosted on a different machine, so that the game client, login server, and login database are shared. I have a number of questions, but I guess I'll start with my biggest concerns: Does the Hercules emulator use pre-renewal or renewal mechanics? Do you provide support for both, or is it entirely pre-renewal or renewal? I'm using an older version of eAthena with some of my own modifications, and I'd like to try out the Hercules emulator without having to make a separate client for it. Sorry if this was already answered elsewhere; I didn't look very hard lol.

Thank you, Ind and Trojal; both of your responses answered my questions perfectly. I hope to see great things from the Hercules project and contribute what I can.

Hi guys, I read Jman's post about why Hercules was started, and what I'd like to know is basically this: Where does Hercules stand with rAthena? Despite the fact that both emulators are open-source, does it bother you guys that rAthena is using your code to improve their project? Or are the "Hercules merges" just misleading titles? I'm just curious is all; any reply would be appreciated.