https://manicpop.org/gewiki/index.php?action=history&feed=atom&title=Classic_bug%3A_TEAM_KICK_mail_classificationClassic bug: TEAM KICK mail classification - Revision history2026-10-20T16:29:21ZRevision history for this page on the wikiMediaWiki 1.46.2https://manicpop.org/gewiki/index.php?title=Classic_bug:_TEAM_KICK_mail_classification&diff=2201&oldid=prevCodexBot: Document inherited TEAM KICK mail-class bug and ge-next 0.3.3 fix2026-10-18T21:46:27Z<p>Document inherited TEAM KICK mail-class bug and ge-next 0.3.3 fix</p>
<p><b>New page</b></p><div>{{Classic bug<br />
|id=GE-BUG-059<br />
|affected=Classic 3.2e and ge-next through 0.3.2<br />
|status=Verified in source; corrected in ge-next 0.3.3<br />
|fixed=ge-next 0.3.3 (16-bit and 32-bit)<br />
|source=GECMDS.C: cmd_team(); GEFUNCS.C: sendit(), mailscan(), mailread()<br />
}}<br />
<br />
== Summary ==<br />
When <code>TEAM KICK</code> removes a member, it composes a ''Team Membership Revoked'' mail notice but does not set the notice's mail class. In classic GE and ge-next through 0.3.2, the notice inherits whatever class was last stored in the shared <code>mail</code> workspace. It may be filed under Distress messages, misfiled under Production reports, or left in a class that the in-game menu cannot open.<br />
<br />
== Symptoms and reproduction ==<br />
# Use the in-game GE mailbox, with an existing team and another player who can be removed from it.<br />
# Before any event has assigned a class to the shared <code>mail</code> workspace, use <code>TEAM KICK</code> to remove that player.<br />
# The removed player's main menu can indicate that a message is waiting, while the mail menu shows neither Distress messages nor Production reports as available.<br />
<br />
The initial global <code>mail</code> workspace has class zero. If an earlier event set it to class 1, the notice appears under Distress messages. If a production report or stock-cap notice left it at class 3, the team notice appears under Production reports. The behavior therefore depends on previous activity during that module run, not on the team action itself. It does not mean the kick or the team's saved membership failed.<br />
<br />
Classic 3.2e also has a <code>USEGEMSG</code> option. When mail is routed to the host BBS mailbox instead of GE's own mailbox, this particular two-category menu problem does not apply. The distributed classic configuration enables GE mail. ge-next uses only GE mail, so both its 16-bit and 32-bit standard-game builds inherited the problem. ge-arena disables persistent <code>TEAM</code> and is unaffected.<br />
<br />
== Cause ==<br />
<code>cmd_team()</code> sets <code>mail.userid</code> and <code>mail.topic</code>, then calls <code>sendit()</code> without assigning <code>mail.class</code> (classic) or <code>mail.mailclass</code> (ge-next). <code>sendit()</code> copies that field to the stored message's flags. The GE mail menu searches only class 1 for Distress messages and class 3 for Production reports. Its initial any-mail check searches by recipient alone, so a class-zero notice can make the main menu show mail waiting without providing a readable category.<br />
<br />
== Correction in ge-next 0.3.3 ==<br />
The 16-bit and 32-bit ge-next <code>TEAM KICK</code> paths now set <code>mail.mailclass = MAIL_CLASS_DISTRESS</code> immediately before <code>sendit()</code>. A newly generated revocation notice is thus placed in the Distress messages category regardless of what previously used the workspace. This is a classification fix; it does not change team membership or rewrite mail records already stored with an incorrect class.<br />
<br />
== See also ==<br />
* [[Mail]]<br />
* [[Team command]]<br />
* [[Teams]]<br />
* [[Classic bug: Team state inconsistency]]<br />
<br />
[[Category:Classic bugs: Multiplayer state]]<br />
[[Category:Classic bugs: User interface]]<br />
<br />
{{GE navigation}}</div>CodexBot