Tree of Savior Forum

About the easy-to-do changes that never come early to iTOS

Gameplay Feedback General Feedback
#1

I think it’s time to talk about the patching-behaviour of the people managing iTOS.

While it’s understandable that skill-behaviour changes are not coming early, I don’t see any reason why the following two change-categories don’t come faster to iTOS:

  1. item value changes.
    We all know that some items like the Yellow Papers we reduced in their pricing on KTOS several months ago. The Yellow Papers e.g. got their costs cut down by 450 silver to 50 silver.
    The change is an easy removal of a “0” in the shop script of the Taoist Master NPC.
    But it was never implemented in iTOS.

  2. skill value changes.
    Skill values that are a simple number change/exchange in the skill formula like e.g. changing the CD time of Merkabah from 45 to 35 seconds can be done by one person in 1-2 minutes by simply exchanging the “4” with a “3”. There is no need for scripting knowledge, even an elementary school kid could do this.

So why do these simple changes that take a few minutes at best only come to iTOS after several months of waiting time?
Since iTOS doesn’t follow the patch pattern of kTest or KTOS, there is no reason to hold back such fundamental game improvements.

Simple exchanging of ingame values doesn’t break the client, doesn’t change the behaviour/nature of skills and doesn’t create bugs. Those changes should have the utmost priority of implementation as they are easy,bug-free,efficient and showcase the customers that the managing team is at least working on something…

4 Likes
#2

So, you are working in the IMC development team? U make up times that you have no idea about. I think they might just have a messed up repository for the international version and thus they won’t just change stuff within a few minutes…

I know it’s annoying, but don’t make up times when you don’t know bout their environment…

#3

The reason we don’t get those changes fast is because IMC has never prioritized iToS over kToS. Changing talisman price should be very easy no matter how messy their repository is. People make addons out of zero-documented and messy client files, any experienced programmer should be able to find the npc script and change one digit in the price.

It’s a change that can be easily done in 5 minutes, or at most 30 minutes if the person has no clue how the files are organized. The problem here, as I stated before, is that IMC almost never manually changes important files in international repository and instead just merge the repositories every 2 months or so (this is when we get big patches with everything from kToS). This feels (to us, users) like a very sloppy job and also feels like there really isn’t anyone managing the international repository for important changes.

The reasonable explanation for that (as I believe) is that they do not have enough man power to manage both kToS and iToS servers. Developers focus on kToS repository and merge it with international one whenever they have “free time”.

Now as @BlaXun stated, this may be a much more in-depth problem than a simple change of a digit. The company may not have enough workforce to manage both servers and the true problem behind everything is just bad administration (i.e. not employing enough developers).

7 Likes
#4

I agree that it most likely is very easy to fix, but I also think they propably have a different plan for us that they want to stick to as much as possible… even though it might be very annoying for us.

#5

Dumbest way ever to update two repositories, wait months of patchs and changes, make bigger than your team can do, than after 100thousands of lines, you decide to merge, every developer knows this is dumb, there is no other excuses. Even if they don’t care about us, still dumb.
I was a whiteknight once, but i am tired of being stupid, defending stupid decisions make by them, and not responding us, instead of that, they keep quite, i do poor patchs, that does not make anyone happy.

3 Likes
#6

Ofc they could change small things to help us, but where to start and where to end? Randomly picking A and ignoring B?

IMC apparently wants to refrain from doing small changes in between making later bulk changes more complicated. After getting done what nexon wants from them, they may find time to give us a bulk update with every little shît included. Thats how the Administration works.

Nexon is the highly mighty customer paying licence fees to fill their pockets. Itos is just a side project with gambling. It’s nice to have when it works, but ain’t so bad when it fails either.

#7

I agree it’s ■■■■… no use sugarcoating it… but we still don’t know the reason

#8

Didnt they merge the repositories last year and theyre only using 1 now for ktos and itos?

#9

I think they just merge the updates on ktos with itos, otherwise, we will just have the last updates right now!

#10

Waiting QoL(like lower mats price or increasing buff duration) for 2 months is really annoying. They could atleast make this changes come to iToS faster…

#11

They surely don’t use the same update content, as we never got some of the balance changes like e.g. the Out of Body skills ASPD scaling with your ASPD/DEX.

Also, if they used the same updates for a base, we would have our bugs fixed faster as on KTOS, nasty bugs are basically fixed asap while they persist a long time on ITOS, some of them even being recurrent on ITOS only(e.g. the Pardoner shop buffs vanishing when changing maps/losing their effect).

It would be great if we’d just get the same updates as KTOS and just recieve the translations of content later on so that we’d not be so far apart and have less bugs.

After all, it’s not like having some Hangeul would give your eyes cataracts or some ingame descriptions lagging behind the changes could make the game worse than being buggy as hell.

1 Like
#12

Than its worse that i thought. They surely do ctrl+c ctrl+v literally. For God sake, why?

#13

They’ve ■■■■■■ up royally every time they tried to cherrypick small changes.
Now they only port big patches to completely synchronise ktos and itos.