[Instance] Raid Tab and Join Msg Not Showing Reset time.

[Auntie Mangos]

to settti i run this from this threat http://getmangos.eu/community/viewtopic.php?id=14700&p=120911&viewfull=1#post120911, seems to work fine, but im not sure at all, im having the issues that i post above.

you shouldn't test with a new instance like FoS, but rather with one of the older, my tests were everything ok (raids and heroic-dungeons), I tested with Naxx, UtgardeKeep, Sethek Halls, and also the initial resetTime for FoS was correct (though it didn't bind..) - tested with UDB392

tested atm in UK, got the TTR time same as the FoS time, the ttr of the fos was 13h-6n-48s, and the uk got the same, maybe when the ttr reach 24 reset?? if this is the case still wrong caus like i said my instanceresettime is at 4am and when ttr reach 24h will be the 1am here that is the time of the server.

btw i think you have the defaul resetinstancetime right? that is 4am, at what time you got save and what time you will get the reset of the heroic? maybe can you post some pics, or help to get a solution without droping the characters?

also the same errors that i said about the raid tab and welcome msg still.

[Auntie Mangos]

with clean characters database and mangos 10426, sd2 1815 i have no problems with instances reset, tested with ulduar normal and ulduar halls of lightning heroic.

tested with naxxramas, icc - works normal.

Could you recheck this, if your server is up more than, let's say, 6-7 days straight?

I once made a long thread(lost ) with not unbinding of heroic instances + raids after long uptime.

Problem was confirmed by many.

It also gave duplicate slq-entries and the instance reset time ingame shown was '" . " too.

Revision then was 8104 and up.

Clearing the mentioned tables did indeed fix the problem, but only shortly: after long uptime, problems returned.

Servers that have less uptime won't notice it quickly since restart server always does a "Cleaning up instances...".

Pitty i can't link the thread anymore and have no idea if this is in any way related, but it shure looks a lot like the same problem.

See aswell:

http://getmangos.eu/community/viewtopic.php?id=10241&pagenumber= (point 2)

http://getmangos.eu/community/viewtopic.php?id=12727&page=1

http://getmangos.eu/community/viewtopic.php?id=14700&pagenumber=

[Auntie Mangos]

Could you recheck this, if your server is up more than, let's say, 6-7 days straight?

I once made a long thread(lost ) with not unbinding of heroic instances + raids after long uptime.

Problem was confirmed by many.

It also gave duplicate slq-entries and the instance reset time ingame shown was '" . " too.

Revision then was 8104 and up.

Clearing the mentioned tables did indeed fix the problem, but only shortly: after long uptime, problems returned.

Servers that have less uptime won't notice it quickly since restart server always does a "Cleaning up instances...".

Pitty i can't link the thread anymore and have no idea if this is in any way related, but it shure looks a lot like the same problem.

See aswell:

http://getmangos.eu/community/viewtopic.php?id=10241&pagenumber= (point 2)

http://getmangos.eu/community/viewtopic.php?id=12727&page=1

http://getmangos.eu/community/viewtopic.php?id=14700&pagenumber=

ok no matter what i do, latter that the TTR ends and instance reset correctly the TTR becomes crazy.

just with enter in the instance, I GOT SAVED, making .instance listbinds it appear that i got saved just with enter in the instance ( BUT in the raid tab doesnt appear anything ), and the ttr keep decreasing in negative value.

THE ONLY WAY is restarting the server, and get fixed ( not at all ) like i said b4, the TTR is like default, reset occurs at 23:30m not taking the time of the mangos.conf where said default should be 4am.

i take from character.sql from the folder of mangos sql this part of the sql to clear again the tables and be sure that its all correct. and well the report its the same im saying in this reply

-- Table structure for table `character_instance`
--

DROP TABLE IF EXISTS `character_instance`;
CREATE TABLE `character_instance` (
 `guid` int(11) unsigned NOT NULL default '0',
 `instance` int(11) unsigned NOT NULL default '0',
 `permanent` tinyint(1) unsigned NOT NULL default '0',
 PRIMARY KEY  (`guid`,`instance`),
 KEY `instance` (`instance`)
) ENGINE=InnoDB DEFAULT CHARSET=utf8;

