CDPR-Modding-Documentation / CDPR-Modding-Documentation/REDkit-bugtracker

CSV editor broken when copying and pasting text

Open
#10 0 comments 0 reactions 0 assignees View on GitHub
REDkit
Dominant language
No language data
Stars
7
Forks
1
PR merge metrics
No merged PRs in 30d

Description

**Describe the bug**
This is something ive noticed while trying to make weather edits. When editing a weather table with redkits csv editor if you copy and paste one cell to another in the csv (like adding a new cloud type or env), save, close and reopen the table, everything in the row after the cell that was pasted into gets put in a new row below.

**To Reproduce**
Steps to reproduce the behavior:
1. Open say weather_skellige.csv as an example or any other csv for that matter
2. Double click on a cell like for example the envs path for WT_Wild_Hunt quest weather
3. Right click and click copy
4. Paste it into another cell, as an example the empty env path for WT_Clear
5. File > Save
6. Close csv editor window
7. Reopen csv, sometimes a restart of redkit is required to see change or just open it in excel after saving in redkit.
8. Observe that everything to the right of envPath column in the WT_Clear row (EnvBlend, effect 1 etc) has been put in a new row below it.

**Expected behavior**
It should not shift all columns down 1 row after a pasting.

**Screenshots**
Before
![Image](https://github.com/user-attachments/assets/cb1416ab-fbbb-4378-99b2-5160ced38354)

Edit:
![Image](https://github.com/user-attachments/assets/83e42e00-1808-456a-ae49-4b0fd782bd30)

After:
![Image](https://github.com/user-attachments/assets/6a9480a0-8acb-4e42-b545-3456e58edf03)

Contributor guide

No contributing guide indexed for this repository

Research direction

Reproduce the issue in the CSV editor using weather_skellige.csv, following the copy-and-paste steps for the envPath cells in WT_Wild_Hunt and WT_Clear. Save, close, and reopen the table, or inspect the saved file in Excel, to confirm whether columns after the pasted cell move to a new row; done means the row remains intact after saving and reopening.

Written by the indexing model from the issue text.

Assessment

Domain
tooling
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Clearly specified
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.