Akkarin

I know in other threads i've asked for input on the current modules that ship with the default rA FluxCP, but are there are modules that you guys would like adding in? It doesn't matter if it doesn't exist, we can always hammer it out and commit it to the repo if its a good idea. Just looking for some thoughts.

I did a search on the forums using the search function. In future, please make use of it. Link in a signature led me to here: http://www.mediafire.com/folder/ivfidqkhb6qdd/Ragnarok_2013_client#euir9g9639zwt Also posted in wrong section. Topic moved.

petheal commit: d20cbca Deprecated 'petheal' script command has been removed. Please update your pets with the appropriate petskillsupport command.

No. If it's not a ' in the config files in between the other ' ' then you're good. This looks like an issue with config/servers.php 'Database' => 'ragnarok', Or 'Database' => 'ragnarok', Could be wrong, but it's best guess with the info you've provided. Unless your database is called -172 then ignore the above.

The error in your screenshot is not being caused by Emistry's script.

Everything is easy if you know how 1. git clone to server 2. upload RO data files/GRFs to client/ and put them where the files tell you to 3. install wsproxy and leave running in a 'screen' session 4. open up /examples/api-online-frame.html and edit ROConfig() to suit your needs, then open the file in your browser If you're struggling, enable debug in /client/configs.php Everything else that you need to look at if you're stuck is in the js console. I've found that Firefox seems to be more helpful than Chrome with this part, but roBrowser seems to run better in Chrome. As far as using it in dev/test mode goes, that's pretty much it. For use in "production" environment, compile scripts using /tools/build and set 'development: true', to false. If you're still stuck, pm me on discord.

You've put a character like ' or " in a config file where you should'nt have. Most likely in servers.php.

It might be more useful to send the files to one of the developers..

The same with eAthena

I believe you're going to have to create your own cutin because it will depend on the items you put in the script. can u guide me how to make? i dont know.. As I've said, there's a page on the wiki for cutins: https://rathena.org/wiki/Cutin

The original FluxCP is designed for eAthena. https://code.google.com/archive/p/fluxcp/downloads There's quite a few differences between the two versions now, and changing everything in the rA version to be compatible will take a while @.@ You'd be better off using the original and throwing modules into it that you want.

You can use the search function to find several daily reward scripts. There is a page on the wiki relating to cutins, which also has a search feature.

Did you try Emistry's solution? It already looks like it will suit your needs.

SSO isn't a bad idea and has been done before, but players still needed to create a password unless you plan on creating a src diff to accept an oauth token and ping back to the service for authorisation. Otherwise it doesn't seem very seamless.

I guess you could add a check to make sure that if .@x$ exists or is not null or is not 0 then echo out that line in the atcommand @warp line..

Again, untested: - script atcmd_go -1,{ OnInit: bindatcmd "go",strnpcinfo(3)+"::OnAtcommand"; bindatcmd "warp",strnpcinfo(3)+"::OnAtcommand"; end; OnAtcommand: if(!getarraysize(.@atcmd_parameters$)) { message strcharinfo(0), "Invalid syntax."; end; } .@cmd$ = .@atcmd_command$; .@location$ = .@atcmd_parameters$[0]; .@x$ = .@atcmd_parameters$[1]; .@y$ = .@atcmd_parameters$[2]; dispbottom .@cmd$ +" used"; if( .@cmd$ == "@go" ){ dispbottom "found @go"; if( .@location$ == "0" ){ dispbottom "found 0"; if(BaseLevel < 100){ dispbottom "You need to be atleast Base Level 100 to go there!"; } else { atcommand "@go 0"; } } else if( .@location$ == "1" ){ dispbottom "found 1"; if(BaseLevel < 100){ dispbottom "You need to be atleast Base Level 100 to go there!"; } else { atcommand "@warp invek"; } } else { dispbottom "found something else"; atcommand "@go "+ .@location$; } } else if( .@cmd$ == "@warp" ){ dispbottom "found @warp"; if( .@location$ == "invek" ){ dispbottom "found invek"; if(BaseLevel < 100){ dispbottom "You need to be atleast Base Level 100 to go there!"; } else { atcommand "@warp invek" + .@x$ + " " + .@y$; } } else { atcommand "@warp "+ .@location$ + " " + .@x$ + " " + .@y$; } } else { dispbottom "Odd.. nothing processed.."; } dispbottom "@ end"; end; } Just needed additional parameters adding for the x and y coordinates.

