[DiscordArchive] ?? what was the last change you made. I assume you didn't change _every_ DBC file without testing
[DiscordArchive] ?? what was the last change you made. I assume you didn't change _every_ DBC file without testing
Original source
?? what was the last change you made. I assume you didn't change _every_ DBC file without testing
rektbyfaith
05-04-2022, 03:24 PM #1Archived author: stoneharry • Posted: 2022-05-04T15:24:50.977000+00:00
Original source
?? what was the last change you made. I assume you didn't change _every_ DBC file without testing
Original source
nah...my friend did it since he wanted to be up to date coz we edit a lot and didn't want to ask me every time what did i edit....
rektbyfaith
05-04-2022, 03:25 PM #2Archived author: exanimis • Posted: 2022-05-04T15:25:46.454000+00:00
Original source
nah...my friend did it since he wanted to be up to date coz we edit a lot and didn't want to ask me every time what did i edit....
Original source
not sure if he gets one more error coz of that
rektbyfaith
05-04-2022, 03:26 PM #3Archived author: exanimis • Posted: 2022-05-04T15:26:01.257000+00:00
Original source
not sure if he gets one more error coz of that
Original source
Why not version control your edits
rektbyfaith
05-04-2022, 03:26 PM #4Archived author: stoneharry • Posted: 2022-05-04T15:26:03.842000+00:00
Original source
Why not version control your edits
Original source
or don't edit the same DBCs at all, store your data in SQL
rektbyfaith
05-04-2022, 03:26 PM #5Archived author: stoneharry • Posted: 2022-05-04T15:26:14.741000+00:00
Original source
or don't edit the same DBCs at all, store your data in SQL
Original source
i can always keep him up to date what is edited....not sure why he does that
rektbyfaith
05-04-2022, 03:28 PM #6Archived author: exanimis • Posted: 2022-05-04T15:28:30.398000+00:00
Original source
i can always keep him up to date what is edited....not sure why he does that
Original source
You have bigger problems than some corrupt data, you need to look at how you develop - how you share changes and how you document/version them. It will save you a lot of time in the long run.
rektbyfaith
05-04-2022, 03:29 PM #7Archived author: stoneharry • Posted: 2022-05-04T15:29:07.702000+00:00
Original source
You have bigger problems than some corrupt data, you need to look at how you develop - how you share changes and how you document/version them. It will save you a lot of time in the long run.
Original source
How I personally do it ATM, prob changing to version controlling later.
I assign each person a said ID range in DBC's they work on and merge em all in the end when they sent it to me (ofc have multiple backup version)
rektbyfaith
05-04-2022, 03:34 PM #8Archived author: Jyria • Posted: 2022-05-04T15:34:54.622000+00:00
Original source
How I personally do it ATM, prob changing to version controlling later.
I assign each person a said ID range in DBC's they work on and merge em all in the end when they sent it to me (ofc have multiple backup version)
Original source
ew, just use the same SQL server
rektbyfaith
05-04-2022, 03:35 PM #9Archived author: stoneharry • Posted: 2022-05-04T15:35:09.276000+00:00
Original source
ew, just use the same SQL server
Original source
we do not change same dbc at same time...
rektbyfaith
05-04-2022, 03:35 PM #10Archived author: exanimis • Posted: 2022-05-04T15:35:30.744000+00:00
Original source
we do not change same dbc at same time...
1 Guest(s)
1 Guest(s)