Page 1 of 1
Don't settle for only 1 RvR
Posted: Fri Sep 08, 2017 12:56 pm
by Nidwin
I know this is kind of a bitch devl wise for source code management but try different RvR "types" and when one seems to be fine, saved it (the code) so once out of alpha, beta you can have some kind of rotation, regular change of RvR types out there in the lakes.
Re: Don't settle for only 1 RvR
Posted: Fri Sep 08, 2017 2:16 pm
by Haojin
Wat
Re: Don't settle for only 1 RvR
Posted: Fri Sep 08, 2017 2:43 pm
by Sulorie
Google translator told me he wants to keep different "working" rvr systems and alternate them at later time to keep the game play fresh and interesting.
As getting a working and robust rvr system itself is a process I doubt anyone will go back to a less developed rvr system.
Re: Don't settle for only 1 RvR
Posted: Fri Sep 08, 2017 3:57 pm
by Luuca
Don't get Zaxxed and post.
Re: Don't settle for only 1 RvR
Posted: Sat Sep 09, 2017 1:19 am
by Tesq
Well kinda in line with tabletop spirit, per se short period of test can be used to find by try and errors the best avaiable system.
Codingwise is a doom
Re: Don't settle for only 1 RvR
Posted: Sat Sep 09, 2017 9:28 am
by Natherul
just no, simply (apart from the migraine inducing code management) it would make its super annoying for a player to get whats going on, its not player friendly.
locking