sketchyphoenix

anywhere you see something declared as int, declare as int64.

If I need helpers, events, or people just to be around so players can have feely-feels, great. They won't have any powers. Events can be monitored and scripted to a degree where @commands are unnecessary. The only thing to really look out for is whether or not my prospects can deal with people when they act shitty to them. I'd put up a help-desk on my server's website for everything else. I'd make an in-game script to handle in-game GM stuff since I don't trust my people with special @commands. If any action needs to be taken, from item restores to bans, a helper can put a ticket in for somebody higher up to approve and the script will handle that. I've never really had issues with any kind of egregious abuse with this system because there's nothing to abuse.

I'm gonna hit you with the realest real post here. If you're actually running a server that is pre-RE, Herc and rA might as well be the same. Out of the box: rA is better at RE, Herc is more customizable. If you're a decent programmer, pick whatever you like. You'll be writing custom systems anyway on either.

Remove or rework every mechanic in the game that is dependent on client/player performance (e.g. Double Strafe) and make it all server-side. I really dislike how much of the game's official behavior leaves holes open. Rebalance Renewal from the top down into something better streamlined yet enjoyable. More roleplay/non-combat features so there's stuff to do other than grind monsters. Make the world more interactive.

The answer is simple: You need a server that can handle the load. How much traffic is going through to your server during a DDoS? How big of a DDoS are you trying to manage? Can you afford one that can handle more than that so that you can continue to service your clients?

Where's Shinomori when you need him? The dream is real, boys! Only partial support for VS https://msdn.microsoft.com/en-us/library/hh567368.aspx

I don't think xampp is the best example for that statement. Also, for a time when the code was first implemented, the server would simply shut down after warning the user it was running as root. I don't know why it was deemed a better idea to take that away instead of using it as an opportunity to educate people on superusers. That was an irresponsible flip-flop. It's also questionable to just drop software into people's lap (on a guide) and not make a mention of a piece of that software's colorful vulnerability history. Anyway I guess the point I'm trying to make is that a lot of people like to forget that the only people who would even need these detailed guides would also need some additional tips or insight from another about what exactly they're putting on their machines so at least they can make an informed decision on whether they want to go through with it or use another method.

Well if you want me to extrapolate this to rA... When I was making this post I was going to point out how even in the wiki it either promotes the use of poor practices or does not mention any basic ones. The wiki is a part of the rathena website it is, by all intents and purposes, the official rA information hub. The wiki guide writers have included detailed instructions for downloading, installing and configuring the rA software (and its dependencies as well as some 3rd party software), so there is a reasonable obligation to at least include basic server security instructions or, failing that, mentioning them and providing external links. I would imagine people would default to the defense of: "it's the server owner's responsibility" and that reasoning is wrong. If we're going that route, then why include any support for server owners if it's all supposed to be "their responsibility"? With that reasoning, they should be knowledgeable enough to be able to download, install and configure the software (and dependencies and unnecessary 3rd party software) without any guides. Sounds like elitism, doesn't it? So why are there guides available on the official wiki? Because there are people that realize many server owners don't know what to do and need a walkthrough to get them started. Again, there is a reasonable obligation to at least help them with things like setting up their firewall and discouraging the use of software that is full of holes all the time. TL;DR throwing responsibility to server owners (yet providing step by step guides to everything (except the stuff that really matters)) is a tired elitist excuse from all the way back to the eA days.

server owners are still: using phpmyadmin. allowing remote root logins and using root/superuser level access on everything. using no firewalls You know it to be true. I know from seeing it myself it is true.

posting in the right section would help a lot.

It's the scripter's responsibility to not make bad routines that would eat up cycles. On the other hand, I wonder how server performance would look like when many script states are shuffling around many IDs.

Unfortunately, this project is no longer using svn. We git now. Both out of date. Will post a link when I finish my big change.

i'm all for people wanting to protect their work, and normally i don't comment on this type of stuff much, but threatening to ddos people that pirate it? laff if i ever get my hands on an updated copy i'd take out the backdoors myself.. because fuck that kind of attitude tbh.

sup on dem awards?

Just posting to inform everyone that I've been fixing bugs the past day or so. Ill need to put this on another repo since I don't have svn here and ill update the links when I do done

Who the hell cares what the project is? I'm loyal to the code, not the name. Also posting to add legend to the thread.

Nope. It's always been like this.

The reason it got removed was because it was hardly ever used and probably wasn't maintained either.

It can. If you loaded it plain they would all be defined as globals. Most of the commands work. The only ones I haven't worked on were item scripts. Considering the variable handling is being done entirely* in lua, all it takes is for one to write a script to do it. *still using athena's inter-server functions for sending the right variables to the right server for saving, but the db operations for it will be done in lua so anybody can use their own (supported by luadbi anyway) engine if they wanted.

Easier than you would think~

So I was making some custom code for a server and I decide that I'm going to put any custom atcommands and script commands in a custom source file as to save me some time in case a conflict comes down the road. And I noticed especially in script.c that pretty much all the macros are in it instead of the header. Should they be moved into headers ( at the very least, the most used stack macros like script_get* or script_push* ) ?

Sometime this week should be another update when I finish merges and that update should include some code to make item scripts work.

I'd go with Harmony.