--
-- Dumping data for table `character_instance`
--

LOCK TABLES `character_instance` WRITE;
/*!40000 ALTER TABLE `character_instance` DISABLE KEYS */;
/*!40000 ALTER TABLE `character_instance` ENABLE KEYS */;
UNLOCK TABLES;


-- Table structure for table `groups`
--

DROP TABLE IF EXISTS `groups`;
CREATE TABLE `groups` (
 `groupId` int(11) unsigned NOT NULL,
 `leaderGuid` int(11) unsigned NOT NULL,
 `mainTank` int(11) unsigned NOT NULL,
 `mainAssistant` int(11) unsigned NOT NULL,
 `lootMethod` tinyint(4) unsigned NOT NULL,
 `looterGuid` int(11) unsigned NOT NULL,
 `lootThreshold` tinyint(4) unsigned NOT NULL,
 `icon1` int(11) unsigned NOT NULL,
 `icon2` int(11) unsigned NOT NULL,
 `icon3` int(11) unsigned NOT NULL,
 `icon4` int(11) unsigned NOT NULL,
 `icon5` int(11) unsigned NOT NULL,
 `icon6` int(11) unsigned NOT NULL,
 `icon7` int(11) unsigned NOT NULL,
 `icon8` int(11) unsigned NOT NULL,
 `groupType` tinyint(1) unsigned NOT NULL,
 `difficulty` tinyint(3) unsigned NOT NULL default '0',
 `raiddifficulty` int(11) UNSIGNED NOT NULL default '0',
 PRIMARY KEY  (`groupId`),
 UNIQUE KEY  (`leaderGuid`)
) ENGINE=InnoDB DEFAULT CHARSET=utf8 ROW_FORMAT=FIXED COMMENT='Groups';

--
-- Dumping data for table `groups`
--

LOCK TABLES `groups` WRITE;
/*!40000 ALTER TABLE `groups` DISABLE KEYS */;
/*!40000 ALTER TABLE `groups` ENABLE KEYS */;
UNLOCK TABLES;

-- ----------------------------
-- Table structure for group_instance
-- ----------------------------
DROP TABLE IF EXISTS `group_instance`;
CREATE TABLE `group_instance` (
 `leaderGuid` int(11) unsigned NOT NULL default '0',
 `instance` int(11) unsigned NOT NULL default '0',
 `permanent` tinyint(1) unsigned NOT NULL default '0',
 PRIMARY KEY  (`leaderGuid`,`instance`),
 KEY `instance` (`instance`)
) ENGINE=InnoDB DEFAULT CHARSET=utf8;

--
-- Dumping data for table `group_instance`
--

LOCK TABLES `group_instance` WRITE;
/*!40000 ALTER TABLE `group_instance` DISABLE KEYS */;
/*!40000 ALTER TABLE `group_instance` ENABLE KEYS */;
UNLOCK TABLES;

--
-- Table structure for table `group_member`
--

DROP TABLE IF EXISTS `group_member`;
CREATE TABLE `group_member` (
 `groupId` int(11) unsigned NOT NULL,
 `memberGuid` int(11) unsigned NOT NULL,
 `assistant` tinyint(1) unsigned NOT NULL,
 `subgroup` smallint(6) unsigned NOT NULL,
 PRIMARY KEY  (`groupId`,`memberGuid`),
 INDEX `Idx_memberGuid`(`memberGuid`)
) ENGINE=InnoDB DEFAULT CHARSET=utf8 ROW_FORMAT=FIXED COMMENT='Groups';

--
-- Dumping data for table `group_member`
--

LOCK TABLES `group_member` WRITE;
/*!40000 ALTER TABLE `group_member` DISABLE KEYS */;
/*!40000 ALTER TABLE `group_member` ENABLE KEYS */;
UNLOCK TABLES;

--
-- Table structure for table `instance`
--

DROP TABLE IF EXISTS `instance`;
CREATE TABLE `instance` (
 `id` int(11) unsigned NOT NULL default '0',
 `map` int(11) unsigned NOT NULL default '0',
 `resettime` bigint(40) NOT NULL default '0',
 `difficulty` tinyint(1) unsigned NOT NULL default '0',
 `data` longtext,
 PRIMARY KEY  (`id`),
 KEY `map` (`map`),
 KEY `resettime` (`resettime`)
) ENGINE=InnoDB DEFAULT CHARSET=utf8;

