Aleos

Now that I'm taking a break from 3rd skill fixes, I started working on this some. I have it pretty much done besides the fact that the char_slots option is going to be near to impossible to implement with the groups.conf. The login-server doesn't hold character data so we don't know what these values are. I'll talk with lighta and Cydh and see if there are other ways for us to possibly get something going. Other than that we can now make multiple VIP groups, each with their own VIP Permissions.

Read the first post again. It says why.

I'll take a look and see what more we can do to make it more flexible.

Third Class 2011 Post Balance Patch As of 0f7ecd0, rAthena is now up to date with the Third Class 2011 Post Balance release from kRO/iRO. It's safe to say we have finally taken a big step forward to balancing the emulator even more! This was a conglomeration work between leftover work from 3CeAM and other various sources. The information that was used mainly came from iRO Wiki Forums. iRO released their balance notes in a nice format and it was uploaded to Google Docs for everyone to see. Not all of the information is there for all skills so some skills may still need to be worked on. Feel free to look through the docs and make sure the skill is not actually wrong before you post a bug! This is just the first push forward with more to come! If you run into any issues please make a bug report for that specific skill so we can resolve it! I'll try to keep this post updated with related commits for fixes and updates. We can use everyone's help now to test the skills out since it's hard to test these skills alone and gets very boring. Bring on the bug reports! Thanks everyone! Note: I realize there are a few more changes from 2011 on with the Third Class skills and they will be updated to those newer changes when reliable sources are shown! Thanks! Follow-up commits: c1871e9 3181ff6 4019fb4 3fce137 96c768f

iRO VIP System 30648216 and d2ee0dd adds in a the official iRO VIP System. For a quick comparison of VIP and non-VIP please view here. To enable, see src/config/core.h: /// Uncomment to enable VIP system. //#define VIP_ENABLE Features: Characters per account can be increased with unique VIP slot. Storage limit can be increased per account. Base and Job experience configs allow increase rates. Base and Job experience configs allow decreased death penalties. Battle Manual experience config allows increased rates. Item Drop config allows increased rates. Gemstone skill requirement removal (Works like Mistress Card). All NPC related updates were applied in d2ee0dd which follows euRO. Please view log for full details. 1 @command and 2 new script commands were added which are detailed below. Configuration: See conf/battle/player.conf for general VIP settings. See conf/groups.conf to adjust the VIP group to your liking. See conf/login_athena.conf for VIP character increase settings. Credits to Lighta and Cydh for debugging and support and Akinari for pushing us to release it. Also big thanks to Euphy for the NPC related script! Please report all issues/bugs in the proper bug report section. Don't forget to update your SQL tables with upgrade_20131118.sql!

Completed in cdccf88.

You are recompiling each time you change the OFFICIAL_WALKPATH option right? That should resolve your issue there.

I was actually working on an implementation as well. Glad to see you got around to it. @Rage The reason is because the enum value 1 in item_types is IT_UNKNOWN and value 9 is IT_UNKNOWN2.

This is very useful. The commands that create monsters should have returned their GID to begin with. We are seeing the need to implement mob control again for minigames such as the Wave Mode dungeon.

Just to give a heads up. This actually took on a larger task. Many more official VIP features will be added in with this. Development and testing is being down now by a couple of the devs.

I actually had something like this I had created before for my server because I got tired of manually tracking the previous owner of an item. I see no issue extending the logging system.

Right now the easiest option is to do what Euphy said and provide a packaged and supported client (with hexes not applied) and the data that goes along with it. Having a custom client has been something people have asked for for years. It would be great to have an official client for rA but it would require a team of its own. There are three suggestive works in progress right now in the client section. One of which is open sourced and the other two supposedly being open sourced soon. We will just have to see where we go from here, web browser based client or normal desktop based client. Maybe a perk would be to host it alongside rA in the GIT repo. That would possibly pick up some incentive.

A battle config can exist for this. I believe it's an option in 3CeAM. I don't see any harm in adding this.

I think this is cool idea. I support the implementation of this.

You're wanting to disable guild invitations on all of Saturday and up to Sunday at 12:25AM? if (t->tmwday == 6 || (t->tm_wday == 0 && t->tm_hour == 0 && t->tm_min >= 0 && t->tm_min < 26)) { Or you're trying to disable on Saturday and Sunday, both days at 12:25AM? if ((t->tm_wday == 0 || t->tm_wday == 6) && t->tm_hour == 0 && t->tm_min >= 0 && t->tm_min < 26))

I feel like it is the way forward. It also helps with new functionality for WoE:TE stuff and blocking classes much more easily. You could add a new category restriction like "disable_class" and define a few jobs in there that can't enter the zone.

This isn't possible via a script. You'd have to make a source change in /src/map/guild.c::guild_invite. If you want to disable during WoE you can just do something like: if (agit_flag || agi2_flag) { clif_guild_inviteack(sd,0); return 0; } If you are wanting to disable for specific times outside of WoE then you'll need to check with the timer. time_t timer; struct tm *t; time(&timer); t = localtime(&timer); if (t->tm_wday == x && t->tm_hour == 0 && t->tm_min >= 0 && t->tm_min < 26) { clif_guild_inviteack(sd,0); return 0; } You'd need to change the x in the t->tm_wday to some value from 0-6 (Sunday = 0, Saturday = 6).

Yes, putting it at a higher number will increase the pet catch rate. Leaving it at 100 is official. Catching a pet is not a 50/50 chance (there are many factors that go into the formula for catching a pet) so that is something you will have to change. If you want it to be a 50/50 chance then you need to change the formula in the source. You will need to change (in /src/map/pet.c): if(rnd()%10000 < pet_catch_rate) to if(rnd()%2 < 1) Don't forget to recompile.

conf/battle/pet.conf: // Rate for catching pets (Note 2) pet_catch_rate: 100 Making it 200 will double the success rate. This will change the catch rate for all taming items.

- script OnPCLoginEvent#GMCheck -1,{ OnPCLoginEvent: if (getcharid(3) == 2000000) { mes "You can't login on this server."; close2; atcommand "@kick "+ strcharinfo(0); } end; }

conf/char_athena.conf Change the setting to no.

I support this as well.

Wrong section, but either way. Select your login table and click the Operations tab. Under AUTO_INCREMENT you'll see the value that it is set to go to next. You can adjust it here.

Ok so I have a working VIP System that is fully configurable (with support from Akinari and Lighta) following this: http://irowiki.org/wiki/IRO_Servers_Comparison The only things that aren't completed are the NPC related things but technically that can easily be done with a group ID check in the NPCs. I'm going to go over it once more and possibly add in the NPC related things.

Oh wow! Thanks Judas! I had searched the other day but looking at the post date looks like I searched right before that was posted. Thanks again!