Akkarin

There are now 4266 posts in this topic. Something went wrong somewhere!! I'll hand out a prize to the member that discovers it :3 4268

@.@ Double posted - duplicate deleted. Uninformative topic title - please change. Topic moved from Script Discussion to Scripting Support. Please post in correct location in future. Edited post to put your code in a codebox. It's like you haven't even bothered. 4/4, not bad.

When you open the client, instead of typing in your username to login, you type the username you want with _m or _f to register through the client. Example: Akkarin_m would register a male account called Akkarin. The password you use when registering is also the password you'd need to use the next time you login.

You can have many char & map servers connect to a single login server, just use the same login server details in each of your configs. Editing athena-start to remove the login server is the easiest solution.

Over the course of this week I've turned my attention to the Paid Services section. A stagnant, undervalued area of the forums that has been the basis for concern throughout rAthena's history. To say this area has undergone an overhaul is an understatement. Third-Party Services The first thing on the list was to change the name to something more appropriate. Members offering their services are indeed third-party, so the name choice was a natural selection. Next, we needed somewhere to put the new service entries. Using a sub-forum for things like this was always a terrible idea, but never-mind. I created an IP.Pages databases to contain the services - this was the easy part. The hard part was making it all look snazzy. The default template files for IP.Pages are awful to say the least, so I based these templates off IPS's own version of this. It took the better part of a day to get it all looking cohesive in design, but it was well worth the time spent. The Service template itself also took some time to get right, but I think most of you will agree it looks pretty good! The "Available" and "Not available" status switches easily let other members know if a service is willing to take on more clients. This seemed to be a much better way of portraying availability than seeing "[unavailable]" in the topic title. The Available Services pills make it easier to search for third-parties offering a particular service, so the string of services at the top of the main page will filter out the services who don't offer what you're looking for. Th Contact Me button is a URL controlled by the service owner. It defaults to a link to PM them (providing they add their member id) but this could lead to various locations such as Facebook, their website, etc. The next thing i had to think hard about were public responses to these services. Paid Services were only supposed to have replies that contained a review, so I went with a review system: Users can select upto 5 stars (which show on the main service listing page) and can leave a comment. For now, these reviews must be approved by a moderator before the review content is visible. The last thing that needed working out were the guidelines for having a service listed. The old and rather stale Paid Services rules were.. unfair. After speaking with Aleos and getting some feedback from the Staff, I believe we've now got a firm method of approval! Point Scoring. Similar to how Maxmind determines a fraudulent transaction, we'll use this method to determine the outcome of a submitted service: Age of account [5] Less than 6 months, 1 point More than 6 months, 5 points Posts on forum [5] Less than 50 posts, 1 point Between 51 and 200 posts, 3 points More than 200 posts, 5 points Activity on github [10] Issue Reporting Reported 3 or fewer issues, 1 point Reported more than 3 issues, 5 points Pull Requests 2 or fewer merged PRs, 1 point More than 2 merged PRs, 5 points Uploaded Files [5] Less than 5, 1 point Equal to or more than 5, 5 points Previous warnings [5] No warnings, 5 points Maximum points available: 30, must reach 20 points to be approved. This matrix ensures that members who submit a service that are unable to contribute to the repos directly still have the opportunity to have their service listed. None of the currently approved Paid Services will be migrated automatically - everyone must go through the same process now. The old Paid Services section is now locked and will vanish next Sunday (19th Feb). When submitting, if your service is approved you should receive a forum notification (if you have them enabled), but if your service is not approved you'll receive a PM from myself giving you pointers on how to reach 20 points. A link has been placed into the "Community" drop-down in the main navigation bar. I look forward to this area becoming busy again! If you encounter any issues, please report them directly to me as soon as possible.

// Sells Potions using #CUSTOMPOINTS as currency - pointshop pointtest 123,#CUSTOMPOINTS,501:1,502:1,505:3

They are just account variables. #CASHPOINTS, #KAFRAPOINTS, #YOURROPOINTS, #OTHERPOINTS, #DONATIONPOINTS, etc.

Your directory structure should look like this: /var/www/addons/ /var/www/config/ /var/www/data/ /var/www/lang/ Etc. If you've installed it to a subdirectory instead, you'll need to put your IP in your address bar followed by the name of your subdirectory, like http://ip.add.re.ss/fluxcp

Did you install apache and php on your VPS?

