1stClassGenesis
New Member
- Joined
- Apr 28, 2013
- Messages
- 28
- Points
- 1
In the right manner and the right intake of caffiene, anything is possible in a video game 
Jinji's Staff Journal
- Thread starter Jinji
- Start date
Heh, so true. Though I'm not a big fan of energy drinks myself; and "Mountain Dew Energy" (as it's branded in the UK, since it's a slightly changed recipe from the U.S. "Mtn Dew") is waaaaaaaaaay too sugary in my view; so the only "gamer fuel" I really drink is Dr. Pepper and only occasionally.
To be honest, my daily caffeine intake mostly comes from coffee. If there are soft drinks involved, they're mostly Pepsi or Coke, as usually 2-litre bottles of at least one of those is on offer at a local store per week; though sometimes it's an "any two bottles of Dr.Pepper, Sprite or Fanta" deal instead. On rare occasions they'll run several of these offers at the same time and that's when I go overboard.
To be honest, my daily caffeine intake mostly comes from coffee. If there are soft drinks involved, they're mostly Pepsi or Coke, as usually 2-litre bottles of at least one of those is on offer at a local store per week; though sometimes it's an "any two bottles of Dr.Pepper, Sprite or Fanta" deal instead. On rare occasions they'll run several of these offers at the same time and that's when I go overboard.
1stClassGenesis
New Member
- Joined
- Apr 28, 2013
- Messages
- 28
- Points
- 1
My intake of caffeine is like a elephant taking in over 9000 peanuts, in otherwords, way to much, im like a addict and I cant help it D:
I got a message back from both the manufacturer of my laptop today and the courier who took it to them for repair; and if I am reading it correctly, my issue is finally resolved and I will have my laptop returned and operational after this weekend. I am hopeful this is correct.
Indeed I was correct - such are the benefits of Ghostly wisdom. My damaged laptop has been fully repaired, and was returned early this morning with all its data still intact, but with a whole new chassis and charger. This was a lot faster than had been previously indicated by the manufacturers; and with no wiped data I only had to check that the repair did the job - which it had - and I was thereafter able to get straight back to work with only a week's worth of software updates providing any extra delay.
TL;DR: PWO's Ghostly Resident has returned and is active once again. Whether this is a relief or a nightmare is your own decision to make.
TL;DR: PWO's Ghostly Resident has returned and is active once again. Whether this is a relief or a nightmare is your own decision to make.
xDaSnowman
New Member
- Joined
- Jan 28, 2013
- Messages
- 279
- Points
- 16
Welcome back Jinji
Thanks, Snow.xDaSnowman said:Welcome back Jinji
Starting from the next Server Restart following this post, a change to the PWO Battle System will be live. If all goes well, it will now be impossible for the same Status Ailment to take effect on a Pokémon already afflicted with it.
In recent discussions on the Forum, a number of you complained about the Sleep effect being overpowered as it can be repeatedly inflicted. Sleep is guaranteed to last at least one turn if effective on a Pokémon, but the claim was that it could be used on an already sleeping Pokémon to reset the timer. This claim took some of us Staff by surprise, as we believed the server already had checks to prevent multiple application of the same Status. However, I did not observe such a check on analysing the code earlier today.
Ever resourceful, I took matters into my own hands. Should all work as intended, the behaviour in battle now should be, whenever a new Status is attempted to be applied to a Pokémon, it is compared to their existing Status. If an attack tries to give a Pokémon a Status Ailment or change it already has, you will be shown the appropriate "already affected" message; and the Status will not be reapplied.
Example: Try to confuse a Pidgey that already is confused, and you'll now see "Pidgey is already Confused!" and we won't try to Confuse again. Jigglypuff tries to send you to sleep twice? Same thing again, only the message will say "...is already asleep!" This applies to all currently supported Status Ailments, in the same way as official games if I recall correctly. So if your Pokémon seems to sleep forever and it's not a Snorlax... perhaps you should seek medical attention for it, or check it's not had its mind damaged by darker forces... kekeke...
As always, please inform us if you observe any bugs or unexpected behaviour with this change.
In recent discussions on the Forum, a number of you complained about the Sleep effect being overpowered as it can be repeatedly inflicted. Sleep is guaranteed to last at least one turn if effective on a Pokémon, but the claim was that it could be used on an already sleeping Pokémon to reset the timer. This claim took some of us Staff by surprise, as we believed the server already had checks to prevent multiple application of the same Status. However, I did not observe such a check on analysing the code earlier today.
Ever resourceful, I took matters into my own hands. Should all work as intended, the behaviour in battle now should be, whenever a new Status is attempted to be applied to a Pokémon, it is compared to their existing Status. If an attack tries to give a Pokémon a Status Ailment or change it already has, you will be shown the appropriate "already affected" message; and the Status will not be reapplied.
Example: Try to confuse a Pidgey that already is confused, and you'll now see "Pidgey is already Confused!" and we won't try to Confuse again. Jigglypuff tries to send you to sleep twice? Same thing again, only the message will say "...is already asleep!" This applies to all currently supported Status Ailments, in the same way as official games if I recall correctly. So if your Pokémon seems to sleep forever and it's not a Snorlax... perhaps you should seek medical attention for it, or check it's not had its mind damaged by darker forces... kekeke...
As always, please inform us if you observe any bugs or unexpected behaviour with this change.
I knew I should've explained this better. No, the new system doesn't extend this far currently; and honestly I don't see any good reason for doing it like this. A Pokémon that has an ailment simply can't be affected by the same ailment while it is effective; but there is nothing preventing the ailment being replaced with another before it wears out.Merse said:
Orean
New Member
Not sure if this has been reported yet, but the fix seems to have been a no-go on this attempt, as I tested it out with status-ailment moves. When using a status-inducing move on a Pokemon, already onset by a status ailment, it appears to reset the counter still.
I have done this extensively to ascertain this, and through this cycle, the Pokemon's status ailment still outlasted the maximum amount of rounds it should have under it (sleep, in this example); due to re-applying the status to them every round.
Apart from that, there is not any abnormal behavior with this change that I have taken notice to.
I have done this extensively to ascertain this, and through this cycle, the Pokemon's status ailment still outlasted the maximum amount of rounds it should have under it (sleep, in this example); due to re-applying the status to them every round.
Apart from that, there is not any abnormal behavior with this change that I have taken notice to.
Based on the time of your post, it's possible at the time you tried this that the new code was not yet in use because it was awaiting a server restart to execute the new code. Could you tell me if this is still occurring now?
*Sigh* Darn it... so the test isn't working then. Okay, I'll need to go back through it again.
I currently don't have the time available to work on this.
Uh, maybe you put the test in a wrong place? Cause right now both pokemon can't have the same status problem. In a few battles, like Exeggutor vs Exeggutor only the first Leech Seed worked. I tried with my Exe 3 times to Seed the opponent, but it simply didn't do anything, because i was already seeded. The same thing happened when 2 Confuse Rays were used by myself and my opponent. The first worked, the second didn't. I haven't been able to confirm yet if different statuses work, but in a battle both pokemon can't have the same status problem.
EDIT: I know how it is with the time, I'm busy too, just check on it whenever you're free.
EDIT: I know how it is with the time, I'm busy too, just check on it whenever you're free.
Tecknician
New Member
- Joined
- Dec 10, 2012
- Messages
- 925
- Points
- 16
Added something to the code that should fix this issue.
Jinji, I will pm you the details.
Jinji, I will pm you the details.
Hmm... I thought I did exactly that already. Well, let's see how it works.