Jump to content

Nameless2you

Members
  • Posts

    351
  • Joined

  • Last visited

  • Days Won

    2

Everything posted by Nameless2you

  1. Remember that zone 1 restriction already exist, so what ever other map has that restriction will now be unable to use the item 547 on that map.
  2. server time = computer time check the systems time and change it accordingly, does not require server restart
  3. I'd prefer that to then be "in addition", taking my suggestion from lRO, http://board.limit-ro.net/index.php?/tracker/ . It just makes overview easier or at least that's how I feel about it.
  4. That's something different you can add/change that url in clientinfo.xml it was as you mentioned the registration link. In a live running in-game environment you need as Emistry mentioned some source mod and yes the new clients allow you to add a website, 1 website where the "Ragnarok" button is, should appear if you open alt+v.
  5. This should do.. http://upaste.me/c657400ba4e4724 if not please state the error the map server is giving, best if screenshot
  6. Find: waitingroom "Battle Station 5 Players",5, and replace it with waitingroom "Battle Station 3 Players",3, Remember there are 3 KVM scripts and it's 2 teams each time so you will have to find the first line 6x. Find: if( .@Guillaume < 5 || .@Croix < 5 ) and replace it with if( .@Guillaume < 3 || .@Croix < 3 ) this you will only find 3 times.
  7. I believe the Bug Tracker needs to be organized better, meaning instead of having all the skills in 1 section, create subcategories inside the skill folder for jobs, so Rune Knight, Royal Guard and so on, that way posts such as these: http://rathena.org/b...ebalancing-kro/ could possibly be handled better and it's be more organized. Players, server owners or who ever posts any information could possibly target specific jobs or just have a simpler overview. I know it would mean a lot of subcategories considering all the jobs but i highly believe it would be for the better, would help solving skill issues if one is attempting to fix all skills for a specific job. TL;DR: Add sub-categories in the 'Skill' section for each 3rd job.
  8. Ok those are your times, but when do you want it to announce? On a side note: Pretty intense woe schedule.
  9. So I just thought maybe adding wiki.rathena.org would be another great way to improve rAthena, instead of having to type out rathena.org/wiki, of course you can bookmark it but typing wiki.rathena.org is easier and usually you'd only need to type out wiki.ra because it'll have it cached. This would be in addition of rathena.org/wiki, and not to replace it. Well that's all I got.
  10. it was added again Removed again
  11. So I've come across this new command makeitem, it's pretty nice but I got 2 suggestions for it. Enable omitting x & y, so the item can be spawned randomly on the map. Enable x1,y1,x2,y2; that way you could specify the location of the item within a specific area.
  12. Read lighta's post please. Not every change only custom stuff or major things. For instance adding a new script command makeitem or other stuff that has significance, it also helps for the future when you need support for the specific command and want to ask the creator.
  13. Well theoretically there should be one in Payon, Shunbi or w/e that guy was called should accept those tickets and then refine the item to the item specified level..
  14. I have to disagree on this part, as much as commenting is not really required, leaving the authors name on a specific section if they've created it should be ok, that way they can get some attention and gratitude for the work they've done and not be generalized as simple "dev". The do nothing example of course is although incorrect because it should be does nothing, but aside from that I agree with it. However I wouldn't mind if behind getitem 601,1; there was getitem 601,1; //apple , now the example is silly because everybody knows 601 is an apple but, not everybody knows that 12103 is a bloody branch. As to indenting, I know I personally don't use it too much when I'm on a script spree because I know what I'm doing, but I have to agree with it's usage, it makes things easier for everybody else and therefore I support it, however anything that's in a comment should be up to the author, one could go through each script and change it but that would simply be aesthetic and not required as it isn't required to be read anyways so why make it pretty.
  15. ^ don't need that one xD
  16. Skulls, like yours that are dropped in pvp are just normal skulls, id 7420, nothing special about them, they're just signed with your name, no different worth or any other id.
  17. my suggestion is using setquest, <id>; and giving the quest 24 hour delay, that way it'll be easier script wise.
  18. Suggest you add the script to the post, or http://upaste.me the script so it can be added if you don't know how. Also concerning alejandra's script, I would add ' / 64' behind the '5") + "]' else it'll just show the amount of users but not the limit of the room, although for the limit you'd have to consider adding another possible line, since just putting into plain text won't prevent more players from accessing it.
  19. Just disable it in the item_noequip.txt ._. and add a mapflag to prontera restricting it, that'll allow you to expand on things people can't do in prontera such as casting annoying spells for instance..
  20. What Aerie ment was, change the announce "some text",1; to announce "some text",3; And what he also ment was that you can all look it up here: http://rathena.org/wiki/Announce
  21. Map only or player only? Possible script: http://upaste.me/9e5c319f7627bda announces to the entire map and only if player is in prontera
  22. Sounds like a rather easy task using character variables & OnPCLoginEvent.. However I suppose it would be a lot easier if you could provide us with the initial script that you want edited so it works even after relogging. Paste it here: http://upaste.me
  23. It is not part of a script. And vending using zeny or cash is not possible without a source edit, therefore this ist the wrong section. However it's already reported for a move.
  24. there is a delay timer on how often you can enter Endless Tower.. which is 7 days (1week) and 6 hours.
×
×
  • Create New...