Jump to content

lioran

Members
  • Content Count

    3
  • Joined

  • Last visited

Everything posted by lioran

  1. Version 1.00

    104 downloads

    Follow Alice into the forest in Niflheim and try to figure out what is wrong with her. This is an instance dungeon that includes 3 maps, 2 quest and 3 boss for pre-renewal. One of the boss is a hidden extra to the instance with a small quest including a multi stage battle that will take a few days to fully complete. There are no default drops or rewards to the dungeon quests or monsters, So you will need to add those yourself. Although the instance is Pre-renewal, it can be used for renewal but you will need to revamp the monsters else they will be extremly weak. If your server is a highly modified pre-re server you might wanna tweak the monster since they are geared toward original RO servers. More detailed info in readme.txt Map used are Haunt_e and Haunt_1 made by Syouji
  2. View File Alice's Nightmare Instance(Pre-Re) Follow Alice into the forest in Niflheim and try to figure out what is wrong with her. This is an instance dungeon that includes 3 maps, 2 quest and 3 boss for pre-renewal. One of the boss is a hidden extra to the instance with a small quest including a multi stage battle that will take a few days to fully complete. There are no default drops or rewards to the dungeon quests or monsters, So you will need to add those yourself. Although the instance is Pre-renewal, it can be used for renewal but you will need to revamp the monsters else they will be extremly weak. If your server is a highly modified pre-re server you might wanna tweak the monster since they are geared toward original RO servers. More detailed info in readme.txt Map used are Haunt_e and Haunt_1 made by Syouji Submitter lioran Submitted 07/06/18 Category Quest, Shops, Functions & Algorithms  
  3. Ok I know how people react when you start talking about RNG and such. people say its luck and all but this can be tested by devs. So I started to notice weird things when I moved to hercules. Bunch of stuff that just make you go "damn that's bad luck"... or is it? Here are a few occurrences . cases 1 killed 40 monster and not getting its 25% drop 40 times in a row . If you do that math it comes down to 1 out of 99437 to happen. cases 3 killing 15,000 of a monster on a x5 rate server not getting a single card (multiple case of that in a short span of time for a lot of people) cases 2 Getting 3 cards on a x5 rate server in 10 kills (you calculate that on your own) So now with that being said. Most people would be incline to say "well that's just bad luck". Problem here is not that it happened...the problem is that it happened to several people in a short amount of time on a small community. Saw it happening a bunch of time on a low population server(100+) in a short amount of time and now seeing it happen on a big population server(700+) repeatedly. If you do the math just getting no card after 15000 on a x5 server is about 1 out of 1811 occurence. (0.9995^15000) So once in a while you expect it to happen. but not multiple time in a really short period of time that's just absurd. Even it just happening twice in your entire life is absurd. (more number crunch 1 out 3,281,303 to happen twice in a row but hunting 15000 takes alot of time) I heard that the RNG seed used for drop takes character ID, process ID, and clock. My question is this... Why would you ever include a number that never changes in a Random number generator seed. I don't know if that's the problem but there is obviously something wrong here. I know I would never host a server with a RNG like that. So it would be good to look into that, run tests to try different IDs. See if some IDs are more bias toward small number vs big numbers. It is NOT RNG if the seed is bias toward certain numbers. This post is not to start argument... this is just to try to get someone to check maybe whats wrong. I have some programming knowledge but not enough to dive into this.
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.