-
Posts
4,918 -
Joined
-
Last visited
-
Days Won
686
Content Type
Profiles
Wiki
Issue Tracker
Forums
Cash Shop
Gallery
Everything posted by Ueda
-
Connection Status text now shown during login on the client To inform players what's going on in the background while they login. No more Authentication Server Removed the need for central authentication server application by using modern database, cloud-based replacement. This also means the issue where the server would not "come back online" after automated scheduled maintenances is fixed. Cloud-based Saves Rewrote saving of player data from saving to local JSON files to saving into cloud database. Upgraded server to .NET 5, stripped down to lightweight console application Faster generally, cross-platform server application. Server ported to a Console Application. Replaced ZLib with LZMA A Modern, faster compression library, with better compatibility. ZLib was causing some players to be unable to run the new client. New oAuth Login System (Social Logins!) Rewritten login system to login through OAuth 2.0 standard which allows players to authenticate directly through the forum. This also means social logins is working again after all this time. Not just the existing methods of social logins, but we can basically add any service that has oAuth as an authentication method for Nin Online! Map Instancing We now have the in-engine functionality to create instanced maps. This for the time being will just used for Player Housing. Player Housing Player Housing is now implemented into the Engine, however there are currently no purchasable houses in the world, we'll add them as soon as we ensure the server is stable. Furniture System aka Placeable Objects Placeable Objects, there are now items that can be placed into the world (not just houses) like a Chair, or Table. Corporation aka. Corps System This is the successor to Official Organizations. Player Organizations will be a completely separate, new system in the future. Corporations is a fully in-game replacement of player organizations. Kages can now manage the corps in their village, and assign leaders there. Leaders can manage members. Each corporation can have a unique set of roles/titles. Each corporation can have a time limit for how long a member can stay in it, and a cooldown for how long before you can rejoin it. This takes effect whether you were kicked or time runs out to prevent abuse. The in-game UI for Corps is currently using a temporary UI that only works when running in windowed mode. New Player Reporting System The previous report system was essentially useless. You can now Right-click -> Report a player to open a game window that asks you what the player is doing wrong. This will immediately alert any GMs online about it, and save the report to our cloud server, where can handle data better than ever before. Profanity Chat Filter In an effort to encourage better player communication, we've added a system that replaces words like the N word to a cleaner alternative. Added 144 FPS cap on the client This was missing in the previous versions of the Inochi client. Stat Reset at Level 10 This is now a permanent, automatic feature because I don't want people feeling that they didn't add the right stats at level 10 and need to buy a stat reset or create a new character. It's too early to take a player's money, and they didn't know any better. So at level 10, your stats automatically reset, no item required. Forum upgraded The forum just underwent a major upgrade after quite some years. It should contain a lot of cool new features coming soon! Client now prioritizes 64-bit processing mode. Replaced client fonts. Improved Map Loading times by improving process and using better compression method. Rewrote how Packets are handled on the server, Improving latency by up to 20ms Fixed jerky movement present on the Inochi client by rewriting movement client-side to use Linear Interpolation and time instead of pixel-by-pixel movement. Fixed Blurry Textures after Zooming Bug Possibly fixed the Client bug known as "After Images" Fixed a bug where typing in some UI would trigger HUD and interact with the game. Map Transitions are now Time Based instead of FPS based and should be consistently fast on lower FPS capped clients. Fixed some issues causing the new client to not work on some computers, related to outdated libraries and rare crashes, based on player crash reports. Fixed client grabbing your wrong IPv4 for localhost testing. Fixed some visual flaws in Character Creation with the Mist Village button (No animations). Improved Combat Text to move at a consistent speed on all FPS. Client now Times out during Server Selection if it fails to login after 30 seconds Fixed a bug where Jutsu with cooldowns less then 1 second wouldn't be correctly processed Fix to Slow Cast Jutsu making walking move players backwards Fixed an exploitable bug where two trades could be opened at once Fixed a lot of issues where the Client would disconnect from the server unexpectedly. Rewrote game's time calculations, which Improves Server Responsiveness for attacks and Jutsu. Optimized, refactored login processing to speed up logins dramatically. Halved the server startup times by threading loading of data, allowing for faster server scheduled maintenances restarts. Powerful server Job System, allowing for tasks to be multi-threaded, put simply, This improves server performance. Improved the new UI System (Currently used for options menu, housing menu) rendering performance. Fixed an issue with resizing your client making the cursor invisible on the title bar of the game. Game Masters & Developer Related Changes Players can now be muted for longer than 255 hours Fixed some of our Live Editors crashing the game on the new client /heal can now be used by Game Masters, allowing them to remove Battle Injuries from players Clone/Paste functionality has returned to our Live Editors. Fixed many Event Management commands not working as intended Added /faint to force yourself to faint PatchnoteFeaturesHeader.png.cb804e75c3da7a4e81a4bcaf546ecd6d.png.1477a5ae2419bed77fe06f7c7eeba9de.png.url
- 788 replies
-
- 23
-
-
-
We'll take this into consideration.
-
Is this outdated? If rogues can't finish the quests, it's a bug https://github.com/HitsparkInteractive/NinOnline/issues
-
Thanks for the suggestion. We have a system planned to allow players to easily swap between titles they've unlocked.
- 1 reply
-
- 1
-
-
Fixed issue where "Mission! What's that!?" Mission would not complete if you talked to Tengu if you were a Leaf Missing Ninja
-
Are you using the new or old client? If new client, are you using the Legacy Map Rendering option? If old client, I think it's to do with Forced Anti-aliasing on your NVIDIA control panel.
-
Added Koji mini-boss to "Chilling Corridor" map. Added White Bandit Mask drop to Koji. Added Black Bandit Mask drop to Koji. Fixed visual bug on "Entrance to Takumi Village" map. Made Blue Short Jacket available to be used by Male ninja.
-
It's not perfect, there's jaggies because the female shoulder is thinner, but if players don't mind it we can allow it for now and maybe do a male version when we have more time in the future.
-
The only reason it hasn't been available is because when we added the art there wasn't a male version for it done. If it really fits fine without any modifications we can just enable it. But I don't... think it does? If it needs modification, we can do it, but it's not really something we should be focusing on atm, but I can take a look and see how hard it is to modify it (if required at all) in a minute.
-
Nobody has "created" Jutsu for their clans because making jutsu is a lot more work than making idea posts... As much as I want to just take everything as people want and implement it as well, a lot of suggestions people make tend to be unusable for one reason or another. We also have had most of the jutsu for each Clan planned for at least a year now. But we've not had the manpower required to work on it because we've been working on major architectural changes to the engine. A lot of which was done with the intention to make adding on top of the engine easier so we can sustainably add more features. When it comes to Clan clothes, I've explained in this dev log post why we haven't been pushing any graphical updates.
-
The current "Chidori" jutsu isn't actually chidori. It's based on this https://naruto.fandom.com/wiki/Lightning_Cutter The final form of Chidori will be much different.
-
Dear Ninja, The next update for Nin Online has been awhile coming now, and we're also not sure when we'll be able to get it ready to launch. We're working almost every day of the week to try to make sure the update is the best it can be. But in the end, it's only really going to disappoint a large number of people because just by launching it because it's not like straight out content updates, we've been working on underlying systems a lot to get the game fully modernized. We put time into the wrong things In hindsight, a lot of what we've been working on is less important than it seemed. Like we re-programmed the entire game's saving to be Object-Oriented, in a production-level cloud database, MongoDB Atlas, but in the end, it's still going to be entirely the same for the end user. So it's a shame, it's something I believed was going to be a seamless transition, but took weeks out of our time to resolve all the problems, and we might still be having some. And again, in hindsight, this should've taken a backseat to working on things people care about or would directly affected their gameplay. Cloud saving is nice to have, and it brings about opportunity for stuff like a Web frontend for Nin, like imagine being able to display your characters on the forum, or edit their name from the web, manage your items etc. We rewrote the login system to use oAuth, a clean login standard that means no more entering your password every time you want to login too. It also simplifies our server's job of checking MySQL tables to check if a player is banned because oAuth handles all that on the client and web side. Logins should also just be faster in general now, as we've rewrote a lot of the underlying login code as well. We updated the server to work with .NET 5 instead of .NET Framework. It's basically Microsoft's latest development framework. Which sounds like a small change, but .NET Framework is ancient technology at this point. .NET 5 allows us to modernize the server even further and export it as a containerized server for hosting services like Heroku. This also means that the server is now a console application, and cross-platform (we can host it on Linux servers which are cheaper because Linux is free and Windows Servers need licenses, Linux servers are also more easily available). Along with this, we also halved the server loading/launching time. So less down time between server restarts. Wolf rewrote the packet handler thread in this update, it should shave off about 20ms off larger packets. We updated our networking library to use it's latest version, this was an attempt to fix some low-level bugs with disconnection we were having. We replaced the compression library from Zlib to LZMA, which fixes a lot of compatibility issues players were having with the new client and potential crashes. We also managed to get map packets and map loading down a lot with better compression along with reducing the amount of packets needed to be sent on login by almost 10 fold. So faster logins, better map loading times. But in order to do this, it meant we had to deprecate the old client. It's a weird situation. In order to deprecate the old client we needed to make this change, but Zlib was also making it so some people couldn't move to the new client. We have the player housing update, furniture update and corps update in this too one patch too. We also used MongoDB to replace an entire component of our server architecture, our authentication. It's now an entirely passive web-based solution. Servers register to an online database instead of sending that data to the authentication server to do the central server selection stuff. As such, we also had to make it so the server does the saving directly to the cloud instead of the authentication server. So a lot of these things were interconnected, and had to be all done at once. This directly caused us to stack update after update into one patch, and it became harder and harder to push one patch without issues. With all the major architectural changes and low-level code rewrites, a lot of things broke. Because of the nature of the changes we were making, we also couldn't make them independently of each other, so it had to be one big update or nothing. There's also a hundred other things I've left out, including reworking movement on the client side to animate smoother. These things don't make the patch any more complicated, so it's not worth mentioning. Hectic month of testing with BR Server We started testing the latest patch around a month ago on the Brazil Server now. During that time, we've fixed issue after issue, and some of the "fixes" were also entire rewrites, which caused more issues. It's been stressful, we've had days spent just fixing login issues, and days spent just fixing saving. We've had data corruption issues, where players accounts and all their data become too messed up to fix, and we've had to do hacky fixes for them like restore partially their data from old backups. We've had a period where the same player couldn't login for a span of days, and we realized the server wasn't disconnecting players properly. Stressful stuff. We've had issues where resetting characters wasn't working and worst yet, it created a duping exploit. We've had more of these issues in a span of a month, than we've had over the last 3 years of development. We pushed two new major features, one is currently being used actively, and that also came with it's own issues, but was a lot easier to fix than the issues that came from major architectural changes. Though some have been incidental to them. We've had issues where players were logging in as other players when they tried to login at the same time. We've had players spamming us telling us we're idiots and we should just put back the old client, we've had players spamming us telling us to revert to the old server, to stop using them as a test server, all while our full-time job had become fixing issues for a month. It's been stressful, for both me and Wolf. Side note: Whenever Brazil players complain about the issues happening, we sympathize with them, but we also think about how up until now, they've only been getting updates that have been screened and tested by the NA/Global server (you guys) and so they're fortunate to not have been the guinea pigs up until now haha Irreversible Update The worst part in all this was the difficulty in which the reversal of this update would've been. In order to update Brazil server, we needed to move all of the existing data into the cloud into a slightly different format. Which meant if we want to reverse the update, we would need to build a software to convert the data back into our old format as local JSON files or rolling back players a month. So it's been a go hard or go home month. There were times where I'm so tired I wanted to reverse the entire update and call it quits (this also happened just yesterday) but I had to force myself to look through code and fix it instead, despite being so sick of it. This is going to be even more so irreversible for the main server, because in order to update the next patch, we have to update the forum software, and that's one-way. So we're going to have to be even more careful with this server, which is why we're taking our time and making sure everything is good to go. The worst part I'm also stressing out about how this update won't bring enough content to make players happy, or bring gameplay value to people. It's very painful, knowing this, because we've been working so hard on this, but I know in the end, this is more for the sake of the game in the long term, and also some of it is just wasted effort. Most people won't care that the game server runs slightly smoother and that login is faster, more convenient etc. Nobody is going to care that player data is now stored in a cloud database. This update has been months of work now, but I'm just waiting for the criticism on how it's a shit update etc. It's going to happen, and I'll understand why, but it'll still be hurtful. This update when it takes into account how much work has gone into it by two of us, thousands of hours of work, which means tens of thousands of dollars worth of work. It's not funny for me, it's very painful. And I agree with players, is it really necessary? We could've done without. I could've just not have a full-time programmer, and I could've just focused my time on working on stuff people care about like adding more Jutsu. This has been the hardest months of development since maybe 2017 when the server was unstable, crashing every 1-4 hours, and it's self inflicted. The bright side The bright side is that things are looking much better, there seems to be some rare bugs that happen, but it's stable for the most part now. One guy claims he managed to login multiple times in a row without it saving his progress, which we're looking into. And there's some others who seem to not be able to login sometimes. We're looking into that too. The reception of the update has been a lot better, after holding a tournament yesterday, Kenock (Brazil server admin) remarked that the server felt smoother than ever with a large number of people on the map, and it was a high activity period of Brazil server as well, so there were lots of players online in general. Brazil server host is also notoriously bad (despite being super expensive), so if it runs on Brazil's server well, it's going to run even better on NA's. We don't know when we'll be confident to launch this update on the main server yet. Because if anything messes up, we'll be running heroics, fixing corrupted data, or salvaging the situation, pushing updates on two servers instead of one. This is another reason why we regret so much making this update so major (on an architectural level). We did also have to do a lot of this in order to deprecate the old client. We did spend some time making sure the new client is ready to completely replace the old client, and that anyone will be able to use it. So we haven't had anyone on Brazil server that can't use the new client completely anymore... Lastly, I'd just like to apologize in advance if what we've worked on doesn't please you. I know, it's not what anyone wanted. But we've been doing what we thought was important. We've re-evaluated what's more important going forward and will focus on bringing content updates here on out. It's both easier for us, and more fun for you. Regards, Ueda EDIT: Just thought of something funny. Maybe the reason we worked on Cloud saving is because everyone kept asking "Cloud when?" and we interpreted it wrongly EDIT2: Some of the low-level changes we made include rewriting the game's method of calculating time, and the spell buffer. This could've been causing issues with sometimes your jutsu not casting when you press it, and small things like that - that maybe some players will notice.
- 15 replies
-
- 24
-
-
-
July 2021 Promotions Leaf Village Jonin: @Shinobee Hinode @Naizen Chunin: @Sky Walker @C1over @Sakashi @Gintoki Sand Village Jonin: @Deidara @ana primal Chunin: @Tormenta @Gilgamesh @Obituary @BlackRain Mist Village Jonin: @fox @Insidious Chunin: @Lamentations @pxy @Maniac @Scalpel
-
I signed you out of discord so you can try now Annyeong, welcome to Nin Online.
-
Since launching the Inochi Client at the start of 2021, we've got it to a state where most people, if not all, are better off using it. Some of the major advantages it brings are obvious as a player. For most people, it will bring a performance boost, has new features that weren't possible before and there's no need to install Visual Basic runtime files (COM Components) to run it, which means no more pesky runtime errors. But we've talked a lot about what it brings to the table. Today I'm here to talk about what keeping the Old client around costs and why we have to deprecate it soon. The increased workload of double updates It's hard to push updates with on both clients. There's a separate procedure for pushing updates on both so we have to do double the work. Also, some of the art has to be reworked into different formats for it to work on the old client. We're effectively maintaining, updating and supporting two games at the moment. Two sets of it's own troubles and issues. When an important bug is found on one, it might have to be patched on both. To add an item to the game, we have to update both etc. This slows down development, and this alone outweighs the benefits of maintaining the old client. A new engine, with new possibilities, bogged down by the old client's limitations There's new features that we've added and will be adding that cannot be done in our old engine. Some examples that we've worked on in the past few months that simply wouldn't have been possible before include oAuth login system (which also means social media login), Housing System & Furniture System. There's optimizations that can be made, but not without losing support for the new client. We've done a lot of this in the past few months as well. eg. LZMA Compression (Modern compression library). Once the next update is up, the new client will download and cache maps faster than ever before. There's features we want to add and shaders that we want to use, but will only be possible on the new client as well. Such as a way to recolor hairstyles to any color you want on the spectrum. Better debugging With everyone on the New Client, regardless of how it performs for the individual, it will give us valuable information on how to solve remaining issues and improve performance across the board. We've added a lot more debugging information, along with what's available through 3rd party resources for modern .NET software, we will be able to handle issue reports that crop up better. We've also been able to fix a lot of major issues that have long been impossible to on the new client, thanks to having Visual Studio .NET to work with, better debugging tools. Visual Basic 6 was deprecated in the early 2000s, the IDE doesn't even have Mouse scrollwheel support. That's the kind of limitations we've had to work with all this time. Conclusion There's a lot we can't do until we finally get past the hurdle of finally deprecating our ancient technology. As much as it's sad to say good bye to the old client and the work environment I've been using for 15 years, and 7 years for Nin Online. It's time to say good bye and move towards better days. This is also going to be a one-way street. Once we make this move, it will never be possible to go back because of how major the upgrade is going to be and how much data is going to be converted... but it's one we have to delve into bravely. I hope for everyone's understanding and support. If you haven't already moved over to the new client, please do so by downloading the new installer on the Download section. It also supports Macintosh! PS: For people who are having issues using the new client, part of the deprecation of the old client involves removing some components that were causing that issue. So it will hopefully be working when the update comes. Regards, Ueda
- 2 replies
-
- 12
-
-
-
Thanks for the chat! Enjoyed it.
-
It's not easy. We are only two people. We work on Nin Online full time. We cannot work any faster than we do.
-
We wanted to do this, but due to recent feedback regarding our time spent reworking core systems to make anything rather than late game content like more jutsu. We've decided to pivot focus into just working on the stuff that people actually care about.
-
We wanted to do this, but due to recent feedback regarding our time spent reworking core systems to make anything rather than late game content like more jutsu. We've decided to pivot focus into just working on the stuff that people actually care about.
-
We wanted to do this, but due to recent feedback regarding our time spent reworking core systems to make anything rather than late game content like more jutsu. We've decided to pivot focus into just working on the stuff that people actually care about.
-
Dear Ninja, 7th July 2021 to 7th September 2021 - we'll be hosting our first ever LevelUp! Event to celebrate our 8th Anniversary and as a way to encourage a new beginning for old players, as well as make it a good time for new players to enter Nin Online. The event which will introduce prizes for creating a fresh ninja/character and leveling up. LevelUp! Event Details All characters created after this announcement (Or currently under level 10) is made is eligible for the rewards. For new characters, once you finish the Academy/Tutorial segment, you'll be given a Mission Chain corresponding with your village. Eg. Welcome to the Leaf / Welcome to the Sand. This mission gives new players Blood Pills to have a smoother time grinding solo and EXP to reach level 10 faster. Once you are done with that, you will receive a mission called "Reach Level 10". This starts you off on your LevelUp! event Mission chain. Once you reach Level 10, you'll get a second mission for reaching level 20 and so on! For each 10 levels, players will receive a combination of Event Coupon, Stat Reset, Daily Resets and Blank Scrolls depending on the level. On top of that there are special prizes at Level 30 and Level 60 if you can reach that before the end of the Event. These items will not be available once the event is over. If you have a character under level 10, that character is also eligible join the event by taking on the mission from the LevelUp! Event NPC in each village. Level 30 Special Reward Level 60 Special Reward Anniversary Exclusive Items On top of the LevelUp! Event, we also two time-exclusive cosmetic items that will only be on sale from 7th July - 7th August, they are... Anniversary Summoning Robe Ceramic Furred War Armor Other new Cash Shop Items We're also adding two new cash shop items permanently, they are... Inoshishi Mask by @Master Ant & @Fuze Eye Wrapping Bandages by @Sezu Regards, Ueda
-
- 12
-
-
-
-
8th Anniversary Event for Leveling up new characters (LevelUp! Event) Added option to skip Genin Test if the player is feeling confident. When you get your forehead protector after finishing the Genin Test, you will be teleported to the mission assignment desk. This should make it clearer for new players what to do, instead of expecting them to find their way there. New Missions Chain Added for New Characters, in line with Event announcement. To make level 1-10 easier while introducing new players to the locations in their villages. Also gives them blood pills to train solo easier. Added Anniversary Summoning Robe time-exclusive cash shop cosmetic. Added Ceramic Furred War Armor time-exclusive cash shop cosmetic. Added Eye Wrapping Bandages cash shop cosmetic. Added Inoshishi Mask cash shop cosmetic. Added free stat resets for all new accounts that reach level 10. Reworked some graphics that were directly referenced from Naruto series. Renamed Leaf Village Aviary to Leaf Aviary to match Mist/Sand. Improved Icon Artwork for Summoning Robe. Fixed Chain Missions feature.
-
I've been transparent all this while. People saying I've kept this from people for years. I've not mentioned that we were working on it all this while. I've in fact been saying the opposite. Everything I say in this community is lost in the void and at the end of the day, any form of communication just seems like a mistake. Every criticism put towards me, is appalling to me because I've specifically addressed all those things and responded to all those questions, many times on streams, in announcements, in discord all these years. Nothing gets through, everyone's been self-hyping this for years despite my best attempts at telling people not to. This is my attempt at making it clear. It's only resulted it hate, and I'm done with that. Things are going to change in that regard.
-
And yet again more people missing the point: Nothings changed. We've not been working on Advanced Masteries the way people have been hyping for years now. We've been focusing on reworking the entire game so that when we eventually work on expanding content vertically, it will be worth expanding. The problem is as we were working on Advanced Masteries we were tasked with creating hundreds of new jutsu, it became apparent - everything new being made was just a scaled up reskin of jutsu that already exists with bigger hitboxes or more damage. This wasn't fun. The reason we're reworking the entire game's engine is so we can add more features to it so jutsu aren't just reskins of each other. The reason I announced that Advanced Masteries is cancelled is because the amount of hype people have been having is unproportional to what it would've been if we just "hurry and released advanced masteries" like a lot of people want. Instead, over the past 3 years we've increased content in other ways besides just adding further linear progression to higher levels, we've expanded content by adding more ways you can make your own ninja unique by introducing clans and summons for example which will be two other ways players will be able to build their character differently. Advanced Masteries in the way that was announced in 2018 and soon after stopped being worked on is cancelled. Any further content progression will be something entirely different and is being worked on from the ground up with the new capabilities of the new engine in mind and has always been, but will not be what we announced back then.
HITSPARK