--
-- Dumping data for table `instance`
--

LOCK TABLES `instance` WRITE;
/*!40000 ALTER TABLE `instance` DISABLE KEYS */;
/*!40000 ALTER TABLE `instance` ENABLE KEYS */;
UNLOCK TABLES;

-- ----------------------------
-- Table structure for instance_reset
-- ----------------------------
DROP TABLE IF EXISTS `instance_reset`;
CREATE TABLE `instance_reset` (
 `mapid` int(11) unsigned NOT NULL default '0',
 `difficulty` tinyint(1) unsigned NOT NULL default '0',
 `resettime` bigint(40) NOT NULL default '0',
 PRIMARY KEY  (`mapid`,`difficulty`)
) ENGINE=InnoDB DEFAULT CHARSET=utf8;

--
-- Dumping data for table `instance_reset`
--

LOCK TABLES `instance_reset` WRITE;
/*!40000 ALTER TABLE `instance_reset` DISABLE KEYS */;
/*!40000 ALTER TABLE `instance_reset` ENABLE KEYS */;
UNLOCK TABLES;

o btw forgot to mention something. the Reset instance buttom when you right click on your character seems to not working, i push it, and nothing happend, but if i change from 5H to 5N it reset the instance.

[Mylifesuxito]

well i post this in another threat where the main problem seem to be solved so i decide to make a new one threat with other bug.

test again with cleaned source and cleaned DB - no problem for me with 10406 and UDB 392

i clear some tables of the characters about the instances and now seems to be working fine. But still exist this problem.

1) when you enter in a instance the text msg " Welcome To ( Instance Name)(5 Player Heroic). Instance Lock are Sheduled to expire in. ( Here Should Appear the time left for reset) "

1.a) The time is set at mangos.conf the hour for the instance reset. i have it at 4am so if the current time is 11pm. should say " Expire in. 5 Hours".

2) At raid Info Tab the time for expired time doesnt appear now, not sure if here should appear the time that we set in mangos.conf like a said if i set it to 4am maybe should appear Expired time 4am or like before the time left for reset. will confirm this latter.

some pics:

Schomoozerd --> That problem or bug you have it too?? or it works for you??

--

i have another question i just kill a boss in FoS i use the commands .instance listbinds the first TimeToReset (TTR) Was:

*1h-13m-47s

i used a second time and now the TTR was

*1h-14m-11s

third time was

*1h-14m-27s

so my question is why the TTR time Increase? im not sure but it should be something like if at mangosd.conf the Instance.ResetTimeHour is set at 4am and i got saved at 12:40 the TTR should be 3h-20m-xxs ??.

i thought also that the TTR was like a clock i mean taking the time of the server and when it reach the Instance.ResetTimeHour will reset, but atm it show me TTR: 1h-29m-27s but the time of the server is 1pm, so really dont know.

or how TTR works??

Btw i test this with Heroic instance only not raid.

[ascent]

I think your screen shot is delete;..

[Mylifesuxito]

i click on the screens and their fine o.0

[settti]

I have the same problem. Can I ask which tables you cleaned? Heroic ID reset is not working for me.

[Schmoozerd]

you shouldn't test with a new instance like FoS, but rather with one of the older, my tests were everything ok (raids and heroic-dungeons), I tested with Naxx, UtgardeKeep, Sethek Halls, and also the initial resetTime for FoS was correct (though it didn't bind..) - tested with UDB392

[Mylifesuxito]

my apologies for bumping this.

Schmoozerd> your right. i test with the same core but just with a clear character db and its fine the welcome msg and raid tab appear the time BUT, its not totally fine caus i join and said 23hours left for the ttr and its 12am so if in my instanceresettime at mangos.cfg i have at 4am should said 4h left. maybe that part of the config not working.

Note 1: now the problem i have is how i clear my old characters db without losing characters or an idea of what could be wrong in the character db to keep this bug any idea help could be really appreciaty.

Note 2: in the clean character db the TTR is decreasing that is find, but in the old character db is increasing like i post above.