Bah. Sometimes i forget which language i'm using *_* /me edits. - script atcmd_go -1,{ OnInit: bindatcmd "go",strnpcinfo(3)+"::OnAtcommand"; bindatcmd "warp",strnpcinfo(3)+"::OnAtcommand"; end; OnAtcommand: if(!getarraysize(.@atcmd_parameters$)) { message strcharinfo(0), "Invalid syntax."; end; } .@cmd$ = .@atcmd_command$; .@location$ = .@atcmd_parameters$[0]; dispbottom .@cmd$ +" used"; if( .@cmd$ == "@go" ){ dispbottom "found @go"; if( .@location$ == "0" ){ dispbottom "found 0"; if(BaseLevel < 100){ dispbottom "You need to be atleast Base Level 100 to go there!"; } else { atcommand "@go 0"; } } else if( .@location$ == "1" ){ dispbottom "found 1"; if(BaseLevel < 100){ dispbottom "You need to be atleast Base Level 100 to go there!"; } else { atcommand "@warp invek"; } } else { dispbottom "found something else"; atcommand "@go "+ .@location$; } } else if( .@cmd$ == "@warp" ){ dispbottom "found @warp"; if( .@location$ == "invek" ){ dispbottom "found invek"; if(BaseLevel < 100){ dispbottom "You need to be atleast Base Level 100 to go there!"; } else { atcommand "@warp invek"; } } else { atcommand "@warp "+ .@location$; } } else { dispbottom "Odd.. nothing processed.."; } dispbottom "@ end"; end; } You can do away with all of the dispbottom's everywhere, they're just there for debugging.

- script atcmd_go -1,{ OnInit: bindatcmd "go",strnpcinfo(3)+"::OnAtcommand"; bindatcmd "warp",strnpcinfo(3)+"::OnAtcommand"; end; OnAtcommand: if(!getarraysize(.@atcmd_parameters$)) { message strcharinfo(0), "Invalid syntax."; end; } .@cmd$ = .@atcmd_command$; .@location = .@atcmd_parameters$[0]; switch(.@cmd){ case "go": switch(.@location){ case 0: if(BaseLevel < 100){ dispbottom "You need to be atleast Base Level 100 to go there!"; } else { atcommand "@go 0"; } break; case 1: if(BaseLevel < 100){ dispbottom "You need to be atleast Base Level 100 to go there!"; } else { atcommand "@warp invek"; } break; case default: atcommand "@go "+ .@location; break; } break; case "warp": switch(.@location){ case "invek": if(BaseLevel < 100){ dispbottom "You need to be atleast Base Level 100 to go there!"; } else { atcommand "@warp invek"; } break; case default: atcommand "@warp "+ .@location; break; } break; } end; } Currently untested, but this should provide you with a good base to edit without breaking it Should be fairly easy to follow so you can add additional locations in the future.

Well... you need an elseif in there, and your error is because the script is trying to warp you to a map called "0". Give me 20 mins to get to a PC and i can rewrite it for you and test.

Did you change: packet_db_ver: default in db/packet_db.txt and #define PACKETVER 20130807 in src/common/mmo.h and then recompile your server?

I have no doubt that it works, i'm just baffled by the unnecessary use of an array and so many variables where a very simple script would do the same job. I see no valid reason to reinvent the wheel when there's a perfectly good wheel in the repo that can be tweaked to requirements, that's all.

They create the list of items sold in the shop. From script_commands.txt: *npcshopadditem "<name>",<item id>,<price>{,<item id>,<price>{,<item id>,<price>{,...}}}; This command will add more items at the end of the selling list for the specified NPC shop or cashshop. If you specify an item already for sell, that item will appear twice on the sell list. The function returns 1 if shop was updated successfully, or 0 if not found. NOTES: - That you cannot use -1 to specify default selling price! - If attached shop type is market shop, need an extra param after price, it's <qty> and make sure don't add duplication item! --------------------------------------- *npcshopdelitem "<name>",<item id>{,<item id>{,<item id>{,...}}}; This command will remove items from the specified NPC shop or cashshop. If the item to remove exists more than once on the shop, all instances will be removed. Note that the function returns 1 even if no items were removed. The return value is only to confirm that the shop was indeed found.

The iRO wiki page gives you all the map locations for NPCs and all the item IDs involved in the quest. It shouldn't take much more than an hour to script this. You can use the script_commands.txt doc for help with creating an NPC, getting and deleting items and how to reward EXP. Since it's from 2014, i doubt anyone will have the official dialogue, so you may as well make it up as you go along.

A quick way to do this without changing any of the source would be to overwrite the @go command using bindatcmd: - script atcmd_go -1,{ OnInit: bindatcmd "go",strnpcinfo(3)+"::OnAtcommand"; end; OnAtcommand: if(!getarraysize(.@atcmd_parameters$)) { message strcharinfo(0), "Invalid syntax."; end; } .@location = .@atcmd_parameters$[0]; if(.@location == 0){ if(BaseLevel < 100){ dispbottom "You need to be atleast Base Level 100 to go there!"; } else { atcommand "@go 0"; } } else { atcommand "@go "+ .@location; } end; } Tested and works on my localhost, you'd need to edit to add more if/else's if you want to restrict other locations.

There's a floating rates NPC script already in the rA repo: https://github.com/rathena/rathena/blob/master/npc/custom/etc/floating_rates.txt Just change the OnHour labels to something else: OnClock<hour><minute>: OnMinute<minute>: OnHour<hour>: On<weekday><hour><minute>: OnDay<month><day>: This will execute when the server clock hits the specified date or time. Hours and minutes are given in military time. ('0105' will mean 01:05 AM). Weekdays are Sun,Mon,Tue,Wed,Thu,Fri,Sat. Months are 01 to 12, days are 01 to 31. Remember the zero. So You'd use OnFri0000: and then use OnMon0000: to set the specific rates back again.