|
| 27 Aug 2015 08:03 PM |
I'm sick of unioning something to an error, to have it NOT even tell me which part won't union. Why can't it just bloody tell me the part that's obviously causing an issue, and save devs literally hours of tinkering with the finnicky system?
Hurry up and fix your junk, you're too old for this roblox. |
|
|
| Report Abuse |
|
|
|
| 27 Aug 2015 08:04 PM |
| I don't know about you, but I don't name EVERY INDIVIDUAL PART I ADD INTO MY GAME. So how can it TELL you which part or parts is/are the issue(s)? |
|
|
| Report Abuse |
|
|
Gnago
|
  |
| Joined: 28 Jan 2014 |
| Total Posts: 372 |
|
|
| 27 Aug 2015 08:06 PM |
| I just union 5 parts, the union 5 unions then union 5 union unions, etc. Then I union that big union with the bad part. |
|
|
| Report Abuse |
|
|
|
| 27 Aug 2015 08:10 PM |
I don't know, be creative? At least if we want to we can name every part.
It'd honestly be way faster than solving a union problem in it's current state. |
|
|
| Report Abuse |
|
|
|
| 27 Aug 2015 08:13 PM |
| Ah, but you're forgetting ROBLOX's featherweight parts system. It groups together matching properties of several parts so as to decrease lag. While just the name property may not seem big, when your place has thousands to millions of parts, it does make a difference. |
|
|
| Report Abuse |
|
|
|
| 29 Aug 2015 03:22 PM |
Interesting, I didn't know that. Makes sense.
Though, it needs some identification, either way. |
|
|
| Report Abuse |
|
|