*Clear character DB TTR at start was: 23hxxM dont remember the M ATM TTR is on: 22h30M

*Normal Character DB: TTR Start Was: 1h-13m-47s -- ATM is on: TTR: -1d-1h-33m-58s --> exactly as appear in the screen to me.

i test with the same core that have the armory patch of shadez, and works fine this mean that the patch is not causing the trouble, its something in the character db.

[Schmoozerd]

if you only truncate the instance_reset and character_instance table the worst thing happening is that players may kill a boss more often then they should, so this is should be a good start to get the mess out of the system

[Mylifesuxito]

if you only truncate the instance_reset and character_instance table the worst thing happening is that players may kill a boss more often then they should, so this is should be a good start to get the mess out of the system

srry schmooz didnt understand u very well . but i clean or truncate the following tables.

*Character_instance

*Group_instance

*Group_member

*Group

*Instance

*Instance_reset

Now the time appear fine with only 1 error, i got added to ttr like 30 min more or 20min when i start the server i join it, go in to FoS and said Welcome To ( Instance Name)(5 Player Heroic). Instance Lock are Sheduled to expire in 1d 17minutes, i test and test and the time is decreasing so thats good.

then i go to a raid instance and get the same msg with time 7days 15 min so hope you get my point, maybe with some time it get fixed alone?

[Mylifesuxito]

one more time im bumping this srry one more time got an issues. latter of truncate the tables above, i got like i said the timers fine in the msg now at this exactly moment, when the ttr comes to the end and the instances has been reset.

its bugged again the time is not appearing in the welcome msg and also at the raid tab , so wth o.0. could be wrong .

but looks this 2 pictures, really interesting.

*

see the TTR time from the raid and the Heroic instance -- as you can see the ttr time of the raid instance is positive and the heroic instance is negative

second image

*

seet once more time the TTR time from both, the raid time is decreasing normally and the once from the Heroic is decreasing but in negative value.

its like latter of the reset the db get corrupted or something. caus i go to a raid instance and the time its appearing at the welcome msg but for the rest of heroics its bugged. im pretty sure that the timer for the raid instance will get corrupted too when the TTR comes to the end.

any ideas? need more info? im trying to give all i have to get this fixed T_T

UPDATE 4: i just got a feeling that if i restart the server could be a solution due some strange class of unsucess update of the tables. and i was right, i just restart the server and now the timer for the instance H appear fine, also in the once that i got saved.

so i can maybe say that something is wrong updating the tables?? when the ttr times come?.

btw, i check the resettime in instance_reset just after the ttr go to the end and get bugged the welcome msg and raid tab ttr, resettime of the map 619 where i got saved once again to test, was ( 1283227200 ) latter of restart the server, the time was the same, but the welcome msgs and raid tab like i said was fixed get the correct ttr.

i convert the unix time ( 1283227200 ) and its correct it should reset Tue, 31 Aug 2010 04:00:00 GMT thats what is set it in the conf, but its like right now the ttr its managed in other way. if the resettime show the correct time when the instance should be reset why, the reset of the instance H its done at 11:25pm or 23:25 GMT?¿.

but most important why latter of finished the ttr get bugged the time, and need to restart the server to fix them?

here the image latter of the server restart. you can see that the time appear normally now . something is not refreshing the things good?

[The_Game_Master]

Just a quick question, should instances have individual (raids/dungeons) reset time anyway?

[Electros]

with clean characters database and mangos 10426, sd2 1815 i have no problems with instances reset, tested with ulduar normal and ulduar halls of lightning heroic.

tested with naxxramas, icc - works normal.

[Mylifesuxito]

Just a quick question, should instances have individual (raids/dungeons) reset time anyway?

no the thing that the H insance have the same ttr its fine, but my problema if what u can see in the image i truncate the tables aboves, the first ttr finish up, and now the ttr for h instance start to decreasing in negative value.

i shutdown the server start it again and the ttr was fixed .

For Electros:

with the clear db, if at your mangos.conf have the default instancereset at 4am, their are reseting at that time? also your raids? the default day to reset i wenesdsday or tuesday dont remember

[Darky88]

Same error since [10549], ¿Some fix or idea?

Att Darky