Untested example: prontera,100,100,5 script Freebie 123,{ if(accfreebie > 0){ goto L_Already; } .id = getcharid(3); if(.id < 2000051){ getitem .reward, .qty; accfreebie = 1; mes "Here, have a reward!"; close; } L_Already: mes "You have already been given this reward."; close; OnInit: .reward = 501; // Red Potion .qty = 1; end; } Alter to suit your needs. You can find basic functions for scripting in the script_commands.txt file

As Dorams are not available in Pre-Renewal, it's likely the skills only exist in the Renewal /db/ files and potentially inside #ifdef RENEWAL within the src.

You put them in the html directory. On a linux VPS it's usually in /var/www/

Not yet - I've only just hit the "enabled" button! Staff will be uploading their files when they're ready. You can Follow the @Files user to be notified of new uploads

Since August of last year, @Aleos and I have been discussing the feasibility of bringing this system back to life. Once upon a time it allowed rAthena to flourish, encouraging members to create amazing scripts and designs as there was a great motivator involved; money. Being able to sell files on rAthena was good motivation for members, and with the rAT (rAthena Tax Value of 20%) it meant that rAthena itself was able to cover costs without dipping into the staff's pockets to cover shortfall. Unfortunately this feature took abit of a nose-dive due to Admin inactivity and chargebacks. Inactivity meant that members who were selling their files didn't get their payout request completed in a timely manner. With the rA PayPal account being registered in a different country to myself, I couldn't provision many requests without paypal locking me out. Chargebacks meant PayPal was reversing the transaction and charging us for the privilege of having less money. After many months of planning, we believe we have ironed out the kinks and have placed contingencies to prevent another nose-dive. To begin with, some of the rAthena Staff have been busy creating designs, scripts, source edits, etc to upload to a special user on the system. They will be appearing on an "as and when" basis continually over the next few months. The @Files user is a system bot and will be the account responsible for selling files. Staff are all aware that adding a file to the system under this user negates "commission" that they would normally earn when uploading as themselves. The funds go directly to rA's PayPal account to accrue or be used for general rAthena outgoings. If there are no major hitches, we will consider re-opening the system for members to submit their files for sale under their own account in order to earn themselves commission. Current outstanding payout requests have all been cancelled and need to be resubmitted. The requests and user credit was transferred during the upgrade from IPB3 to IPS4, but the payout method has changed slightly, so they need to be resubmitted for the system to handle them correctly. You can find this page under main navigation My Account -> Account Credit. Payouts can also be authorised by the Content Moderators - this time round there will be no need for members to wait for me to be online. Please also note, when being moved to the PayPal page you will no longer see "rAthena" at the top. Instead you will see "Industrial-Illusions". The paypal email for rAthena hasn't changed. As of last week, rAthena is officially a registered not-for-profit legal entity. We have an accountant and everything! The devs can now put rAthena on their Résumé and use each other as Professional References. Neat huh? The Staff have been preparing for this for many months and are happy to answer any questions you might have regarding the IP.Commerce App. We would be grateful for constructive feedback too!

If you'd looked at the first post you'd realise this is the page he's having problems with.

Well once it's there you're done - you won't get the same error again so look for the next one..

No. I said change localhost to your website address. Like 'ServerAddress' => 'myragnaroksite.com',

/config/application.php 'ServerAddress' => 'localhost', // This value is the hostname:port under which Flux runs. (e.g., example.com or example.com:80) Change localhost to your website address.

Check your error logs: /data/logs/errors/

For drops data you can use "getmobdrops". You can find an example in https://raw.githubusercontent.com/rathena/rathena/master/doc/script_commands.txt

Change: if(getmonsterinfo(.@id,MOB_NAME) == -1){ dispbottom "Monster ID not found"; end; } To: if (getmonsterinfo(.@id, MOB_LV) < 0 || getmonsterinfo (.@id, MOB_NAME) == "null") { dispbottom "Monster ID not found"; end; }

I did read and I understood your post. I apologise if I've come across as arrogant - I was simply trying to re-iterate my point that we provide a method of allowing custom items to exist without updates interfering with them. It's your job to look over commits that you apply to your local repo to check for conflicts. The mechanics you're looking for aren't feasible in the current setup, but perhaps @Secrets might have a way in the C++ version to create a method of overwriting single item/mob values?

Please stop necro'ing old posts Also, I wouldn't expect old scripts to be 100% compatible with the current rAthena scripting engine.

The easiest way to achieve this would be to bindatcmd @mi to a script, so you can then control every aspect of the command. For example: - script atcmd_mi -1,{ OnInit: bindatcmd "mi",strnpcinfo(3)+"::OnAtcommand"; end; OnAtcommand: if(.@atcmd_numparameters == 0){ dispbottom "Usage: @mi <id>"; end;} .@id = atoi(.@atcmd_parameters$[0]); if(getmonsterinfo(.@id,MOB_NAME) == -1){ dispbottom "Monster ID not found"; end; } mes "Name:" + getmonsterinfo(.@id,MOB_NAME); mes "Lv:" + getmonsterinfo(.@id,MOB_LV); mes "HP:" + getmonsterinfo(.@id,MOB_MAXHP); mes "Base EXP:" + getmonsterinfo(.@id,MOB_BASEEXP); mes "Job EXP:" + getmonsterinfo(.@id,MOB_JOBEXP); end; }

https://rathena.org/board/forum/99-client-releases/ There are several threads offering kRO's installer and/or files. Please use the search feature.