Page is missing title.
Yeah, assuming I didn't screw anything up (What? T.J. make a coding error? IMPOSSIBLE!) Invis chips should now actually do something beyond going to your box and sitting there for the rest of the battle.
On that note, the box is cleared at the end of every turn now, which is the way it's supposed to be.
*Watches as users now abuse Invis chips in the worst ways possible*
Yes, that's right. A BLOG POST. onoz.
Not much to say, but I have made a slight change to the site. The HP of higher ranked viruses will no longer be as high. I mean, BeeTank3 had 1200 HP (300 Chip HP * 4 Stars), and even the second-highest leveled user had trouble killing it. Now it has 900, which is still high, but that's 300 less HP that you have to deal with.
The login page now has a password reset feature that will let you reset your password using either e-mail or AIM.
The registration page now works (I never updated it for the PHP5 version, so when I switched over, people couldn't register).
E-Mail and AIM verification now works (Same as above, forgot to update to PHP5 version)
If you now look at the shop, hovering your mouse over one of the chips will show you information about that chip, which means no more buying blindly.
I've only tested it in Firefox, though, since I don't have IE.
I plan to add it to the Deck and Folder pages at a later date.
In other news, this is the 42nd dev blog post. Hurrah.
First off, I've added the beginnings of a friend system. You can get your friend code on the account page, share it with others, and add other people's friend codes in order to establish a network of friends. Right now being friends doesn't do much, but soon there'll be some nice features such as zeny and chip transfer between friends.
Second, I've updated the help page. It now provides some information about what the deck, folder, and sack are for people unfamiliar with how things work.
As part of an initiative to convert all my sites to PHP5, I'll be working on updating BNCT to PHP5. Due to the nature of this update, the transition from mysql() to PDO() and good coding practices, I can't just slowly convert pages. Instead, I have to keep a separate copy of the code that I'll try to convert, and keep the "production" copy up and running.
What I'm getting to is, in order to see the PHP5 version if for some odd reason you're curious or you enjoy trying to use sites that don't fully function, see http://bnct5.us.to
Simple post to inform everyone about a little fix-everything promotion. Every user that finds and reports a bug to me will get 1,000 zeny. For beta testers it's 10,000 zeny.
Silence on the forums? I know there's been at least 5 people (not including myself) on in the past week, so why doesn't anyone bother with the forums?
[03:00:26] MMBNCT: Done. 5 row(s).
I've actually been doing a lot of work on BNCT today, for whatever reason. There's some more TWoMMBN integration (That I can't tell you more about because that'd give it away), more bug fixing, and a new dev feature called Dev.Docs, where you can read stuff about the internals of BNCT.
I know, surprising, random, and spontaneous comeback, eh?
First things first. I believe registration is fully working. As in, it'll send you an e-mail now. I hope.
Second, fun bug reported by JT. If you beat another player with zeny that's less than zero, it'll make their zeny zero and give you their debt. Not so fun for you, obviously, so I made it so if they are in debt, you don't win anything. Obviously that's not fun either, but it's more fun than losing zeny.
Risch just noticed that using the Regain Lost Turns feature, your zeny can go below 0 if you don't have enough. No longer will that happen.
And taking a look through the code, I realized that if your turns are 20 and you try it, you'll lose zeny but won't get your turns.
Such is the way of betas.
I've accomplished a lot today:
User Vs. User
Donator's Center for those of you who have donated
Lots of Bug fixes
BNCT AIM Bot Enhancements.
I'm not quite sure where AIM got the idea of where I was born, but I finally figured it out. Everyone needs to re-give me their AIM address, though.
Well, let's see, the AIM bot:
Is not infringing on the rights of others.
"is unlawful, threatening, abusive, harassing, defamatory, libelous, deceptive, fraudulent, invasive of another's privacy, tortious, or contains explicit or graphic descriptions, or accounts of, sexual acts"
"victimizes, harasses, degrades, or intimidates an individual or group of individuals on the basis of religion, gender, sexual orientation, race, ethnicity, age, or disability;"
"impersonates any person, business or entity, including AOL and its employees and agents;"
"contains viruses or any other computer code, files or programs that interrupt, destroy or limit the functionality of any computer software or hardware or telecommunications equipment, or otherwise permit the unauthorized use of a computer or computer network;"
No viruses or malicious computer code.
"encourages conduct that would constitute a criminal offense, or that gives rise to civil liability;"
I don't think blog announcements constitute a criminal offense.
"interferes with the use of the AOL Network by others."
No interference caused, the messages are optional.
"You may not use any of our Services or communication tools to transmit, directly or indirectly, any unsolicited bulk communications (including e-mails and instant messages)."
Like I said, you have to sign up saying you want to recieve messages, so it's not unsolicited.
So AOL has no basis for suspending both of my accounts other than their "We may cancel or suspend your registered user account or Screen Name at any time, without cause and/or without notice." clause
But if they did suspend it "without cause" then why did they tell me the cause was that I violated the terms of service?
Because that's what I want to try to say.
I think I know where I was born, Mr. Im-Cool-Because-Im-The-AIM-Password-Recovery-Tool.
But no, it decided that what I put in is not where I was born.
* Chances of adding are low since this virus doesn't attack.
And that's not all. That's just the viruses I didn't implement into Den/Koto/Netopia/Undernet/WWW area. There's still the Detonator/Castle/Main/Apartment/WhateverImissed Comps.
In my slow overhauling of all code from its original version, I have redone the Library. Ta-da? You probably shouldn't notice to much of a difference if you use firefox, other than the fact that it should load much faster and be much less server-intensive. However, in IE, it now looks semi-readable. Same with Opera.
Next up: Deck, most likely with Folder soon to follow.
They suspended the BNCT screen name by scrambling the password and won't let me recover it like the e-mail they send told me to. Way to go.
In the meantime I'll be using NightManEXE as the bot.
I've done a lot of fixing up of the registration. It definately was really buggy before, but no one really cares, I bet.
What you do care about is the battle delay. Don't worry, you can still refresh over and over, you just won't see the outcome. Well, at least you can refresh over and over for now, that'll probably change. The whole point is to get people to read what actually happens during the battle.
I just put up the registration page, meaning anyone who wants to can sign up. At the moment, automatic e-mail validation doesn't work, so if you sign up, manually send an e-mail to bnct[at]technoized.com with your account name and you'll be able to battle.
it's now semi-integraded. Your login for BNCT is required to get onto TWoMMBN, plus there's some NPCs on there that are related to BNCT.
Enjoy, as the lottery now has a point.
So now you need to win 20 battles in an area before you can move onto the next area.
Prevents n00bs from going into advanced areas, once I make them.
Yes, I did it a day ago, but I figured I'd post about it since I didn't have much else to post about.
Because I mean, an entire forum isn't "much else." It should auto-log you in when you login to BNCT, and if you have "remember me" set so that you aren't logged in, then logout then back in and ta-da.
Time to implement cr-A better method of allowing area access rather than just having ever battle area available from the beginning.
And I'm not sure if people actually care whether I make a visual battle or not. I know that should I make one, there will be an option to still use text-only. I'm going to add a delay to the text battle, so watch out rapid refreshers.
Sorry for being a bit...nonexistant in the past week or so. I've definately been busy, off winning Camp Hyrule (CABIN 9 PWNZ U) =D
I should be working on more stuff eventually.
The menu looks better now, thanks to some graphics. =D
I'm not sure what to call the section currently labeled "chips." I mean, they're all tied together, but I can't think of the right word to describe them.
With yet another obvious-yet-took-forever-to-find bug. I mean, it's been there for at least a week or 2, and no one noticed it until now.
Description: Swords (or any chip with "Random" effect) end turn automatically.
Technical Description: Rogue break command caused it to skip the rest of the turn.
In English: I screwed up and forgot to take something out.
...And I squashed it. So yeah, apparantly I never set computer's navis max HP, so if a computer navi tried to heal over its max, its HP automatically went to 0 and you won. This was really noticable vs. Anna, whose first chip is always Recov50, meaning you got an instant S buster rating.
And thus this bug shall forever be known as the "Anna Bug"
I definately forgot to mention, but there's a help section now.
Whenever I get around to creating more writeups, I will, but I'm more focused on working on the game itself.
I created an AIM screenname for BNCT, named MMBNCT. But don't IM it, it's a bot used to IMing announcements to people. Like an announcement about this Dev.Blog post, or that their turns are 20. Just fill out your screen name in Account->Change Profile.
Total Possible Codes: 99,999,999
Possible Winning Codes: 1,152
Chances of Winning: 0.00001152...
Chances of Winning (In English =P): 1 in 100,000.
Better chances than real lottos, I guess =P
And those chances will go up as I add in more chips.
Also, I started to make the user vs. user battling, but I stopped because I'm not sure how I want to do it. So, using whatever your preferred mode of contact with me is, give me suggestions as to what you want user to user battling to include. Whether you just want to be able to see who'd win, or if you think you should be able to wager chips, tell me what you want.
Sorry, I had to do it. I reset all of the beta tester's accounts. I have to make sure the game isn't too hard for people just signing up, and that it doesn't get too easy for people who get more experience.
So I can someday buy a domain. =D
You know you want to.
It's down on the menu at the bottom
So, yeah. You will not believe how damn hard it was to implement the stun effect. I mean, ugh.
But hey, it's there, you better use it.
I know people have complained that it's hard to make money, especially when they keep getting S busting levels on viruses. So, now I'm making it easier. First of all, you can sell chips for money. The amount you can sell it for will change day to day, though.
Also, I'm going to make it so viruses give more zeny.
And thus, it'll become easier to afford those expodentially more expensive MB and HP upgrades.
First of all, you can fight navi's again. I only disabled it in the first place because having only one computer navi to fight is a bit bad/cheap/boring. Now there's five or so and I plan on adding more.
On a similar note of battling, you can now view your recent logs in the account section.
I just optimized the library so it runs 50-70% faster and uses 25% of the amount queries it used to. What does this mean? Lower load times and less server resources used, so that it won't kill the server it's on if/when BNCT gets popular.
Yes, I just went through and looked at my queries+code to make sure they were secure against SQL-injection and other hacks. And so I noticed, PHP Notice-level errors do a good job at preventing register_globals exploits.
So. Have fun buying HP and MB upgrades. Just remember they get steadily more expensive.
Other than that, I fixed a few other bugs, etc, you know. I should probably go over my code and make sure there's no vulnerabilities in it, but yeah. No one's hacked it yet. =P That's only because no one knows it exists yet, but oh well.
K, I didn't get to do account yet. Oh well. I changed all instances of "alpha" to "beta." This site never really was alpha after the first 2 days, since it's been a working game and I make sure new features work before I release them.
There's been relatively few bugs so far, but all of the reported ones have been fixed. Remember, if you have a bug, e-mail/IM me. Most beta testers can contact me on AIM, but if you need it my e-mail is bnct[at]technoized.com
Yes, I am home. Unfortunately this means a lack of port 80, so there's a new URL. But if you're reading this post then you're on the new site so it's all good.
Login can now remember people! That in itself is nice since we all hate logging in again and again.
I also did some random securing of the site after seeing how damn unsecure Aardvark Topsites is.
Expect a user control center sometime soon. Soon may be tomorrow, depending on if I get to it in the next 30 minutes.
I'm writing this from a dark hotel in Daytona Beach. Dark because everyone else is sleeping.
Anyways, new battle system is public, and I bet you can't tell the difference. I'm looking into the flash frontend, and it's looking pretty possible.
I fixed the shop a bit so it tells you that you bought a chip. I also made it so that there'll be no duplicate chips in the shop. Because we all hate duplicates.
Maybe I'll add more chips later, but for now, time for me to catch some Y's. Or was it Q's? Nah, definately
I guess the initial rush of users has died down. I know there's 6 beta testers and a demo account, but none of the testers go on anymore. Maybe once I add new chips.
Also, if any beta testers are reading this, prepare for a character reset soon. I need to test how easy/hard the game is from a newbie standpoint.
Yes, the redo is 50% done.
On another note, all activity is apparantly dying off.
On a third note, I created a "closed" system so that I can prevent people from accessing the site if need be.
On a fourth and completely unimportant-to-you note, I made it easier for me to post in the dev.blog.
That's right, I started the battle system redo. it's kind of annoying, but so far it's working out fine. I have everything planned out, so I hope it goes smoothly. It's not in a state where I can show it to you yet, but once it is I'll put up a link to a test battle.
Then again, considering I'm the only one doing the development, I guess it's pretty obvious who that "somebody" is...
Right. So I decided, instead of working on stuff, I'm going to waste my time creating a development blog. It's not like it'll take too much time, but it'll waste time so I can put off the dreaded battle system rewrite I know I have coming. The current battle system may look fine to you users, but the source code to it is a mess, and in it's current state it won't work for what else I plan to do: Implement a flash frontend so your battles look nice and pretty. And so, I get to rewrite the battle system. You shouldn't notice any difference at first, but I will =D.
Other things I've done to delay the inevitable: Implement so more chips, like Fire/Aqua/ElecBlde VarSwrd, and CustSwrd. The only way to get them is through the lottery (Like that's going to happen, there's only around 1000 winning codes and 98,999,999 possibilities [I think], so the chances of winning with any one code are 0.001%, or 1/100000) or through the chip shop (Wait a day or two and I bet at least one of them will end up in there.) Which reminds me, I need to make an upgrades shop for buying MB and HP upgrades.
I guess it's time to stop writing this post now and to actually code the dev blog so I can get on with the battle system redo...
And in case any testers/people using the demo user are wondering, I disabled battling computer navis until I put in more computer navis than just Koetsu.