cmss13-devs / cmss13-devs/cmss13

Tacmap lacks full multiz support

Open
#11,184 0 comments 0 reactions 0 assignees View on GitHub
Bug Confirmed Bug
Dominant language
DM
Stars
170
Forks
940
Avg merge
5d 16h
Merged PRs (30d)
61

Description

### Testmerges

10611

### Round ID

N/A

### Description of the bug

- Only current Z view is submitted to marines despite there being icons & drawings on other Zs
- Admin tacmap panel only displays the Z viewed when submitting the tacmap
- Tacmap viewers only display the viewed Z when the tacmap was submitted

For example drawing 1, 2, and 3 on each Z but looking at this Z when submitting it, then taking a marine to that Z they see this (correct):
Image
That Z as a ghost (so live - correct):
Image
But then we go up a Z. Marine sees this (incorrect):
Image
Ghost sees this (correct):
Image
Command tacmap sees this (correct):
Image

### What's the difference with what should have happened?

- All Zs should be submitted
- Admin tacmap panel should show all Zs or a way to change Z
- Tacmap viewer should show all Zs or a way to change Z

### How do we reproduce this bug?

1. Boot game with a multi-z map e.g. White Antre Research Facility
2. Optionally change to distress signal
3. Draw on tacmap on different Zs
4. Submit (only currently viewed Z will be submitted)
5. View as marine on that Z vs other vs as a ghost

### Issue Bingo

- [x] Issue could be reproduced at least once
- [x] Issue happened in a recent (less than 7 days ago) round
- [x] Couldn't find an existing issue about this (https://github.com/cmss13-devs/cmss13/issues)

Contributor guide

Open the contributing guide

Research direction

Reproduce the issue on the White Antre Research Facility map by drawing on multiple Z levels and submitting the tacmap. Trace the tacmap submission, admin panel, and viewer entry points to determine where the current Z is selected. Done means all Z levels are submitted and can be viewed by marines, admins, and ghosts, with the stated reproduction steps passing.

Written by the indexing model from the issue text.

Assessment

Domain
game-dev
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.