Jump to content

  •  

Bug Tracker Migration

June 3rd
Good news everyone! The staff has decided that it is time to slowly kill off this Bug Tracker. We will begin the process of slowly migrating from this Bug Tracker over to our Github Issues which can be found here: https://github.com/HerculesWS/Hercules/issues

Over the next couple of days, I will be closing off any opportunity to create new reports. However, I still will keep the opportunity to reply to existing Bug Reports. Doing this will allow us to slowly fix any bug reports we have listed here so that we can easily migrate over to our Issue Tracker.

Update - June 7th 2015: Creating new bug posts has been disabled. Please use our https://github.com/HerculesWS/Hercules/issues tracker to post bugs. Users are still able to reply to existing bug posts.

- Administration

Issue Information

  • #008590

  • 0 - None Assigned

  • Fixed

Issue Confirmations

  • Yes (0)No (0)
Photo

Endless Tower possible bug

Posted by milk on 25 March 2015 - 01:54 PM

Characters, that already have cooldown for the Endless Tower can join the another character's (who haven't cooldown yet) party and enter the ET once again.


Exmaple:

Characters A and B in party Z generates the Dungeon and enters the Tower. They must have a 6 day 20 hour cooldown period to enter to the Tower again.

Character C (have no cooldown period yet) organizes the party Y and invites characters A and B to the party. Character C generates the Dungeon and enters the Tower, so characters A and B now are able to enter to the Endless Tower too.

It seems, script checks only party.

Sorry, I don't know the official behavior.

changed status to: Working as Intended

http://irowiki.org/wiki/Endless_Tower

There is no limit on how many instances a party can create within the 4 hour limit. A new instance can be created under a different party leader if the previous instance was destroyed. Once the time limit is up, there is a 6 day 20 hour cooldown period for all party members in which they cannot enter a new Endless Tower instance. However, additional instances will not allow access to additional MVPs.

we do this in iRO....

:meow:

http://irowiki.org/wiki/Endless_Tower



There is no limit on how many instances a party can create within the 4 hour limit. A new instance can be created under a different party leader if the previous instance was destroyed. Once the time limit is up, there is a 6 day 20 hour cooldown period for all party members in which they cannot enter a new Endless Tower instance. However, additional instances will not allow access to additional MVPs.

we do this in iRO....

:meow:


Even when 4 hour limit is ended?

Posted Image

Will work always if there is a weekly timer:
else if (.@etower_timer == 1) {
		mes "If you have the dungeon generated already, you can enter it. ";
		next;
		switch(select("Enter the "+.@md_name$+":Return to Alberta:Cancel")) {
		case 1:
			callsub L_Enter,0,0,.@md_name$,.@p_name$;
		case 2:
			mes "I will move you to Alberta.";
			close2;
			warp "alberta",223,36;
			end;
		case 3:
			break;
		}
		close;

Won't work since pevious if {}
else if (.@etower_timer == 1 && .@etower_timer2 == 2) {

		.@dun_lim_time = etower_timer+604800; // 1 week
		.@dun_lim_time2 = etower_timer+14400; // 4 hours
		.@dun_cur_time = gettimetick(2);
		.@dun_ent_t = (.@dun_lim_time - .@dun_cur_time);
		.@dun_h = (.@dun_ent_t / 3600);
		.@dun_m = (.@dun_ent_t - (.@dun_h * 3600)) / 60;
		.@dun_s = .@dun_ent_t - ((.@dun_h * 3600) + (.@dun_m * 60));

		mes "Due to the tower's aftereffects, you cannot enter the dungeon right now, " + .@dun_h + "hours " + .@dun_m + "minutes " + .@dun_s + "seconds left to enter the next dungeon.";
		next;
		mes "It is dangerous here. Let me move you to Alberta.";
		close2;
		warp "alberta",223,36;
		end;


Is it okay, or I am wrong?

Edited by milk, 25 March 2015 - 07:28 PM.


changed status to: Confirmed

yeah your right...the last check should come 2nd...
now all is clear....

:meow:

changed status to: Fixed

https://github.com/H...rcules/pull/476
Can you check it?

Thanks!

Fixed @ b92f634da7f7ad247d8e3f856d45225dad3c667c
:meow: